[ale] network setup problem

Jim Kinney jkinney at teller.physics.emory.edu
Fri Sep 1 17:06:59 EDT 2000


Output of netstat -nr on gateway machine:

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
170.140.111.3   0.0.0.0         255.255.255.255 UH        0 0          0
eth1
192.168.0.3     0.0.0.0         255.255.255.255 UH        0 0          0
eth0
170.140.111.0   0.0.0.0         255.255.255.192 U         0 0          0
eth1
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0
eth0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0
lo
0.0.0.0         170.140.111.62  0.0.0.0         UG        0 0          0
eth1


command used:

route add default gw 170.140.111.62

also added with linuxconf and control-panel gui's. Same result.

netstat -rn output from an internal machine:

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
192.168.0.7     0.0.0.0         255.255.255.255 UH        0 0          0
eth0
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0
eth0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0
lo
0.0.0.0         192.168.0.3     0.0.0.0         UG        0 0          0
eth0

I have since read more (RTFM man ping) and discovered ping -n (don't try
and resolve the IP address) and lo' an' behold, I can ping the other
internal boxes with default gateways. Somewhere along the way, ping
changed to default to use DNS. 

So my ping attempts fell on unresolving ears ( :) and were dropped. Since
these are all to be masqueraded I am adding them to a hosts file and all
works well normally.

<homer> Doh! </homer>

JimK
A much embarrassed admin who now has a better understanding of how things
go  `ping'  in the night.

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.





More information about the Ale mailing list