[hercules-390] z/OS V1R10 Networking in Hercules/Hyperion

Discussion:

'Joachim B.' hercules4joachim@gmail.com [hercules-390]

2017-10-18 20:17:42 UTC

Hello user group,

as you may have noticed:
I am new here. And I have a few problems configuring TCP/IP in z/OS correctly.

First my environment and used software:
- Windows 10 64-bit: Windows-6.2.9200 x64
- Hyperion: 4.0.0.8873-SDL-ga36e0bbc
- Packet.dll (WinPCap): 4.1.0.2980
- FishPack64.dll: 3.5.1.4556
- TunTap64.dll (CTCI-WIN 64): 3.5.1.4556
- z/OS: 1.10 ADCD

My IP configuration:
- Windows 10 64bit: 192.168.178.20
- Hercules + z/OS: 192.168.178.111
- Gateway + Name Server: 192.168.178.1
- Printer: 192.167.178.2
- Other computer: 192.167.178.34

Hercules configuration line
0E20.2 CTCI -d 192.168.178.111 192.168.178.20

z/OS 1.10 configuration - ADCD.Z110S.TCPPARMS(PROFILE)
DEVICE CTC1 CTC E20
LINK CTC1L CTC 0 CTC1
HOME 192.168.178.111 CTC1L
GATEWAY
192.168.178.1 = CTC1L DEFAULTSIZE HOST
DEFAULTNET 192.168.178.1 CTC1L DEFAULTSIZE 0
START CTC1

z/OS 1.10 configuration - TCPIP.TCPIP.DATA
HOSTNAME ADCD
DOMAINORIGIN JOACHIMS.NET
NSINTERADDR 192.168.178.1

Hyperion starts fine and from Windows I can successfully ping *all*
systems stated above (.1/.2/.20/.34/.111).

Now my problems:
Problem #1 - I *cannot* ping the gateway (.1) from z/OS. I always get
a "Ping timed out" message.
Problem #2 - I *cannot* ping the Windows PC (.20) from z/OS. I get the
same "Ping timed out" message.
Problem #3 - I *cannot* reach the name server (maybe due to problem #1).

And now the amazing oddity:
I *can* ping the printer (.2), the other computer (.34), and also
Googles server (216.58.212.164).
I can also traceroute the Google server.

But: How can I get rid of the 3 problems?

Best regards
Joachim

João Reginato jb.reginato@gmail.com [hercules-390]

2017-10-18 20:33:03 UTC

Permalink

You are mixing 192.168 with 192.167

De: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Enviada em: quarta-feira, 18 de outubro de 2017 18:18
Para: hercules-***@yahoogroups.com
Assunto: [hercules-390] z/OS V1R10 Networking in Hercules/Hyperion

Hello user group,

as you may have noticed:
I am new here. And I have a few problems configuring TCP/IP in z/OS correctly.

First my environment and used software:
- Windows 10 64-bit: Windows-6.2.9200 x64
- Hyperion: 4.0.0.8873-SDL-ga36e0bbc
- Packet.dll (WinPCap): 4.1.0.2980
- FishPack64.dll: 3.5.1.4556
- TunTap64.dll (CTCI-WIN 64): 3.5.1.4556
- z/OS: 1.10 ADCD

My IP configuration:
- Windows 10 64bit: 192.168.178.20
- Hercules + z/OS: 192.168.178.111
- Gateway + Name Server: 192.168.178.1
- Printer: 192.167.178.2
- Other computer: 192.167.178.34

Hercules configuration line
0E20.2 CTCI -d 192.168.178.111 192.168.178.20

z/OS 1.10 configuration - ADCD.Z110S.TCPPARMS(PROFILE)
DEVICE CTC1 CTC E20
LINK CTC1L CTC 0 CTC1
HOME 192.168.178.111 CTC1L
GATEWAY
192.168.178.1 = CTC1L DEFAULTSIZE HOST
DEFAULTNET 192.168.178.1 CTC1L DEFAULTSIZE 0
START CTC1

z/OS 1.10 configuration - TCPIP.TCPIP.DATA
HOSTNAME ADCD
DOMAINORIGIN JOACHIMS.NET
NSINTERADDR 192.168.178.1

Hyperion starts fine and from Windows I can successfully ping *all*
systems stated above (.1/.2/.20/.34/.111).

Now my problems:
Problem #1 - I *cannot* ping the gateway (.1) from z/OS. I always get
a "Ping timed out" message.
Problem #2 - I *cannot* ping the Windows PC (.20) from z/OS. I get the
same "Ping timed out" message.
Problem #3 - I *cannot* reach the name server (maybe due to problem #1).

And now the amazing oddity:
I *can* ping the printer (.2), the other computer (.34), and also
Googles server (216.58.212.164).
I can also traceroute the Google server.

But: How can I get rid of the 3 problems?

Best regards
Joachim

'Joachim B.' hercules4joachim@gmail.com [hercules-390]

2017-10-22 15:11:45 UTC

Permalink

Hi again,

I think, this might be a bug in the CTCI-WIN software - it mixes MAC
adresses in special cases.

Constallation:
* IP = 192.168.178.1 - MAC 34:81:c4:08:89:0b - Gateway
* IP = 192.168.178.2 - MAC not relevant - Printer
* IP = 192.168.178.20 - MAC 00:23:54:10:4e:ba - Windows PC
* IP = 192.168.178.111 - MAC 02:00:5e:a8:b2:6f - z/OS
* IP = 216.58.210.4 - MAC not relevant - www.google.com

My test cases, using WireShark (v2.4.2) to inspect the network traffic.
---------------------------------------------------------------
Pinging the gateway (.1) from z/OS (.111) --- Time Out :-/
PING 192.168.178.1
Ethernet II, Src: 02:00:5e:a8:b2:6f (z/OS), Dst: 00:23:54:10:4e:ba (Win10)
IPv4, Src: 192.168.178.111, Dst: 192.168.178.1

Here you see the Win10's MAC as Destination.
Why is this packet routed to Win10 (.20) ???
---------------------------------------------------------------
Pinging the Win10 (.20) from z/OS (.111) --- Time Out :-/
PING 192.168.178.20
Ethernet II, Src: 34:81:c4:08:89:0b (Gateway), Dst: 00:23:54:10:4e:ba (Win10)
IPv4, Src: 192.168.178.111, Dst: 192.168.178.20

Here you see the Gateway's MAC as Source.
Why has this packet the Gateway's MAC as its Source ???
---------------------------------------------------------------
Pinging the printer (.2) from z/OS) .111 --- Works fine :-)
PING 192.168.178.2
Ethernet II, Src: 02:00:5e:a8:b2:6f (z/OS), Dst: 34:81:c4:08:89:0b (Gateway)
IPv4, Src: 192.168.178.111, Dst: 192.168.178.2
---------------------------------------------------------------
Pinging another PC (.34) from z/OS (.111) --- Works fine :-)
PING 192.168.178.34
Ethernet II, Src: 02:00:5e:a8:b2:6f (z/OS), Dst: 34:81:c4:08:89:0b (Gateway)
IPv4, Src: 192.168.178.111, Dst: 192.168.178.34
---------------------------------------------------------------
Pinging Google (216.58.210.4) from z/OS (.111) --- Works fine :-)
PING 216.58.210.4
Ethernet II, Src: 02:00:5e:a8:b2:6f (z/OS), Dst: 34:81:c4:08:89:0b (Gateway)
IPv4, Src: 192.168.178.111, Dst: 216.58.210.4
---------------------------------------------------------------

So I think, the function which creates packets is not working
correctly when it has to address the Gateway (.1) and/or the
Hercules/Hyperion host system (.20) directly.

For the first case I would expect
Ethernet II, Src: 02:00:5e:a8:b2:6f (z/OS), Dst: 34:81:c4:08:89:0b (Gateway)
IPv4, Src: 192.168.178.111 (z/OS), Dst: 192.168.178.1 (Gateway)

For the second case I would expect
Ethernet II, Src: 02:00:5e:a8:b2:6f (z/OS), Dst: 00:23:54:10:4e:ba (Win10)
IPv4, Src: 192.168.178.111 (z/OS), Dst: 192.168.178.20 (Win10)

However, these wrong Dst/Src data might be an explanation why z/OS
finally gets Time Outs: The return packets cannot be routed back
correctly.

I also checked the behaviour using TTTest64.exe:

Pinging the gateway (.1) from TTTest64.exe (192.168.178.113 /
02-00-5E-A8-B2-60) --- Works fine, too :-)
Ethernet II, Src: 02:00:5e:a8:b2:60 (TTest64), Dst: 34:81:c4:08:89:0b (Gateway)
IPv4, Src: 192.168.178.113, Dst: 192.168.178.1

Best regards
Joachim