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 :) Alan Altmark <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 03/26/2004 01:24 PM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject: Re: CTC Route Problem On Friday, 03/26/2004 at 01:11 EST, "Peter E. Abresch Jr. - at Pepco" <[EMAIL PROTECTED]> wrote: > I made the change but still cannot ping from z/OS. Do you have a default route active? I noticed you have SOURCEVIPA active. That means the packets will have the VIPA address in them, not the CTC. Without a route entry, you're right, Linux won't know what to do. route add default gw 161.186.86.5 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 ---------------------------------------------------------------------- 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