Jill, It isn't that TCP/IP is "different in Linux." The requirement is that the routers that connect to your VM system have to know where to route packets. If the router isn't told that packets for 10.1.5.150 have to go through your VM TCP/IP stack, it will effectively drop them. How you accomplish this can be done a number of ways: static routes in the router, dynamic routing protocols to advertise the routes, etc. Alan Altmark gives a very good presentation on this topic at SHARE. Unfortunately I haven't been given a copy to post on the linuxvm.org site, or I would point you to it.
Mark Post -----Original Message----- From: Jill Grine [mailto:[EMAIL PROTECTED]] Sent: Friday, April 26, 2002 11:03 AM To: [EMAIL PROTECTED] Subject: TCPIP - VM Guest GATEWAY for VSE versus Linux Good morning all, Back again, but with a quick direct question. When we run VSE as a guest under VM, we code the TCP/IP GATEWAY statement for VM as follows: GATEWAY 10 = TR1 1500 0 10.1.5.130 10.1.1.120 CTCVSE 1500 HOST (10.1.1.120 is VM first hop) When I use the same syntax for Linux, it can't PING 10.1.1.120. 10.1.5.150 10.1.1.120 LNX1 1492 HOST I can ping the DNS server (10.1.3.140) and the linux machine 10.1.5.150. An earlier post said that we had to use a separate subnet for Linux, but a response said not so. The redbook Mark posted shows their Linux setup: HOME 9.12.14.155 WTSCVMT 9.12.9.178 LINUX5V GATEWAY 9.12.9.184 = LINUX5V 1500 HOST Is this the part we OS/390 folks were warned about with regards to TCPIP being different in Linux? The explanation for the VSE setup was that incoming packets would route to the VM TCP/IP stack (first hop), then get sent forward to VSE. Can someone clarify for SuSE running under VM as guest? Thanks as always, Jill Grine
