On Friday, 03/26/2004 at 01:44 EST, "Peter E. Abresch Jr. - at Pepco" <[EMAIL PROTECTED]> wrote: > If I use the default route, I can ping. The default does not address the > 2nd CTC from another z/OS LPAR. If also causes problems with users coming > from the OSA connections. > > My goal is to run VIPA on Linux using Zebra and OSPFD. This allows the > Linux system to learn the default route. Of course this does not help us > if the ping is not going back to the way it came. > > I should not need the default route. Linux knows about network > 161.186.86.4/30 or as it stands now, 161.186.86.5/32. Why is Linux not > sending the packet back via this network route? Why is it not going back > the way it came? I am so confused. Maybe it is time for a beer :)
As I said before, those packets do not contain 161.186.86.5 as the origin IP address. They contain the associated z/OS VIPA address (because you have SOURCEVIPA active on z/OS). Route selection is based entirely on the routing table. There is no magic; if the Linux routing table does have an entry for your VIPA subnet or host, or a default route, pointing Linux in the right direction, the packet goes nowhere. The interface a ping request comes in on has no bearing on the interface chosen to return the ping response. BTW, I suggest looking at Quagga. Zebra and OSPFD are dead. And if you aren't actively running a routing daemon, you most certainly do need a default gateway spec. Don't worry - when you start up the routing daemon, it will override whatever you put in there. Alan Altmark Sr. Software Engineer IBM z/VM Development ---------------------------------------------------------------------- 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
