danik1956,
If you are using LAN scenario four as you state above, the linux network and the z/OS network are essentially two different networks, sharing one physical network adapter on your machine. While you could set them up to use different physical adapters by using the find_io command and assigning them accordingly, (as you have done,) in most situations, that is not needed since the network traffic will not likely exceed the capacity of most modern adapters.
Both the linux and the z/OS networks are exposed on your LAN. The linux network uses whatever IP address was assigned by your linux admin; either DHCP or by static IP. The z/OS network uses the IP address specified in your TCPIP.PROFILE dataset, 192.168.1.249 above. zPDT introduces a separate, dedicated network connection to allow communication from the host linux to the hosted z/OS on the same machine. This is the so called "tunnel" or TAP connection, your 10. address assigned above. The tunnel network is only used to allow host linux to talk to hosted OS on the same machine.
Some simple guidelines to live by when using TCP/IP on z/OS:
- if you can communicate inbound to z/OS, your HOST address is good.
- If you can communicate outbound from z/OS, your ROUTE statements are correct.
- If you have an application, (like FTP or RSED, or DRDA,) which does both, and your setup is not complete/ correct, you will likely see strange results.
Debug hints:
- If you are having problems, first step is to run the TSO HOMETEST command. This command will verify the HOSTNAME, DOMAINORIGIN, SEARCH, and NSINTERADDR TCPIP.DATA statements. HOMETEST will use the z/OS resolver to obtain the IP addresses assigned to the HOSTNAME and compare them to the HOME list specified in PROFILE.TCPIP. A warning message will be issued if any HOSTNAME IP addresses are missing from the HOME list. For details on the HOMETEST command, see IP System Administrator's Commands - SC27-3661.
- To verify valid ROUTE statements, the TSO TRACERTE command is useful for debugging various network problems. The TRACERTE command sends UDP requests with varying TTL (time-to-live) or hop count values and then waits for the routers between the local and remote hosts to send TTL-exceeded messages. If you hit an unknown or unverifiable host while traversing the routes, TRACERTE will issued an error message. Note there are many options for the TRACERTE command. Refer to IP System Administrator's Commands - SC27-3661 for details.
The above commands will not necessarily tell you exactly where the problems lie, however, they will offer some clues.
After reviewing your configuration above, I see one definite error and two things I would suggest you change.
- In your PROFILE.TCPIP, your ROUTE statement for the 192 network is incorrect. It should be: ROUTE 192.168.1.0 255.255.255.0 = ETH2 MTU 1492
-Again, in your PROFILE.TCPIP, your ROUTE statement for the 10. network, while technically correct, should probably be changed to avoid potential network conflicts. I recommend changing this:
ROUTE 10.0.0.0 255.0.0.0 = ETH1 MTU 1492 to this: ROUTE 10.1.1.0 255.255.255.0 = ETH1 MTU 1492
I have seen the above cause multiple conflicts.
- In your PROFILE.TCPIP you have ip address 192.168.1.254 assigned to your router. In general, host addresses in the 240-254 range are considered "experimental" and should not be used. 192.168.1.1 is a much better, and more standard choice.
RDzJohn (soon to be retired John)
RDzJohn