========================== 2.1.117 capture =======================
[root@hydra /root]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0
TX packets:0 errors:588 dropped:6 overruns:0
eth0 Link encap:Ethernet HWaddr 00:10:4B:36:9C:C0
inet addr:129.120.36.9 Bcast:129.120.36.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1431 errors:0 dropped:0 overruns:0
TX packets:0 errors:0 dropped:4 overruns:0
Interrupt:5 Base address:0xfcc0
[root@hydra /root]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
129.120.36.0 * 255.255.255.0 U 0 0 0 eth0
[root@hydra /root]# ping -c3 129.120.36.250
PING 129.120.36.250 (129.120.36.250): 56 data bytes
64 bytes from 129.120.36.250: icmp_seq=0 ttl=255 time=1.0 ms
64 bytes from 129.120.36.250: icmp_seq=1 ttl=255 time=1.2 ms
64 bytes from 129.120.36.250: icmp_seq=2 ttl=255 time=1.0 ms
--- 129.120.36.250 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.0/1.0/1.2 ms
=====================================================================
Nice, and exactly what I'd expect. But here's what happens with
2.1.120:
========================== 2.1.117 capture =======================
[root@hydra /root]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0
TX packets:0 errors:788 dropped:7 overruns:0
eth0 Link encap:Ethernet HWaddr 00:10:4B:36:9C:C0
inet addr:129.120.36.9 Bcast:129.120.36.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0
TX packets:0 errors:0 dropped:0 overruns:0
Interrupt:5 Base address:0xfcc0
[root@hydra /root]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
129.120.36.0 * 255.255.255.0 U 0 0 0 eth0
[root@hydra /root]# ping -c3 129.120.36.250
PING 129.120.36.250 (129.120.36.250): 56 data bytes
--- 129.120.36.250 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
=====================================================================
So the network card is up, a route for the 129.120.36.0 net is there,
but I can't ping the router on that subnet any more.
I've been playing with so many different kernel versions all day long
that I'm beginning to go cross-eyed, and I'm thinking I'm missing
something really obvious here. But from the above listings, it just
looks like the basic networking isn't working right for me in 2.1.120.
Any ideas?
--Steve Tate srt@cs.unt.edu
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/faq.html