On Fri, 2004-03-26 at 10:40, Peter E. Abresch Jr. - at Pepco wrote: > Like I said, I can ping 161.186.86.5 from 161.186.86.6 with no problems. I > CANNOT ping 161.186.86.6 from 161.186.86.5. An ifconfig ctc0 shows that > the RX PACKETS increases by 1 each time I issue a ping from z/OS. This led > me to believe that the pings were getting to Linux from z/OS but not > finding their way back. I use static routes for the CTCs on both Linux and > z/OS. To simplify, I deleted all routes except for the CTC route which is > as follows:
On z/OS, you must have an appropriate GATEWAY statement, saying that all traffic for 161.186.86.5 should go via CTC-whatever, or you wouldn't be able to ping Linux. > 161.186.86.4/30 dev ctc0 proto kernel scope link 161.186.86.6 > > I could not ping from z/OS. I added the following route and I can ping > Linux from z/OS via CTC all day long. > > 161.186.0.0/16 via 161.186.86.6 dec ctc0 scope link Try 161.186.86.6/32 via 161.186.86.5 and see what happens (that is, add a host route with no explicit dependence on the interface name), and after that try 0/0 via 161.186.86.6 to add a default route via z/OS. I'm always a little nervous about using device names rather than IP addresses to control routing. Adam ---------------------------------------------------------------------- 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
