Getting networking to work with Hercules and Windows 7

[Jeff]

This is my first attempt to work with Hercules networking, so perhaps I am missing something very obvious.

A little background - at first, I set up Hercules to connect to the adapter at ip address 172.20.3.23 and used 172.20.3.239 as the ip of my guest. I was able to ping back and forth between these two addresses, but could not ping any other device on the network, nor could they ping my guest. I had an idea that if I added a second network card, and gave it the 192.168.3.223 and assigned 192.168.3.23 to my guest, then I could add a route statement in my router to make 192.168.x.x addresses come back to my windows pc. This has not worked at all - I cannot even seem to get windows to ping the guest any more, even though I am using the mac address option. Anyway, here is what I have - any ideas would be appreciated....
*****************
Windows ipconfig:
*****************
Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
Physical Address. . . . . . . . . : 00-50-56-AE-00-03
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.3.223(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-50-56-AE-00-02
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6158:d3c6:e53c:d214%11(Preferred)
IPv4 Address. . . . . . . . . . . : 172.20.3.23(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.20.3.1
DHCPv6 IAID . . . . . . . . . . . : 234901590
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-D6-D6-5D-00-50-56-AE-00-02
DNS Servers . . . . . . . . . . . : 172.20.3.19
172.20.3.54
NetBIOS over Tcpip. . . . . . . . : Enabled

***********
Hercules config
***********
# Ethernet adapter
# 04A0.2 CTCI 172.20.3.25 192.168.200.2
# can use the 172.20.3.239 address if this doesn't work
# Careful of these IP addresses!!!!!!!!!!!!!!!!!!!!
# 04A2.2 CTCI 192.168.3.23 172.20.3.23
# 04A2.2 CTCI 192.168.3.23 192.168.3.223
04a2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 0.0.0.0

************
Guest definitions
************
DEVICE LCS4A2 CTCA 4A2
LINK LCS4A2 0 192.168.3.23 255.255.255.0 1480
ROUTE LCS4A2 192.168.3.0 255.255.255.0 192.168.3.223
* ROUTE LCS4A2 172.20.3.0 255.255.255.0 172.20.3.23
* ROUTE LCS4A2 172.20.3.19 255.255.255.0 172.20.3.23 1
* ROUTE LCS4A2 172.20.4.0 255.255.255.0 172.20.3.1 1
ROUTE LCS4A2 0.0.0.0 0.0.0.0 192.168.3.223 1

***********
output of tt32test64
***********
08:18:17.846 Begin TT32Test64.exe, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
08:18:17.846
08:18:17.846 Running on Windows XP, version 6.1.7600
08:18:17.846
08:18:17.846 Using WinPCap Packet.DLL, version "4.1.0.2001" (1.0.4.1), driver version "4.1.0.2001" ...
08:18:17.846
08:18:17.846 Using FishPack64.dll, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
08:18:17.846
08:18:17.846 Using TunTap64.dll, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
08:18:17.846
08:18:17.847 --------- The following relevant DosDevices are defined ---------
08:18:17.847
08:18:17.849 NPF_NdisWanBh
08:18:17.849 NPF_NdisWanIp
08:18:17.849 NPF_NdisWanIpv6
08:18:17.850 NPF_{18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.850 NPF_{5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.850 NPF_{620EB585-BDCC-43D5-A62A-FC9A85864CFC}
08:18:17.850 NPF_{71F897D7-EB7C-4D8D-89DB-AC80D9DD2270}
08:18:17.850 NPF_{78032B7E-4968-42D3-9F37-287EA86C0AAA}
08:18:17.850 NPF_{802389A0-9C1A-4C28-9099-BC7F2A90C31A}
08:18:17.850 NPF_{8E301A52-AFFA-4F49-B9CA-C79096A1A056}
08:18:17.850 NPF_{DF4A9D2C-8742-4EB1-8703-D395C4183F33}
08:18:17.850 NPF_{E43D242B-9EAB-4626-A952-46649FBB939A}
08:18:17.850 NPF_{FB5AA89A-5CF5-47E9-9437-5287F7DD3BE2}
08:18:17.850 {18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.850 {5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.850 {620EB585-BDCC-43D5-A62A-FC9A85864CFC}
08:18:17.850 {71F897D7-EB7C-4D8D-89DB-AC80D9DD2270}
08:18:17.850 {78032B7E-4968-42D3-9F37-287EA86C0AAA}
08:18:17.850 {802389A0-9C1A-4C28-9099-BC7F2A90C31A}
08:18:17.850 {8E301A52-AFFA-4F49-B9CA-C79096A1A056}
08:18:17.850 {DF4A9D2C-8742-4EB1-8703-D395C4183F33}
08:18:17.850 {E43D242B-9EAB-4626-A952-46649FBB939A}
08:18:17.850 {FB5AA89A-5CF5-47E9-9437-5287F7DD3BE2}
08:18:17.850
08:18:17.850 ------------------------- Network Information -------------------------
08:18:17.850
08:18:17.850 Host Name . . . . . . . . . : agxopmf00
08:18:17.850 Node Type . . . . . . . . . : Hybrid
08:18:17.850 DNS Servers . . . . . . . . : 172.20.3.19
08:18:17.850 172.20.3.54
08:18:17.850 IP Routing Enabled. . . . . : yes
08:18:17.850
08:18:17.850 Network Address Netmask Gateway Address Interface Metric
08:18:17.850 0.0.0.0 0.0.0.0 172.20.3.1 172.20.3.23 266
08:18:17.850 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 306
08:18:17.850 127.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 127.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 172.20.3.0 255.255.255.0 172.20.3.23 172.20.3.23 266
08:18:17.850 172.20.3.23 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 172.20.3.255 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 192.168.3.0 255.255.255.0 192.168.3.223 192.168.3.223 266
08:18:17.850 192.168.3.23 255.255.255.255 192.168.3.223 192.168.3.223 11
08:18:17.850 192.168.3.223 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850 192.168.3.255 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850 224.0.0.0 240.0.0.0 127.0.0.1 127.0.0.1 306
08:18:17.850 224.0.0.0 240.0.0.0 172.20.3.23 172.20.3.23 266
08:18:17.850 224.0.0.0 240.0.0.0 192.168.3.223 192.168.3.223 266
08:18:17.850 255.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 255.255.255.255 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 255.255.255.255 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850
08:18:17.850 Default gateway: 172.20.3.1
08:18:17.850
08:18:17.850 -------------------------- Detected Adapters --------------------------
08:18:17.850
08:18:17.857 AdapterName = NPF_{5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.857 Description = Intel(R) PRO/1000 MT Network Connection #2
08:18:17.857 PhysAddr = 00-50-56-AE-00-03
08:18:17.857 LinkType = NdisMedium802_3
08:18:17.857 MediaConnected = Yes
08:18:17.857 LinkSpeed = 1.0 Gbps
08:18:17.857 IPAddr = 192.168.3.223
08:18:17.857 IPAddrMask = 255.255.255.0
08:18:17.857 GatewayIPAddr = 0.0.0.0
08:18:17.857 dwIndex = 0x0000000D
08:18:17.857 Checksum offloading = no
08:18:17.857
08:18:17.859 AdapterName = NPF_{18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.859 Description = @nete1g3e.inf,%e100fgen.devicedesc%;Intel(R) PRO/1000 MT Network Connection
08:18:17.859 PhysAddr = 00-50-56-AE-00-02
08:18:17.859 LinkType = NdisMedium802_3
08:18:17.859 MediaConnected = Yes
08:18:17.859 LinkSpeed = 1.0 Gbps
08:18:17.859 IPAddr = 172.20.3.23
08:18:17.859 IPAddrMask = 255.255.255.0
08:18:17.859 GatewayIPAddr = 172.20.3.1
08:18:17.859 dwIndex = 0x0000000B
08:18:17.859 Checksum offloading = no
08:18:17.859


*********************
Any suggestions are appreciated. thanks.

[jsganino]

Jeff,

Post by Jeff
Hercules config
***********
# Ethernet adapter
# 04A0.2 CTCI 172.20.3.25 192.168.200.2
# can use the 172.20.3.239 address if this doesn't work
# Careful of these IP addresses!!!!!!!!!!!!!!!!!!!!
# 04A2.2 CTCI 192.168.3.23 172.20.3.23
# 04A2.2 CTCI 192.168.3.23 192.168.3.223
04a2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 0.0.0.0

Try

04A2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 192.168.3.223

Or

04A2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 192.168.3.24

(I just picked the .24 address assuming that you don't already use it.)

As I understand it, the CTCI interface sets up a "tun" device and routes a IP (layer 3) point-to-point connection over it. So, your windows box winds up acting like a router directing traffic to Hercules over the "tun" device and traffic to the rest of the subnet over the ethernet device. I just recently struggled with getting an LCS interface to work on a Linux box, but there are posts in this list that describe successes with CTCI, so I'm sure it can be done. The gentleman who wrote the TT32Test64.exe and FishPack64.dll programs you are using visits this list occasionally (and sometime even frequently) and knows the windows side of what you're trying to do quite well. (Fish -- If you are reading this, and I have given Jeff any bum steers, please jump in and correct me.)

Good Luck,

Jim

Post by Jeff
This is my first attempt to work with Hercules networking, so perhaps I am missing something very obvious.
A little background - at first, I set up Hercules to connect to the adapter at ip address 172.20.3.23 and used 172.20.3.239 as the ip of my guest. I was able to ping back and forth between these two addresses, but could not ping any other device on the network, nor could they ping my guest. I had an idea that if I added a second network card, and gave it the 192.168.3.223 and assigned 192.168.3.23 to my guest, then I could add a route statement in my router to make 192.168.x.x addresses come back to my windows pc. This has not worked at all - I cannot even seem to get windows to ping the guest any more, even though I am using the mac address option. Anyway, here is what I have - any ideas would be appreciated....
*****************
*****************
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
Physical Address. . . . . . . . . : 00-50-56-AE-00-03
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.3.223(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
NetBIOS over Tcpip. . . . . . . . : Enabled
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-50-56-AE-00-02
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6158:d3c6:e53c:d214%11(Preferred)
IPv4 Address. . . . . . . . . . . : 172.20.3.23(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.20.3.1
DHCPv6 IAID . . . . . . . . . . . : 234901590
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-D6-D6-5D-00-50-56-AE-00-02
DNS Servers . . . . . . . . . . . : 172.20.3.19
172.20.3.54
NetBIOS over Tcpip. . . . . . . . : Enabled
***********
Hercules config
***********
# Ethernet adapter
# 04A0.2 CTCI 172.20.3.25 192.168.200.2
# can use the 172.20.3.239 address if this doesn't work
# Careful of these IP addresses!!!!!!!!!!!!!!!!!!!!
# 04A2.2 CTCI 192.168.3.23 172.20.3.23
# 04A2.2 CTCI 192.168.3.23 192.168.3.223
04a2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 0.0.0.0
************
Guest definitions
************
DEVICE LCS4A2 CTCA 4A2
LINK LCS4A2 0 192.168.3.23 255.255.255.0 1480
ROUTE LCS4A2 192.168.3.0 255.255.255.0 192.168.3.223
* ROUTE LCS4A2 172.20.3.0 255.255.255.0 172.20.3.23
* ROUTE LCS4A2 172.20.3.19 255.255.255.0 172.20.3.23 1
* ROUTE LCS4A2 172.20.4.0 255.255.255.0 172.20.3.1 1
ROUTE LCS4A2 0.0.0.0 0.0.0.0 192.168.3.223 1
***********
output of tt32test64
***********
08:18:17.846 Begin TT32Test64.exe, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
08:18:17.846
08:18:17.846 Running on Windows XP, version 6.1.7600
08:18:17.846
08:18:17.846 Using WinPCap Packet.DLL, version "4.1.0.2001" (1.0.4.1), driver version "4.1.0.2001" ...
08:18:17.846
08:18:17.846 Using FishPack64.dll, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
08:18:17.846
08:18:17.846 Using TunTap64.dll, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
08:18:17.846
08:18:17.847 --------- The following relevant DosDevices are defined ---------
08:18:17.847
08:18:17.849 NPF_NdisWanBh
08:18:17.849 NPF_NdisWanIp
08:18:17.849 NPF_NdisWanIpv6
08:18:17.850 NPF_{18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.850 NPF_{5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.850 NPF_{620EB585-BDCC-43D5-A62A-FC9A85864CFC}
08:18:17.850 NPF_{71F897D7-EB7C-4D8D-89DB-AC80D9DD2270}
08:18:17.850 NPF_{78032B7E-4968-42D3-9F37-287EA86C0AAA}
08:18:17.850 NPF_{802389A0-9C1A-4C28-9099-BC7F2A90C31A}
08:18:17.850 NPF_{8E301A52-AFFA-4F49-B9CA-C79096A1A056}
08:18:17.850 NPF_{DF4A9D2C-8742-4EB1-8703-D395C4183F33}
08:18:17.850 NPF_{E43D242B-9EAB-4626-A952-46649FBB939A}
08:18:17.850 NPF_{FB5AA89A-5CF5-47E9-9437-5287F7DD3BE2}
08:18:17.850 {18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.850 {5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.850 {620EB585-BDCC-43D5-A62A-FC9A85864CFC}
08:18:17.850 {71F897D7-EB7C-4D8D-89DB-AC80D9DD2270}
08:18:17.850 {78032B7E-4968-42D3-9F37-287EA86C0AAA}
08:18:17.850 {802389A0-9C1A-4C28-9099-BC7F2A90C31A}
08:18:17.850 {8E301A52-AFFA-4F49-B9CA-C79096A1A056}
08:18:17.850 {DF4A9D2C-8742-4EB1-8703-D395C4183F33}
08:18:17.850 {E43D242B-9EAB-4626-A952-46649FBB939A}
08:18:17.850 {FB5AA89A-5CF5-47E9-9437-5287F7DD3BE2}
08:18:17.850
08:18:17.850 ------------------------- Network Information -------------------------
08:18:17.850
08:18:17.850 Host Name . . . . . . . . . : agxopmf00
08:18:17.850 Node Type . . . . . . . . . : Hybrid
08:18:17.850 DNS Servers . . . . . . . . : 172.20.3.19
08:18:17.850 172.20.3.54
08:18:17.850 IP Routing Enabled. . . . . : yes
08:18:17.850
08:18:17.850 Network Address Netmask Gateway Address Interface Metric
08:18:17.850 0.0.0.0 0.0.0.0 172.20.3.1 172.20.3.23 266
08:18:17.850 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 306
08:18:17.850 127.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 127.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 172.20.3.0 255.255.255.0 172.20.3.23 172.20.3.23 266
08:18:17.850 172.20.3.23 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 172.20.3.255 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 192.168.3.0 255.255.255.0 192.168.3.223 192.168.3.223 266
08:18:17.850 192.168.3.23 255.255.255.255 192.168.3.223 192.168.3.223 11
08:18:17.850 192.168.3.223 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850 192.168.3.255 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850 224.0.0.0 240.0.0.0 127.0.0.1 127.0.0.1 306
08:18:17.850 224.0.0.0 240.0.0.0 172.20.3.23 172.20.3.23 266
08:18:17.850 224.0.0.0 240.0.0.0 192.168.3.223 192.168.3.223 266
08:18:17.850 255.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 255.255.255.255 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 255.255.255.255 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850
08:18:17.850 Default gateway: 172.20.3.1
08:18:17.850
08:18:17.850 -------------------------- Detected Adapters --------------------------
08:18:17.850
08:18:17.857 AdapterName = NPF_{5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.857 Description = Intel(R) PRO/1000 MT Network Connection #2
08:18:17.857 PhysAddr = 00-50-56-AE-00-03
08:18:17.857 LinkType = NdisMedium802_3
08:18:17.857 MediaConnected = Yes
08:18:17.857 LinkSpeed = 1.0 Gbps
08:18:17.857 IPAddr = 192.168.3.223
08:18:17.857 IPAddrMask = 255.255.255.0
08:18:17.857 GatewayIPAddr = 0.0.0.0
08:18:17.857 dwIndex = 0x0000000D
08:18:17.857 Checksum offloading = no
08:18:17.857
08:18:17.859 AdapterName = NPF_{18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.859 PhysAddr = 00-50-56-AE-00-02
08:18:17.859 LinkType = NdisMedium802_3
08:18:17.859 MediaConnected = Yes
08:18:17.859 LinkSpeed = 1.0 Gbps
08:18:17.859 IPAddr = 172.20.3.23
08:18:17.859 IPAddrMask = 255.255.255.0
08:18:17.859 GatewayIPAddr = 172.20.3.1
08:18:17.859 dwIndex = 0x0000000B
08:18:17.859 Checksum offloading = no
08:18:17.859
*********************
Any suggestions are appreciated. thanks.

[Rocky]

Jeff

In order to give you the correct answer a little more information is needed.

Do have router in your network?
Does your host windows machine have a static IP address.
what is the LAN IP address of your router
What is the LAN IP address of the HOST (Windows) adapter
what is the subnet mask of your local network

All of the above please ---
Then the answer is very straight forward.

Roc



_____

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org] On
Behalf Of jsganino
Sent: Wednesday, May 30, 2012 8:07 PM
To: hercules-390-***@public.gmane.org
Subject: [hercules-390] Re: Getting networking to work with Hercules and
Windows 7






Jeff,

I'm a little out of my element here, because you are hosting this on a
Windows machine, but I think what you need to do is to give a real local IP

Post by Jeff
Hercules config
***********
# Ethernet adapter
# 04A0.2 CTCI 172.20.3.25 192.168.200.2
# can use the 172.20.3.239 address if this doesn't work
# Careful of these IP addresses!!!!!!!!!!!!!!!!!!!!
# 04A2.2 CTCI 192.168.3.23 172.20.3.23
# 04A2.2 CTCI 192.168.3.23 192.168.3.223
04a2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 0.0.0.0

Try

04A2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 192.168.3.223

Or

04A2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 192.168.3.24

(I just picked the .24 address assuming that you don't already use it.)

As I understand it, the CTCI interface sets up a "tun" device and routes a
IP (layer 3) point-to-point connection over it. So, your windows box winds
up acting like a router directing traffic to Hercules over the "tun" device
and traffic to the rest of the subnet over the ethernet device. I just
recently struggled with getting an LCS interface to work on a Linux box, but
there are posts in this list that describe successes with CTCI, so I'm sure
it can be done. The gentleman who wrote the TT32Test64.exe and
FishPack64.dll programs you are using visits this list occasionally (and
sometime even frequently) and knows the windows side of what you're trying
to do quite well. (Fish -- If you are reading this, and I have given Jeff
any bum steers, please jump in and correct me.)

Good Luck,

Jim

Post by Jeff
This is my first attempt to work with Hercules networking, so perhaps I am

missing something very obvious.

Post by Jeff
A little background - at first, I set up Hercules to connect to the

adapter at ip address 172.20.3.23 and used 172.20.3.239 as the ip of my
guest. I was able to ping back and forth between these two addresses, but
could not ping any other device on the network, nor could they ping my
guest. I had an idea that if I added a second network card, and gave it the
192.168.3.223 and assigned 192.168.3.23 to my guest, then I could add a
route statement in my router to make 192.168.x.x addresses come back to my
windows pc. This has not worked at all - I cannot even seem to get windows
to ping the guest any more, even though I am using the mac address option.
Anyway, here is what I have - any ideas would be appreciated....

Post by Jeff
*****************
*****************
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
Physical Address. . . . . . . . . : 00-50-56-AE-00-03
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.3.223(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
NetBIOS over Tcpip. . . . . . . . : Enabled
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-50-56-AE-00-02
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

fe80::6158:d3c6:e53c:d214%11(Preferred)

Post by Jeff
IPv4 Address. . . . . . . . . . . : 172.20.3.23(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.20.3.1
DHCPv6 IAID . . . . . . . . . . . : 234901590

00-01-00-01-16-D6-D6-5D-00-50-56-AE-00-02

Post by Jeff
DNS Servers . . . . . . . . . . . : 172.20.3.19
172.20.3.54
NetBIOS over Tcpip. . . . . . . . : Enabled
***********
Hercules config
***********
# Ethernet adapter
# 04A0.2 CTCI 172.20.3.25 192.168.200.2
# can use the 172.20.3.239 address if this doesn't work
# Careful of these IP addresses!!!!!!!!!!!!!!!!!!!!
# 04A2.2 CTCI 192.168.3.23 172.20.3.23
# 04A2.2 CTCI 192.168.3.23 192.168.3.223
04a2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 0.0.0.0
************
Guest definitions
************
DEVICE LCS4A2 CTCA 4A2
LINK LCS4A2 0 192.168.3.23 255.255.255.0 1480
ROUTE LCS4A2 192.168.3.0 255.255.255.0 192.168.3.223
* ROUTE LCS4A2 172.20.3.0 255.255.255.0 172.20.3.23
* ROUTE LCS4A2 172.20.3.19 255.255.255.0 172.20.3.23 1
* ROUTE LCS4A2 172.20.4.0 255.255.255.0 172.20.3.1 1
ROUTE LCS4A2 0.0.0.0 0.0.0.0 192.168.3.223 1
***********
output of tt32test64
***********

"64-bit Release version" ...

Post by Jeff
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories

(aka 'Fish' (David B. Trout)).

Post by Jeff
08:18:17.846
08:18:17.846 Running on Windows XP, version 6.1.7600
08:18:17.846
08:18:17.846 Using WinPCap Packet.DLL, version "4.1.0.2001" (1.0.4.1),

driver version "4.1.0.2001" ...

Post by Jeff
08:18:17.846

"64-bit Release version" ...

Post by Jeff
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories

(aka 'Fish' (David B. Trout)).

Post by Jeff
08:18:17.846
08:18:17.846 Using TunTap64.dll, version: "3.2.1.160" (3.2.1.160): "64-bit

Release version" ...

Post by Jeff
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories

(aka 'Fish' (David B. Trout)).

Post by Jeff
08:18:17.846
08:18:17.847 --------- The following relevant DosDevices are defined

---------

Post by Jeff
08:18:17.847
08:18:17.849 NPF_NdisWanBh
08:18:17.849 NPF_NdisWanIp
08:18:17.849 NPF_NdisWanIpv6
08:18:17.850 NPF_{18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.850 NPF_{5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.850 NPF_{620EB585-BDCC-43D5-A62A-FC9A85864CFC}
08:18:17.850 NPF_{71F897D7-EB7C-4D8D-89DB-AC80D9DD2270}
08:18:17.850 NPF_{78032B7E-4968-42D3-9F37-287EA86C0AAA}
08:18:17.850 NPF_{802389A0-9C1A-4C28-9099-BC7F2A90C31A}
08:18:17.850 NPF_{8E301A52-AFFA-4F49-B9CA-C79096A1A056}
08:18:17.850 NPF_{DF4A9D2C-8742-4EB1-8703-D395C4183F33}
08:18:17.850 NPF_{E43D242B-9EAB-4626-A952-46649FBB939A}
08:18:17.850 NPF_{FB5AA89A-5CF5-47E9-9437-5287F7DD3BE2}
08:18:17.850 {18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.850 {5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.850 {620EB585-BDCC-43D5-A62A-FC9A85864CFC}
08:18:17.850 {71F897D7-EB7C-4D8D-89DB-AC80D9DD2270}
08:18:17.850 {78032B7E-4968-42D3-9F37-287EA86C0AAA}
08:18:17.850 {802389A0-9C1A-4C28-9099-BC7F2A90C31A}
08:18:17.850 {8E301A52-AFFA-4F49-B9CA-C79096A1A056}
08:18:17.850 {DF4A9D2C-8742-4EB1-8703-D395C4183F33}
08:18:17.850 {E43D242B-9EAB-4626-A952-46649FBB939A}
08:18:17.850 {FB5AA89A-5CF5-47E9-9437-5287F7DD3BE2}
08:18:17.850
08:18:17.850 ------------------------- Network Information

-------------------------

Post by Jeff
08:18:17.850
08:18:17.850 Host Name . . . . . . . . . : agxopmf00
08:18:17.850 Node Type . . . . . . . . . : Hybrid
08:18:17.850 DNS Servers . . . . . . . . : 172.20.3.19
08:18:17.850 172.20.3.54
08:18:17.850 IP Routing Enabled. . . . . : yes
08:18:17.850
08:18:17.850 Network Address Netmask Gateway Address Interface Metric
08:18:17.850 0.0.0.0 0.0.0.0 172.20.3.1 172.20.3.23 266
08:18:17.850 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 306
08:18:17.850 127.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 127.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 172.20.3.0 255.255.255.0 172.20.3.23 172.20.3.23 266
08:18:17.850 172.20.3.23 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 172.20.3.255 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 192.168.3.0 255.255.255.0 192.168.3.223 192.168.3.223 266
08:18:17.850 192.168.3.23 255.255.255.255 192.168.3.223 192.168.3.223 11
08:18:17.850 192.168.3.223 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850 192.168.3.255 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850 224.0.0.0 240.0.0.0 127.0.0.1 127.0.0.1 306
08:18:17.850 224.0.0.0 240.0.0.0 172.20.3.23 172.20.3.23 266
08:18:17.850 224.0.0.0 240.0.0.0 192.168.3.223 192.168.3.223 266
08:18:17.850 255.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 255.255.255.255 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 255.255.255.255 255.255.255.255 192.168.3.223 192.168.3.223

266

Post by Jeff
08:18:17.850
08:18:17.850 Default gateway: 172.20.3.1
08:18:17.850
08:18:17.850 -------------------------- Detected Adapters

--------------------------

Post by Jeff
08:18:17.850
08:18:17.857 AdapterName = NPF_{5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.857 Description = Intel(R) PRO/1000 MT Network Connection #2
08:18:17.857 PhysAddr = 00-50-56-AE-00-03
08:18:17.857 LinkType = NdisMedium802_3
08:18:17.857 MediaConnected = Yes
08:18:17.857 LinkSpeed = 1.0 Gbps
08:18:17.857 IPAddr = 192.168.3.223
08:18:17.857 IPAddrMask = 255.255.255.0
08:18:17.857 GatewayIPAddr = 0.0.0.0
08:18:17.857 dwIndex = 0x0000000D
08:18:17.857 Checksum offloading = no
08:18:17.857
08:18:17.859 AdapterName = NPF_{18AE9690-8609-4CB1-851C-99726303F286}

PRO/1000 MT Network Connection

Post by Jeff
08:18:17.859 PhysAddr = 00-50-56-AE-00-02
08:18:17.859 LinkType = NdisMedium802_3
08:18:17.859 MediaConnected = Yes
08:18:17.859 LinkSpeed = 1.0 Gbps
08:18:17.859 IPAddr = 172.20.3.23
08:18:17.859 IPAddrMask = 255.255.255.0
08:18:17.859 GatewayIPAddr = 172.20.3.1
08:18:17.859 dwIndex = 0x0000000B
08:18:17.859 Checksum offloading = no
08:18:17.859
*********************
Any suggestions are appreciated. thanks.

[Non-text portions of this message have been removed]

[Harold Grovesteen]

I would add that on Windows, the IP address of the Hercules guest's
interface must be unique and part of the local subnet in use by the
Windows host system's LAN interface. The additional NIC card approach
will not work. Routing isn't really happening here even though you
might think so.

The Hercules guest must also use as its default gateway, the same IP
address as the Windows system uses.

You may need to add a route in the systems on your local LAN (for
example the local LAN's gateway) that the Windows host's IP address is
the route to the Hercules guest's IP address.

I suspect your initial issue is caused by your other system's not
knowing how to reach the Hercules guest or your Hercules guest not using
the local LAN's gateway as its gateway or both.

Harold Grovesteen

Post by jsganino
Jeff,

Post by Jeff
Hercules config
***********
# Ethernet adapter
# 04A0.2 CTCI 172.20.3.25 192.168.200.2
# can use the 172.20.3.239 address if this doesn't work
# Careful of these IP addresses!!!!!!!!!!!!!!!!!!!!
# 04A2.2 CTCI 192.168.3.23 172.20.3.23
# 04A2.2 CTCI 192.168.3.23 192.168.3.223
04a2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 0.0.0.0

Try
04A2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 192.168.3.223
Or
04A2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 192.168.3.24
(I just picked the .24 address assuming that you don't already use it.)
As I understand it, the CTCI interface sets up a "tun" device and routes a IP (layer 3) point-to-point connection over it. So, your windows box winds up acting like a router directing traffic to Hercules over the "tun" device and traffic to the rest of the subnet over the ethernet device. I just recently struggled with getting an LCS interface to work on a Linux box, but there are posts in this list that describe successes with CTCI, so I'm sure it can be done. The gentleman who wrote the TT32Test64.exe and FishPack64.dll programs you are using visits this list occasionally (and sometime even frequently) and knows the windows side of what you're trying to do quite well. (Fish -- If you are reading this, and I have given Jeff any bum steers, please jump in and correct me.)
Good Luck,
Jim

Post by Jeff
This is my first attempt to work with Hercules networking, so perhaps I am missing something very obvious.
A little background - at first, I set up Hercules to connect to the adapter at ip address 172.20.3.23 and used 172.20.3.239 as the ip of my guest. I was able to ping back and forth between these two addresses, but could not ping any other device on the network, nor could they ping my guest. I had an idea that if I added a second network card, and gave it the 192.168.3.223 and assigned 192.168.3.23 to my guest, then I could add a route statement in my router to make 192.168.x.x addresses come back to my windows pc. This has not worked at all - I cannot even seem to get windows to ping the guest any more, even though I am using the mac address option. Anyway, here is what I have - any ideas would be appreciated....
*****************
*****************
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
Physical Address. . . . . . . . . : 00-50-56-AE-00-03
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.3.223(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
NetBIOS over Tcpip. . . . . . . . : Enabled
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-50-56-AE-00-02
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6158:d3c6:e53c:d214%11(Preferred)
IPv4 Address. . . . . . . . . . . : 172.20.3.23(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.20.3.1
DHCPv6 IAID . . . . . . . . . . . : 234901590
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-D6-D6-5D-00-50-56-AE-00-02
DNS Servers . . . . . . . . . . . : 172.20.3.19
172.20.3.54
NetBIOS over Tcpip. . . . . . . . : Enabled
***********
Hercules config
***********
# Ethernet adapter
# 04A0.2 CTCI 172.20.3.25 192.168.200.2
# can use the 172.20.3.239 address if this doesn't work
# Careful of these IP addresses!!!!!!!!!!!!!!!!!!!!
# 04A2.2 CTCI 192.168.3.23 172.20.3.23
# 04A2.2 CTCI 192.168.3.23 192.168.3.223
04a2.2 CTCI -n 00-50-56-AE-00-03 192.168.3.23 0.0.0.0
************
Guest definitions
************
DEVICE LCS4A2 CTCA 4A2
LINK LCS4A2 0 192.168.3.23 255.255.255.0 1480
ROUTE LCS4A2 192.168.3.0 255.255.255.0 192.168.3.223
* ROUTE LCS4A2 172.20.3.0 255.255.255.0 172.20.3.23
* ROUTE LCS4A2 172.20.3.19 255.255.255.0 172.20.3.23 1
* ROUTE LCS4A2 172.20.4.0 255.255.255.0 172.20.3.1 1
ROUTE LCS4A2 0.0.0.0 0.0.0.0 192.168.3.223 1
***********
output of tt32test64
***********
08:18:17.846 Begin TT32Test64.exe, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
08:18:17.846
08:18:17.846 Running on Windows XP, version 6.1.7600
08:18:17.846
08:18:17.846 Using WinPCap Packet.DLL, version "4.1.0.2001" (1.0.4.1), driver version "4.1.0.2001" ...
08:18:17.846
08:18:17.846 Using FishPack64.dll, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
08:18:17.846
08:18:17.846 Using TunTap64.dll, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
08:18:17.846 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
08:18:17.846
08:18:17.847 --------- The following relevant DosDevices are defined ---------
08:18:17.847
08:18:17.849 NPF_NdisWanBh
08:18:17.849 NPF_NdisWanIp
08:18:17.849 NPF_NdisWanIpv6
08:18:17.850 NPF_{18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.850 NPF_{5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.850 NPF_{620EB585-BDCC-43D5-A62A-FC9A85864CFC}
08:18:17.850 NPF_{71F897D7-EB7C-4D8D-89DB-AC80D9DD2270}
08:18:17.850 NPF_{78032B7E-4968-42D3-9F37-287EA86C0AAA}
08:18:17.850 NPF_{802389A0-9C1A-4C28-9099-BC7F2A90C31A}
08:18:17.850 NPF_{8E301A52-AFFA-4F49-B9CA-C79096A1A056}
08:18:17.850 NPF_{DF4A9D2C-8742-4EB1-8703-D395C4183F33}
08:18:17.850 NPF_{E43D242B-9EAB-4626-A952-46649FBB939A}
08:18:17.850 NPF_{FB5AA89A-5CF5-47E9-9437-5287F7DD3BE2}
08:18:17.850 {18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.850 {5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.850 {620EB585-BDCC-43D5-A62A-FC9A85864CFC}
08:18:17.850 {71F897D7-EB7C-4D8D-89DB-AC80D9DD2270}
08:18:17.850 {78032B7E-4968-42D3-9F37-287EA86C0AAA}
08:18:17.850 {802389A0-9C1A-4C28-9099-BC7F2A90C31A}
08:18:17.850 {8E301A52-AFFA-4F49-B9CA-C79096A1A056}
08:18:17.850 {DF4A9D2C-8742-4EB1-8703-D395C4183F33}
08:18:17.850 {E43D242B-9EAB-4626-A952-46649FBB939A}
08:18:17.850 {FB5AA89A-5CF5-47E9-9437-5287F7DD3BE2}
08:18:17.850
08:18:17.850 ------------------------- Network Information -------------------------
08:18:17.850
08:18:17.850 Host Name . . . . . . . . . : agxopmf00
08:18:17.850 Node Type . . . . . . . . . : Hybrid
08:18:17.850 DNS Servers . . . . . . . . : 172.20.3.19
08:18:17.850 172.20.3.54
08:18:17.850 IP Routing Enabled. . . . . : yes
08:18:17.850
08:18:17.850 Network Address Netmask Gateway Address Interface Metric
08:18:17.850 0.0.0.0 0.0.0.0 172.20.3.1 172.20.3.23 266
08:18:17.850 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 306
08:18:17.850 127.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 127.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 172.20.3.0 255.255.255.0 172.20.3.23 172.20.3.23 266
08:18:17.850 172.20.3.23 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 172.20.3.255 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 192.168.3.0 255.255.255.0 192.168.3.223 192.168.3.223 266
08:18:17.850 192.168.3.23 255.255.255.255 192.168.3.223 192.168.3.223 11
08:18:17.850 192.168.3.223 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850 192.168.3.255 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850 224.0.0.0 240.0.0.0 127.0.0.1 127.0.0.1 306
08:18:17.850 224.0.0.0 240.0.0.0 172.20.3.23 172.20.3.23 266
08:18:17.850 224.0.0.0 240.0.0.0 192.168.3.223 192.168.3.223 266
08:18:17.850 255.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 306
08:18:17.850 255.255.255.255 255.255.255.255 172.20.3.23 172.20.3.23 266
08:18:17.850 255.255.255.255 255.255.255.255 192.168.3.223 192.168.3.223 266
08:18:17.850
08:18:17.850 Default gateway: 172.20.3.1
08:18:17.850
08:18:17.850 -------------------------- Detected Adapters --------------------------
08:18:17.850
08:18:17.857 AdapterName = NPF_{5635A39F-1145-4E4E-9A44-2C79D1D9CBF6}
08:18:17.857 Description = Intel(R) PRO/1000 MT Network Connection #2
08:18:17.857 PhysAddr = 00-50-56-AE-00-03
08:18:17.857 LinkType = NdisMedium802_3
08:18:17.857 MediaConnected = Yes
08:18:17.857 LinkSpeed = 1.0 Gbps
08:18:17.857 IPAddr = 192.168.3.223
08:18:17.857 IPAddrMask = 255.255.255.0
08:18:17.857 GatewayIPAddr = 0.0.0.0
08:18:17.857 dwIndex = 0x0000000D
08:18:17.857 Checksum offloading = no
08:18:17.857
08:18:17.859 AdapterName = NPF_{18AE9690-8609-4CB1-851C-99726303F286}
08:18:17.859 PhysAddr = 00-50-56-AE-00-02
08:18:17.859 LinkType = NdisMedium802_3
08:18:17.859 MediaConnected = Yes
08:18:17.859 LinkSpeed = 1.0 Gbps
08:18:17.859 IPAddr = 172.20.3.23
08:18:17.859 IPAddrMask = 255.255.255.0
08:18:17.859 GatewayIPAddr = 172.20.3.1
08:18:17.859 dwIndex = 0x0000000B
08:18:17.859 Checksum offloading = no
08:18:17.859
*********************
Any suggestions are appreciated. thanks.

------------------------------------
http://groups.yahoo.com/group/hercules-390
http://www.hercules-390.org
Yahoo! Groups Links

[John P. Hartmann]

Just to balance the view: I have here a 192.168.2.0/24 network with
Hercules running under CentOS.

I have a VM host via CTCI on tun0 device that has address 192.168.2.65 on
the LAN side which connects to a pair of CTCs that have IP 10.0.0.33 in my
VM system. In the Linux host, I enable IP forwarding. In other machines
on the network, I have to route add -host 10.0.0.33 gw 192.168.2.65 to
connect to the VM system for ftp &c.

Were the VM system instead to have, say, IP 192.168.2.31, I would enable
proxy arp in the hosting stack. This latter is preferable as no routing is
required in the local network, but means modifying my VM configuration.

The final wrinkle is that I create the /dev/tun with openvpn to create a
permanent tun0 tunnel; and configure tun0 with ifconfig at boot time. A
patch to CTC-CTCI.c lets me specify just tun0 as the tunnel and avoid using
hercifc.

Config file:

03e0.2 ctci tun0


[***@servus etc]# ifconfig tun0
tun0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.2.65 P-t-P:10.0.0.33 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:18769 errors:0 dropped:0 overruns:0 frame:0
TX packets:16026 errors:0 dropped:7 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1123080 (1.0 MiB) TX bytes:9139125 (8.7 MiB)

Post by Harold Grovesteen
**
I would add that on Windows, the IP address of the Hercules guest's
interface must be unique and part of the local subnet in use by the
Windows host system's LAN interface. The additional NIC card approach
will not work. Routing isn't really happening here even though you
might think so.

[Non-text portions of this message have been removed]

[Roger Bowler]

I create the /dev/tun with openvpn to create a permanent tun0
tunnel; and configure tun0 with ifconfig at boot time. A
patch to CTC-CTCI.c lets me specify just tun0 as the tunnel
and avoid using hercifc.
03e0.2 ctci tun0

John,

Am I understanding you to say that tuntap now allows the tun0 IP address to be configured at boot time? When Hercules CTCI was first designed, a major annoyance was that the tun interface did not exist until Hercules opened /dev/tun, and therefore you could not configure its address using rc.d scripts or whatever as you can with regular interfaces. It was for this reason that I had to invent hercifc which was never an entirely satisfactory solution.

If you can now preconfigure the tun interface then this is good news and I would be delighted to be able to retire hercifc. What version of Linux is required for this functionality?

Regards,
Roger Bowler
Hercules "the people's mainframe"

[John P. Hartmann]

Yes, Roger, you understand correctly. It has always been the case on
Linux, though I initially had to write my own utilities to open the tun0
device correctly. It really does not depend on the Kernel as long as it
has tun/tap. 2.4.20 with the enormous Alan Cox patch was probably when I
started.

The the major annoyance you refer to never existed; the premise that
Hercules must open tun0 is just not correct. Something must, of course;
openvpn was supposed to, and did somehow, but didn't get the flags correct,
so data would not flow. This required a separate unprivileged program (as
long as /dev/tun allows write access to other than root).

Put simply I have zero tolerance for setuid progams, even by such wizards
as the Herculians. Thus to use Hercules with networking I had to get round
the hercifc program. It took me a couple of days as this was my first
encounter with tun/tap.

Post by Roger Bowler
**
John,
Am I understanding you to say that tuntap now allows the tun0 IP address
to be configured at boot time? When Hercules CTCI was first designed, a
major annoyance was that the tun interface did not exist until Hercules
opened /dev/tun, and therefore you could not configure its address using
rc.d scripts or whatever as you can with regular interfaces. It was for
this reason that I had to invent hercifc which was never an entirely
satisfactory solution.
If you can now preconfigure the tun interface then this is good news and I
would be delighted to be able to retire hercifc. What version of Linux is
required for this functionality?
Regards,
Roger Bowler
Hercules "the people's mainframe"

[Non-text portions of this message have been removed]

[Roger Bowler]

Post by John P. Hartmann
The the major annoyance you refer to never existed; the premise
that Hercules must open tun0 is just not correct. Something
must, of course;

I guess you had better show me how you did it. Then we can get rid of hercifc once and for all.

Roger Bowler
Hercules "the people's mainframe"

[John P. Hartmann]

I posted the patch with explanation for Sandhawk. Harold?

Post by Roger Bowler
**
I guess you had better show me how you did it. Then we can get rid of
hercifc once and for all.
Roger Bowler
Hercules "the people's mainframe"

[Non-text portions of this message have been removed]

[Roger Bowler]

Post by John P. Hartmann
I posted the patch with explanation for Sandhawk. Harold?

I don't see anything. Did you push it to github?

Roger Bowler
Hercules "the people's mainframe"

[Jeff]

Here is the info Roc requested:

Yes I have a router - its address is 172.20.3.1
The host windows machine has a static ip of 172.20.3.23
The network subnet mask is 255.255.255.0

Based upon what I have read, I am removing the 192.168.3.xx addresses and going back to using the "normal" network addresses. Thanks for all of the suggestions so far.

Post by Roger Bowler

Post by John P. Hartmann
I posted the patch with explanation for Sandhawk. Harold?

I don't see anything. Did you push it to github?
Roger Bowler
Hercules "the people's mainframe"

[Rocky]

Jeff

I sent you a few files off-line to the Yahoo address.
jgarrett43 <mailto:jgarrett43-/***@public.gmane.org>

Let me know if they help
Roc

_____

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org] On
Behalf Of Jeff
Sent: Friday, June 01, 2012 5:22 AM
To: hercules-390-***@public.gmane.org
Subject: [hercules-390] Re: Getting networking to work with Hercules and
Windows 7




Here is the info Roc requested:

Yes I have a router - its address is 172.20.3.1
The host windows machine has a static ip of 172.20.3.23
The network subnet mask is 255.255.255.0

Based upon what I have read, I am removing the 192.168.3.xx addresses and
going back to using the "normal" network addresses. Thanks for all of the
suggestions so far.

Post by Roger Bowler

I posted the patch with explanation for Sandhawk. Harold?

I don't see anything. Did you push it to github?
Roger Bowler
Hercules "the people's mainframe"

[Non-text portions of this message have been removed]

[Roger Bowler]

Post by John P. Hartmann
I posted the patch with explanation for Sandhawk. Harold?

John,

Actually I am more interested in knowing how you configure an IP address into the tun interface at Linux boot time. Can you give a summary of what the procedure is?

Thanks and regards,
Roger Bowler
Hercules "the people's mainframe"

[John P. Hartmann]

Roger, I sent the information to your mailbox last night, but here goes too.

Remeber, this is Linux; not Windows.

Yes, the patch is peripheral; all it does is relax the scanning rules for
the CTCI device to leave the device alone. No substantial code change is
required to be rid of hercifcfg.

With the patch, CTCI devices in the configuration file then looks like this:

03e0.2 ctci tun0

I have this in rc.local to create the tunnel device:

openvpn --mktun --dev tun0 --group staff
ifconfig tun0 192.168.2.65 pointopoint 10.0.0.33
echo 1 >/proc/sys/net/ipv4/ip_forward

I also have this udev rule, but I am not convinced it is still
necessary as permissions are now more relaxed than they were when I
started with Hercules (or openvpn has been fixed in the meantime).

KERNEL=="tun", GROUP="staff", MODE="0660"

Post by Roger Bowler
**
Actually I am more interested in knowing how you configure an IP address
into the tun interface at Linux boot time. Can you give a summary of what
the procedure is?

[Non-text portions of this message have been removed]

[Roger Bowler]

Post by John P. Hartmann
Roger, I sent the information to your mailbox last night

Sorry I had not realised that the message you were referring to went back to April 30.

Got it now.

Roger Bowler

[Harold Grovesteen]

I have not gotten the patch into sandhawk, but anyone on the developer
list is free to do so. I have copied John's 30 April 2012 post from the
developer list below in case anyone is interested here. Some additional
information is included about how to use this with Linux.

What I like about John's solution is that it does not eliminate hercifc.
John's solution is dependent upon facilities available with the more
recent Linux versions that older Linux systems (and not necessarily all
that older) may not have or are not available on other Unix family
platforms (Mac's for example).

It is not clear to me that actual elimination of hercifc from Hercules
makes sense, although a Linux build does not need to be dependent upon
it.

Harold

Post by John P. Hartmann
I posted the patch with explanation for Sandhawk. Harold?

Post by Roger Bowler
**
I guess you had better show me how you did it. Then we can get rid of
hercifc once and for all.
Roger Bowler
Hercules "the people's mainframe"

The patch below avoids the use of a setuid program to configure a
tun/tap device on unix. Instead, the device can be defined and
configured at system boot.
The patch updates ctc_ctci.c. It was made with "git diff -b" to make
the size to be reviewed smaller. Once the patch is sorted out, I can
supply one that reformats properly.
The patch allows for just a single parameter on a CTCI device, the
name of the tunnel device, which must be created and configured
elsewhere, for example by openvpn.
The original two-parameter code is still in place and active.
03e0.2 ctci tun0
openvpn --mktun --dev tun0 --group staff
ifconfig tun0 192.168.2.65 pointopoint 10.0.0.33
echo 1 >/proc/sys/net/ipv4/ip_forward
I also have this udev rule, but I am not convinced it is still
necessary as permissions are now more relaxed than they were when I
started with Hercules (or openvpn has been fixed in the meantime).
KERNEL=="tun", GROUP="staff", MODE="0660"
1. I have used only the one-parameter form (I was never able to make
the two-parameter form work for me).
2. The code indicates that flags are acceptable, but they will not
have any effect (at least that is what I think) nor do I think they
are relevant.
3. Not tested with windows. Presumably not applicable either.
Should there be some #ifdef-ing?
diff --git a/ctc_ctci.c b/ctc_ctci.c
index d575133..25babdd 100644
--- a/ctc_ctci.c
+++ b/ctc_ctci.c
@@ -115,6 +115,7 @@ int CTCI_Init( DEVBLK* pDEVBLK, int argc, char
*argv[] )
int rc = 0; // Return code
int nIFFlags; // Interface flags
char thread_name[32]; // CTCI_ReadThread
+ int preconfigured = 0;
nIFFlags = // Interface flags
0
@@ -212,6 +213,7 @@ int CTCI_Init( DEVBLK* pDEVBLK, int argc, char
*argv[] )
pDevCTCBLK->szTUNCharName,
sizeof( pDevCTCBLK->pDEVBLK[1]->filename ) );
+ if (pDevCTCBLK->szTUNDevName[0]) preconfigured = 1;
rc = TUNTAP_CreateInterface( pDevCTCBLK->szTUNCharName,
IFF_TUN | IFF_NO_PI,
&pDevCTCBLK->fd,
@@ -230,6 +232,9 @@ int CTCI_Init( DEVBLK* pDEVBLK, int argc, char
*argv[] )
pDevCTCBLK->szTUNDevName, "TUN");
}
+ if (!preconfigured)
+ {
+
#if defined(OPTION_W32_CTCI)
// Set the specified driver/dll i/o buffer sizes..
@@ -308,6 +313,8 @@ int CTCI_Init( DEVBLK* pDEVBLK, int argc, char
*argv[] )
VERIFY( TUNTAP_SetFlags ( pDevCTCBLK->szTUNDevName, nIFFlags
) == 0 );
+ }
+
// Copy the fd to make panel.c happy
pDevCTCBLK->pDEVBLK[0]->fd =
pDevCTCBLK->pDEVBLK[1]->fd = pDevCTCBLK->fd;
@@ -1171,7 +1178,7 @@ static int ParseArgs( DEVBLK* pDEVBLK, PCTCBLK
pCTCBLK,
OPTRESET();
optind = 0;
// Check for correct number of arguments
- if( argc < 2 )
+ if( argc < 1 )
{
// "%1d:%04X CTC: incorrect number of parameters"
WRMSG(HHC00915, "E", SSID_TO_LCSS(pDEVBLK->ssid),
pDEVBLK->devnum );
@@ -1380,6 +1387,13 @@ static int ParseArgs( DEVBLK* pDEVBLK, PCTCBLK
pCTCBLK,
if( !pCTCBLK->fOldFormat )
{
+ if (1 == argc) /* Pre-configured net device
*/
+ {
+ strlcpy(pCTCBLK->szTUNDevName, argv[0],
sizeof(pCTCBLK->szTUNDevName));
+ argc--; argv++;
+ }
+ else
+ {
// New format has 2 and only 2 parameters (Though several
options).
if( argc != 2 )
{
@@ -1414,6 +1428,7 @@ static int ParseArgs( DEVBLK* pDEVBLK, PCTCBLK
pCTCBLK,
argc--; argv++;
}
+ }
else // if( pCTCBLK->fOldFormat )
{
#if !defined( OPTION_W32_CTCI )

[Harold Grovesteen]

To add to the message below...

Part of why I have not pushed it to the github repository is because I
have been thinking about how to accommodate the platforms that might not
support this and whether John's changes should be specific to Linux. I
have not really had much time to think about that. One view could be
that if the Linux facilities are not available and the configuration
file uses this feature (the configuration statement is different between
the hercifc vs. the no-hercifc approach) the interface will not work,
but I am don't like that approach either.

While the patch itself is very straight forward, how exactly it should
be incorporated under multiple platform considerations has not been that
clear to me.

Roger, feel free to move forward with this if you don't want to wait for
me to get to it. You may have some better ideas about how to integrate
it or feel that "as is" is fine. Experience may be the best answer for
the other platforms when this feature is made available.

Harold

Post by Harold Grovesteen
I have not gotten the patch into sandhawk, but anyone on the developer
list is free to do so. I have copied John's 30 April 2012 post from the
developer list below in case anyone is interested here. Some additional
information is included about how to use this with Linux.
What I like about John's solution is that it does not eliminate hercifc.
John's solution is dependent upon facilities available with the more
recent Linux versions that older Linux systems (and not necessarily all
that older) may not have or are not available on other Unix family
platforms (Mac's for example).
It is not clear to me that actual elimination of hercifc from Hercules
makes sense, although a Linux build does not need to be dependent upon
it.
Harold

Post by John P. Hartmann
I posted the patch with explanation for Sandhawk. Harold?

Post by Roger Bowler
**
I guess you had better show me how you did it. Then we can get rid of
hercifc once and for all.
Roger Bowler
Hercules "the people's mainframe"

The patch below avoids the use of a setuid program to configure a
tun/tap device on unix. Instead, the device can be defined and
configured at system boot.
The patch updates ctc_ctci.c. It was made with "git diff -b" to make
the size to be reviewed smaller. Once the patch is sorted out, I can
supply one that reformats properly.
The patch allows for just a single parameter on a CTCI device, the
name of the tunnel device, which must be created and configured
elsewhere, for example by openvpn.
The original two-parameter code is still in place and active.
03e0.2 ctci tun0
openvpn --mktun --dev tun0 --group staff
ifconfig tun0 192.168.2.65 pointopoint 10.0.0.33
echo 1 >/proc/sys/net/ipv4/ip_forward
I also have this udev rule, but I am not convinced it is still
necessary as permissions are now more relaxed than they were when I
started with Hercules (or openvpn has been fixed in the meantime).
KERNEL=="tun", GROUP="staff", MODE="0660"
1. I have used only the one-parameter form (I was never able to make
the two-parameter form work for me).
2. The code indicates that flags are acceptable, but they will not
have any effect (at least that is what I think) nor do I think they
are relevant.
3. Not tested with windows. Presumably not applicable either.
Should there be some #ifdef-ing?
diff --git a/ctc_ctci.c b/ctc_ctci.c
index d575133..25babdd 100644
--- a/ctc_ctci.c
+++ b/ctc_ctci.c
@@ -115,6 +115,7 @@ int CTCI_Init( DEVBLK* pDEVBLK, int argc, char
*argv[] )
int rc = 0; // Return code
int nIFFlags; // Interface flags
char thread_name[32]; // CTCI_ReadThread
+ int preconfigured = 0;
nIFFlags = // Interface flags
0
@@ -212,6 +213,7 @@ int CTCI_Init( DEVBLK* pDEVBLK, int argc, char
*argv[] )
pDevCTCBLK->szTUNCharName,
sizeof( pDevCTCBLK->pDEVBLK[1]->filename ) );
+ if (pDevCTCBLK->szTUNDevName[0]) preconfigured = 1;
rc = TUNTAP_CreateInterface( pDevCTCBLK->szTUNCharName,
IFF_TUN | IFF_NO_PI,
&pDevCTCBLK->fd,
@@ -230,6 +232,9 @@ int CTCI_Init( DEVBLK* pDEVBLK, int argc, char
*argv[] )
pDevCTCBLK->szTUNDevName, "TUN");
}
+ if (!preconfigured)
+ {
+
#if defined(OPTION_W32_CTCI)
// Set the specified driver/dll i/o buffer sizes..
@@ -308,6 +313,8 @@ int CTCI_Init( DEVBLK* pDEVBLK, int argc, char
*argv[] )
VERIFY( TUNTAP_SetFlags ( pDevCTCBLK->szTUNDevName, nIFFlags
) == 0 );
+ }
+
// Copy the fd to make panel.c happy
pDevCTCBLK->pDEVBLK[0]->fd =
pDevCTCBLK->pDEVBLK[1]->fd = pDevCTCBLK->fd;
@@ -1171,7 +1178,7 @@ static int ParseArgs( DEVBLK* pDEVBLK, PCTCBLK
pCTCBLK,
OPTRESET();
optind = 0;
// Check for correct number of arguments
- if( argc < 2 )
+ if( argc < 1 )
{
// "%1d:%04X CTC: incorrect number of parameters"
WRMSG(HHC00915, "E", SSID_TO_LCSS(pDEVBLK->ssid),
pDEVBLK->devnum );
@@ -1380,6 +1387,13 @@ static int ParseArgs( DEVBLK* pDEVBLK, PCTCBLK
pCTCBLK,
if( !pCTCBLK->fOldFormat )
{
+ if (1 == argc) /* Pre-configured net device
*/
+ {
+ strlcpy(pCTCBLK->szTUNDevName, argv[0],
sizeof(pCTCBLK->szTUNDevName));
+ argc--; argv++;
+ }
+ else
+ {
// New format has 2 and only 2 parameters (Though several
options).
if( argc != 2 )
{
@@ -1414,6 +1428,7 @@ static int ParseArgs( DEVBLK* pDEVBLK, PCTCBLK
pCTCBLK,
argc--; argv++;
}
+ }
else // if( pCTCBLK->fOldFormat )
{
#if !defined( OPTION_W32_CTCI )

[Roger Bowler]

Post by Harold Grovesteen
Part of why I have not pushed it to the github repository is
because I have been thinking about how to accommodate the
platforms that might not support this and whether John's
changes should be specific to Linux.

Harold,

I don't see any backward compatability problems with this change. If I am reading it right, existing configurations which specify an IP address on the CTCI definition will continue to work unchanged (they will still call hercifc). The mod just gives the user an additional choice of omitting the IP address, in which case hercifc is not called, and the user can optionally delete the hercifc executable. Obviously if you forget to pre-configure the tun interface with the IP address, then it won't work, but this doesn't seem a showstopper when there are already plenty of ways you can misconfigure things today.

Regards,
Roger Bowler
Hercules "the people's mainframe"

[Enrico Sorichetti]

Post by Roger Bowler
I don't see any backward compatability problems with this change. If I am reading it right, existing configurations which specify an IP address on the CTCI definition will continue to work unchanged (they will still call hercifc). The mod just gives the user an additional choice of omitting the IP address, in which case hercifc is not called, and the user can optionally delete the hercifc executable. Obviously if you forget to pre-configure the tun interface with the IP address, then it won't work, but this doesn't seem a showstopper when there are already plenty of ways you can misconfigure things today.
Regards,
Roger Bowler
Hercules "the people's mainframe"

it would be nice to surround the mods with the appropriate ifdefs,
for APPLE a different approach might be needed/more appropriate
as I already said to Harold reviewing networking for APPLE is at the top of my to do's
( IIRC the LCS stuff gives quite a bit of problems )

right now I am experimenting changing automatically at boot time
the /dev/tun and /dev/tap permissions, and it seems to work,
I only have to run more experiments for the overall stability of the approach.

it would be nice also to use the proper ifdefs for the priority stuff
if we run without the SETUID approach the priority changes will never succeed!
or even make it a configure option --enable/disable-change-priorities

running without the SETUID things will also fix the wrong attributes for the output files
created by the printer and cardpunch device drivers.

just meditating on it

cheers
Enrico

[M***@public.gmane.org]

Enrico,

Post by Enrico Sorichetti
running without the SETUID things will also fix the wrong attributes for the output files

created by the printer and cardpunch device drivers.

And it might fix the problem that causes this message

HHCCT047E 0E81: Error writing to tun0 Das Argument ist ung ltig

during startup of hercules in UBUNTU since above 8.04- which I "fixed"
by ignoring the condition that leads to the message in the code and
continue as if a zero was returned....

[Enrico Sorichetti]

Post by M***@public.gmane.org
Enrico,

Post by Enrico Sorichetti
running without the SETUID things will also fix the wrong attributes
for the output files

created by the printer and cardpunch device drivers.
And it might fix the problem that causes this message
HHCCT047E 0E81: Error writing to tun0 Das Argument ist ung ltig
during startup of hercules in UBUNTU since above 8.04- which I "fixed"
by ignoring the condition that leads to the message in the code and
continue as if a zero was returned....
--
Martin
Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE
more at http://www.picapcpu.de

Martin,
the current read/write tun error messages are HHC00911/HHC00912
so building a more recent <version> might fix the problem by other means
cheers
Enrico

[Harold Grovesteen]

Post by Enrico Sorichetti

Post by Roger Bowler
I don't see any backward compatability problems with this change. If I am reading it right, existing configurations which specify an IP address on the CTCI definition will continue to work unchanged (they will still call hercifc). The mod just gives the user an additional choice of omitting the IP address, in which case hercifc is not called, and the user can optionally delete the hercifc executable. Obviously if you forget to pre-configure the tun interface with the IP address, then it won't work, but this doesn't seem a showstopper when there are already plenty of ways you can misconfigure things today.
Regards,
Roger Bowler
Hercules "the people's mainframe"

it would be nice to surround the mods with the appropriate ifdefs,
for APPLE a different approach might be needed/more appropriate
as I already said to Harold reviewing networking for APPLE is at the top of my to do's
( IIRC the LCS stuff gives quite a bit of problems )

<snip>

Post by Enrico Sorichetti
cheers
Enrico

These were exactly my concerns. Not backward compatibility for Linux,
but Mac OSX. This is not at all a consideration for Windows.

Harold Grovesteen

[Enrico Sorichetti]

Post by Harold Grovesteen
These were exactly my concerns. Not backward compatibility for Linux,
but Mac OSX. This is not at all a consideration for Windows.
Harold Grovesteen

most probably for APPLE I found a different ( smarter ? , who knows ? ) way
to get rid completely of the SETUID stuff

I made 2 StartupItems to change on the fly the permissions for tun and tap devices to 666 at <boot> time

I did not take the time to test with an OS yet, but the devices were defined
and hercules was up and running

without the tweak I would get the usual message ... permission denied

I will keep investigating and if the solution is stable
I will commit the two StartupItems ( zipped directories )

cheers
Enrico

[John P. Hartmann]

Enrico, has OSX an ifconfig command? If so what does ifconfig -a report?

You need to create a tun0 device and configure it with an IP address. On
Linux, I use opnvpn to create tun0. Is there something similar on OSX?

**

These were exactly my concerns. Not backward compatibility for Linux,
but Mac OSX. This is not at all a consideration for Windows.
Harold Grovesteen

most probably for APPLE I found a different ( smarter ? , who knows ? )
way
to get rid completely of the SETUID stuff
I made 2 StartupItems to change on the fly the permissions for tun and tap
devices to 666 at <boot> time
I did not take the time to test with an OS yet, but the devices were defined
and hercules was up and running
without the tweak I would get the usual message ... permission denied
I will keep investigating and if the solution is stable
I will commit the two StartupItems ( zipped directories )
cheers
Enrico

[Non-text portions of this message have been removed]



------------------------------------

[Enrico Sorichetti]

Post by John P. Hartmann
Enrico, has OSX an ifconfig command? If so what does ifconfig -a report?
You need to create a tun0 device and configure it with an IP address. On
Linux, I use opnvpn to create tun0. Is there something similar on OSX?

Hi John,

under mac OSX the tun/tap <thingies> are defined thru the tun/tap kext extensions
written by Mattias Nissler

I <rebooted> a few times and with the StartupItems present
all the /dev/tun.. and /dev/tap.. devices had the permissions changed to 666

after that I added to my OS hercules configuration
"attach 0E20.2 3088 CTCI /dev/tun0 1500 192.168.0.202 192.168.0.201 255.255.255.255"

the devices were defined, opened ...
and after IPL I was able to ping the OS
ftp and tn3270 are still giving some problems, but I am not in a hurry to solve them!

seems a simple enough approch

cheers
Enrico

P.S.
that' s the way other tools do it, wireshark does it for /dev/bpf..

[Gavin Eadie]

Post by Enrico Sorichetti
I made 2 StartupItems to change on the fly the permissions for tun and tap devices to 666 at <boot> time

... don't use StartupItems [1], they're deprecated. Use launchd [2] instead .. Gavin

[1] http://developer.apple.com/library/mac/#documentation/Darwin/Reference/Manpages/man8/SystemStarter.8.html
[2] http://developer.apple.com/library/mac/#documentation/Darwin/Reference/Manpages/man8/launchd.8.html

for much detail: http://www.afp548.com/article.php?story=20050620071558293

[Enrico Sorichetti]

Post by Gavin Eadie

Post by Enrico Sorichetti
I made 2 StartupItems to change on the fly the permissions for tun and tap devices to 666 at <boot> time

... don't use StartupItems [1], they're deprecated. Use launchd [2] instead .. Gavin
[1] http://developer.apple.com/library/mac/#documentation/Darwin/Reference/Manpages/man8/SystemStarter.8.html
[2] http://developer.apple.com/library/mac/#documentation/Darwin/Reference/Manpages/man8/launchd.8.html
for much detail: http://www.afp548.com/article.php?story=20050620071558293

Hi Gavin,

I had already noticed that, but ...
tuntap already uses the deprecated approach :))
I needed a dependency on tun/tap or properly on tun/ethertap
( without the dependency the tweak does not work )
found simpler for a POC to use the StartupItems approach

cheers
Enrico

PS.
right now I am investigating also why a thread is left hanging around at
hercules termination when a CTCI device is defined!