Home

• Hercules Network & Wireless Cards Driver Download For Windows 10 Free
• Hercules Network & Wireless Cards Driver Download For Windows 10 64-bit
• Hercules Network & Wireless Cards Driver Download For Windows 10 Full
• Hercules Network & Wireless Cards Driver Download For Windows 10 Download

Download Hercules Wireless G USB 2.0 2.5.0.0 (Network Card) Compatible with IEEE 802.11g high-rate standard with speeds up to 54Mbps data-rate Backward compatible with IEEE 802.11b standard. Hercules version 3: TCP/IP networking with Hercules. This page describes how to set up TCP/IP connectivity between a Hercules machine and the outside world. Since Hercules runs as a user process under the control of a driving system (usually Linux/x86 or Windows), it does not have direct access to the driving system's network adapter.

Hercules SETUP utility is useful serial port terminal (RS-485 or RS-232 terminal), UDP/IP terminal and TCP/IP Client Server terminal. It was created for HW group internal use only, but today it's includes many functions in one utility and it's Freeware!

HERCULES Tower provides a range of fully serviced office spaces in several Business Centers in the heart of Limassol.

Book your viewing today or send us a direct request for any further information.

Hercules Network & Wireless Cards Driver Download For Windows 10 Free

This page describes how to set up TCP/IP connectivity betweena Hercules machine and the outside world.

Since Hercules runs as a user process under the control of a drivingsystem (usually Linux/x86 or Windows), it does not have directaccess to the driving system's network adapter. This presents aproblem in establishing connectivity between the network and theTCP/IP stack of an operating system running under Hercules.

But thanks to a technique originally demonstrated byWillem Konynenberg, it is possible to establish a virtualpoint-to-point link between the TCP/IP stack running underHercules and the TCP/IP stack of the driving system. Thedriving system is then used as a router to pass IP framesbetween the Hercules TCP/IP stack and the rest of the network,as shown in the below diagram.

The virtual CTC link is provided by the Universal TUN/TAP driverdeveloped by Maxim Krasnyansky. This driver creates a tunnelwhich appears to Hercules as a character device (/dev/tun0 or/dev/net/tun) and appears to the driving system as a virtualnetwork interface (tun0).The Hercules 3088 driver makes the tun device appear asa CTCA (Channel to Channel Adapter) to the S/390 operating systemrunning under Hercules. Each end of the link has its own IPaddress which is distinct from the IP address of the drivingsystem's real network adapter.

Windows users should refer to Fish's CTCI-WIN web page which provides similar 'TunTap' functionality on Windows platforms.

Installing the TUN/TAP Driver (Linux 2.4)

The TUN/TAP driver is delivered as part of the Linux 2.4 kernel, andif you are using one of the popular Linux distributions you will findthat the TUN/TAP driver is already installed. If not, then you mustrebuild the kernel with the configuration option CONFIG_TUN=m specified.

Note that the version of TUN/TAP in Linux 2.4 differs from the earlierversion in that it allows access to all TUN interfaces (tun0, tun1, etc)through a single character device /dev/net/tun, instead of definingmultiple devices /dev/tun0, /dev/tun1, etc.

The procedure for completing the TUN/TAP setup for Linux 2.4 is shown below.

1. Use these commands to create the TUN device:
su (enter the root password when prompted)
mkdir /dev/net
mknod /dev/net/tun c 10 200
chgrp xxxxx /dev/net/tun (where xxxxx is the group under which you run Hercules)
chmod g+rw /dev/net/tun
chmod o-rw /dev/net/tun
2. Edit the file /etc/modules.conf (it is called /etc/conf.modules in some distributions) and add the following line:
   alias char-major-10-200 tun
   This causes the TUN/TAP driver to be loaded automatically when the /dev/net/tun device is opened by Hercules.

Installing the TUN/TAP Driver (Linux 2.6, FreeBSD, OS X)

For distributions based on the Linux 2.6 kernel you will probably find that theTUN/TAP driver is already installed and the /dev/net/tun device is alreadydefined. If not, then follow the procedure for Linux 2.4 as descibed above.

For FreeBSD, refer to man tun.You will likely want to enablenet.link.tun.devfs_cloning to create/dev/tun, but you will be in uncharted waters.

If you are using a current distributionyou will need to alter the permissions on the /dev/net/tun deviceto allow Hercules to open it.Issue ls -l /dev/net/tun (Linux)ls -l /dev/tun0 (OSX) to determine whether Hercules canopen the device.

You have two ways to make the tun device usable.Use the second only with nonstandard and/or old kernels(that is, if the first udev rule does not work for you.)

1. The preferred way to change properties for the Linux tundevice is via a udev rule in/etc/udev/rules.d
2. Alternatively, use the following commands to set the necessary permissions:

   su (enter the root password when prompted)
chgrp xxxxx /dev/net/tun (where xxxxx is the group under which you run Hercules)
chmod 0660 /dev/net/tun

   or make the device file writable by world; this does not consist an integrity exposure, as the world at large cannot do anything with the file descriptor it gets.

   chmod 0666 /dev/net/tun

   Additional notes from Greg Smith:

   1. I find on my Fedora Core 6 system that I have to add the above 2 commands to /etc/rc.local and update /etc/udev/rules.d/50-udev.rules replacing
      KERNEL'tun', NAME='net/%k'
      by
      KERNEL'tun', NAME='net/%k', GROUP='xxxxx', MODE='0660'
   2. In the hercules log you should see /dev/net/tun0 opened. I get a couple of error messages about SIOCDIFADDR and SIOCSIFHWADDR ioctl's failing but these can be ignored.

In Linux 2.6 the file /etc/modules.conf no longer exists,instead there is a file called /etc/modprobe.conf.TUN/TAP will usually work, however, without any change to the modprobeconfiguration.

Configuring a TUN interface

You may be able to configure the tunnel interfaces you will needat system boot;but if you cannot or will not, Hercules supplies a utility(hercifc) to do this.

At Linux boot

openvpn (http://openvpn.net/)is a utility that can open a tunnel device permanently.In addition you are likely to need a udev rule as described above.Openvpn is usually installed as a package (yum install openvpn on Fedora);if not refer to http://openvpn.net/index.php/open-source/documentation/howto.html.Note, however, that openvpn is just one way to create a permanent tunnel device;alternative methods may be possible.

To create permanent a tunnel interface, add this to rc.local(or as appropriate forthe distribution you are using):

This example assumes that Hercules is in the grouphercules; it shows the tunnel device in a separate network,which requires routing as described below.ifconfig can display the permanent interface:

If the interface is in the same subnet as the Hercules host,you need to enable proxy arp.One way to achieve this is to turn it on dynamically:

Free BSD

On FreeBSD, use the command ifconfig tun create to createan interface.

Using hercifc

The tun0 network interface in the driving system must be configuredas a point-to-point link. The original design of the TUN/TAP driver did notallow the interface to be statically configured like a regular networkinterface — the tun0 interface does not exist until a programopens the TUN device. For this reason, Hercules provides a specialprogram called hercifc to configure the tun0 network interface. Thisprogram is launched automatically by Hercules 3088 CTC deviceinitialization.(Later, the ability to make an interface permanent was added;this is why openvpn and preconfigured interfaces work.)

Hercules Network & Wireless Cards Driver Download For Windows 10 64-bit

To allow the hercifc program to issue the necessary configurationcommands, you must ensure that hercifc is installed with setuid rootfile permissions. When Hercules is built with theconfiguration option --enable-setuid-hercifc=xxxxx, make installwill install hercifc in /usr/local/bin with setuid root permissions.The hercifc program will be executable only by group xxxxx.Note: Unrestricted access to the hercifc program could present apotential security exposure, so you will want to ensure that hercifccan be executed only by the group which is authorized to run Hercules.

Hercules Network & Wireless Cards Driver Download For Windows 10 Full

The following commands have the same effect as theconfiguration option --enable-setuid-hercifc=xxxxx:

su (enter the root password when prompted)
chgrp xxxxx /usr/local/bin/hercifc (where xxxxx is the group under which you run Hercules)
chmod 4750 /usr/local/bin/hercifc
exit

Note: you can avoid the need to install hercifc as a setuid rootprogram by creating a permanent tunnel interface at Linux boot time,as described above.

Enabling IP forwarding

You must ensure that your kernel is enabled for IP forwarding.Popular Linux distributions usually have a configuration optionto enable IP forwarding or routing:

• For RedHat, specify net.ipv4.ip_forward=1 in the /etc/sysctl.conf file.
• For SuSE, specify IP_FORWARD='yes' in the /etc/rc.config file.
• If you cannot find this option in your distribution, the following command should work on any Linux 2.x and later kernel:
  echo '1' > /proc/sys/net/ipv4/ip_forward

Defining a route to Hercules TCP/IP

Client systems that connect to TCP/IP applications running inthe Hercules machine need to have a routing entry to definethe driving system as the gateway into the Hercules system. Anexample route definition for a Unix client system is shown below:

For a Windows client, go to Settings -> Control Panel -> Network ->Configuration -> TCP/IP -> Properties -> Gatewayand add the driving system's IP address to the list of gateways.Alternatively, enter a route command such as:

If you want to avoid having to update client systems, another wayis to add an appropriate routing entry to your default gateway router.

Defining the link in Hercules

You must define a CTC device pair in the Hercules configurationfile:The first device number must be even.The second device must bear the same definition as the firstinstance and be at device number + 1(for CTCI, the first definition beyond the device type is ignored;you only need to specify the definition with the second device).Devices should preferably be grouped (furthermore, it makes theconfiguration file easier to read).

For a preconfigured tunnel:


0E20.2 CTCI tun0
or
0E20,0E21 CTCI tun0
or
0E20-0E21 CTCI tun0

Using hercifc:


0E20.2 CTCI 192.168.200.1 192.168.200.2
or
0E20,0E21 CTCI 192.168.200.1 192.168.200.2
or
0E20-0E21 CTCI 192.168.200.1 192.168.200.2

Check Device Definition Statement syntax for an explanation of device grouping.

Two IP addresses must be assigned, one for the driving system'send of the link, and one for the Hercules end of the link. Forthis example I have chosen 192.168.200.1 for the Hercules IPaddress, and 192.168.200.2 for the driving system's IP address.Since this is a point-to-point link, any addresses may be chosen,provided that the network part of the address (192.168.200 inthis example) does not conflict with any existing networkaddresses used in your IP network.

Configuring the Hercules TCP/IP stack

TCP/IP for VSE

This is an example of the configuration statements which you needto include in the IPINIT00.L member of PRD1.BASE:

The CTC devices should be defined to VSE using the followingstatements in the $IPLxxx.PROC procedure in IJSYSRS.SYSLIB:

TCP/IP for OS/390 or VM/ESA

This is an example of the configuration statements which you needto include in the TCPIP.PROFILE.TCPIP dataset (OS/390), or in thePROFILE TCPIP file on TCPMAINT 198 (VM):

For OS/390, the CTC devices need to be defined as device type 3088 inthe IODF. Use the D U,CTC command to find out which 3088addresses are defined in your IODF.

For VM, the CTC devices must be attached to the TCPIP virtual machine.

Because TCP/IP uses long running channel programs, the missing interrupthandler should be disabled for the CTC devices.For OS/390, add this statement in PARMLIB member IECIOS00:

For VM, add this command to the PROFILE EXEC file of OPERATOR 191:

Linux for S/390

This is an example of the network definitions which you needin a Linux/390 system running under Hercules:

Linux/390 will autodetect the CTC devices E20 and E21at startup and will assign the interface name ctc0.

What to do if TUN/TAP doesn't work

Check the following (thanks to Richard Higson for this checklist):

1. Enter the command ls -l /dev/tun0 /dev/net/tun.
   For Linux 2.4 and later kernels, the response should be:
ls: /dev/tun0: No such file or directory
crw-rw---- 1 root xxxxx 10, 200 Sep 13 07:06 /dev/net/tun
   For Linux 2.2, the response should be:
crw-rw---- 1 root xxxxx 90, 0 Feb 3 2001 /dev/tun0
ls: /dev/net/tun: No such file or directory
   (xxxxx should be the group under which you run Hercules).
2. ls -l /usr/local/bin/hercifc should show
-rwsr-x--- 1 root xxxxx 17333 Dec 31 20:55 /usr/local/bin/hercifc
   (xxxxx should be the group under which you run Hercules).
3. When hercules comes up, and before IPLing your favorite OS, verify that you have your underlying network stuff up and ready to roar:
4. `cat /proc/sys/net/ipv4/ip_forward` should show '1'. If it doesn't, your L386 won't forward (route) packets at all.
5. Is the TUN/TAP driver loaded?
   1. TUN/TAP compiled into the kernel (`make menuconfig`) look for 'CONFIG_TUN=m' in /usr/src/linux
   2. `lsmod` after starting hercules should show tun 3456 2 (autoclean)
6. Look for
Dec 14 16:47:19 wie kernel: Universal TUN/TAP device driver 1.3 (C)1999-2000
Maxim Krasnyansky
   in syslog after starting hercules

Hercules Network & Wireless Cards Driver Download For Windows 10 Download

Last updated $Date$ $Revision$