The traceroute command will show you what path a packet will follow from one system to another. Use the -n switch to speed things up; that disables DNS lookups for all the IP addresses. (In your case that wouldn't be a big deal, but in the general case it can be.)
I would say that your IP network setup looks a little odd. Your HiperSocket IP addresses should not be in the same subnet as your OSA IP addresses. Given that they are, you would need to set up a host route, which means a 255.255.255.255 netmask. You really should change the HiperSocket IP addresses instead. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Tom Duerbusch Sent: Friday, December 29, 2006 1:48 PM To: [email protected] Subject: Re: routing verification Yes, both route and netstat -r shows the routing info. But really doesn't hit you over the head, on if a route is being used or not. At least with ifconfig, you can watch the RX and TX byte counts increment. As I said, the FTP from VSE was comming in over the hipersocket, but the replies were going back over the OSA. I would have never seen this problem if I used "route" or "netstat -r". And I just accidently stumbled over it when I left the ifconfig results up. (finally realized that the TX count for the hipersocket connection wasn't changing, but TX for ETH0 was....) Anyway, it seems like I'm having trouble setting up a static route, via hipersockets to my VSE machine. I do: yast network services routing Default gateway: 192.168.192.1 Select expert configuration Add Destination (for VSE) 192.168.192.7 Gateway for the hipersocket connection: 192.168.192.7 (coding a direct route? right?) Netmask: 255.255.255.0 Device: I select the hipersocket one. On the Linux console, I get: linux41:~ # Dec 29 12:43:45 linux41 ifdown-route: Error while excuting: Dec 29 12:43:45 linux41 ifdown-route: Command 'ip route del to 192.168.192.7/24 via 192.168.192.7 dev hsi0' returned: Dec 29 12:43:45 linux41 ifdown-route: RTNETLINK answers: Invalid argument Dec 29 12:43:45 linux41 ifdown-route: Configuration line: 192.168.192.7 192.168. 192.7 255.255.255.0 hsi-bus-ccw-0.0.2500 Dec 29 12:43:46 linux41 ifup-route: Error while excuting: Dec 29 12:43:46 linux41 ifup-route: Command 'ip route replace to 192.168.192.7/2 4 via 192.168.192.7 dev hsi0' returned: Dec 29 12:43:46 linux41 ifup-route: RTNETLINK answers: Invalid argument Dec 29 12:43:46 linux41 ifup-route: Configuration line: 192.168.192.7 192.168.19 2.7 255.255.255.0 hsi-bus-ccw-0.0.2500 Dec 29 12:43:55 linux41 kernel: hsi0: no IPv6 routers present The route command shows: route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.192.0 * 255.255.252.0 U 0 0 0 eth0 192.168.192.0 * 255.255.252.0 U 0 0 0 hsi0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default 192.168.192.1 0.0.0.0 UG 0 0 0 eth0 Not exactly what I wanted. I now seem to be routing 192.,168.192.0 over both interfaces. What I want is everything to go over the default (eth0) except for 192.168.192.7 which should go over hsi0 (hipersockets). What am I missing here? Thanks Tom Duerbusch THD Consulting (Happy New Year) ---------------------------------------------------------------------- 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
