Re: 2.0.17, routing tables screwed ?

Tyson D Sawyer (tyson@rwii.com)
Fri, 6 Sep 1996 04:56:55 -0400 (EDT)

I have seen some of this and it seems to relate to the arp system.
You will probably find that the "missing" host isn't in the kernel arp
tables and that making an entry by hand will get things going.

I have not found any pattern as to when this happens. It has only happened
a few times to me.

Ty

> bootes:/root # uname -a
> Linux bootes 2.0.17 #1 Thu Sep 5 09:05:52 MET DST 1996 i586
> bootes:/root # ifconfig
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
> RX packets:288 errors:0 dropped:0 overruns:0
> TX packets:288 errors:0 dropped:0 overruns:0
>
> sl0 Link encap:VJ Serial Line IP
> inet addr:10.0.0.254 P-t-P:10.0.0.250 Mask:255.0.0.0
> UP POINTOPOINT RUNNING MTU:296 Metric:1
> RX packets:2150 errors:0 dropped:0 compressed:2119
> TX packets:1349 errors:0 dropped:0 compressed:1322
>
> eth0 Link encap:10Mbps Ethernet HWaddr 00:A0:24:D2:81:C6
> inet addr:192.168.1.22 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:167 errors:0 dropped:0 overruns:0
> TX packets:346 errors:0 dropped:0 overruns:0
> Interrupt:10 Base address:0xe000
>
> bootes:/root # route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface 10.0.0.250 0.0.0.0 255.255.255.255 UH 0 0
> 3 sl0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0
> 2 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 2 lo bootes:/root # !tel
> telnet 192.168.1.1
> Trying 192.168.1.1...
> telnet: Unable to connect to remote host: No route to host
> bootes:/root #
>
> /herp