Since 141.60 is directly connected to the VM stack, it's allowed to
proxy ARP for it, so 140.22 can answer for it. Somehow, the PC needs to
know that to get to 141.63, he has to go through 140.22. Either you need
A) a dynamic routing protocol running on VM 4.3 and your routers need to
accept updates from it, or B) you need to inject a static route in the
routers in the rest of the network pointing 192.168.141.* to
192.168.140.22. Option A is superior; Option B is probably what you'll
get from your network group.
________________________________
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Steve Gentry
Sent: Monday, November 28, 2005 12:16 PM
To: [email protected]
Subject: Linux network problem/question
Greetings. I'm trying to get from my pc, which is on a
different subnet, to a linux guest in an IFL via a hiper socket. I'm
not having much luck. So I wonder if someone could help me. When I ping
192.168.141.63, I get a Request Timeout. I can ping 192.168.141.60
from my pc and get a reply. The hipersocket chpids are attached to
their respective guests.
Thanks in advance.
Steve G.
</console>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
