Hi,
Here is the output of 'ifconfig' that I am running (the real ip's have
been obfuscated) on my gateway (2.2.20pre9) :
eth0 Link encap:Ethernet HWaddr 00:20:78:05:EA:0B
inet addr:192.168.10.140 Bcast:192.168.10.191
Mask:255.255.255.192
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:60154532 errors:2 dropped:472 overruns:2 frame:2
TX packets:62565527 errors:1 dropped:0 overruns:1 carrier:0
collisions:0 txqueuelen:100
Interrupt:15 Base address:0xa000
eth1 Link encap:Ethernet HWaddr 00:03:6D:1C:E3:3F
inet addr:192.168.9.1 Bcast:192.168.9.31 Mask:255.255.255.224
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:51351501 errors:2 dropped:5 overruns:2 frame:2
TX packets:50714444 errors:2 dropped:0 overruns:2 carrier:0
collisions:0 txqueuelen:100
Interrupt:5 Base address:0x9000
eth1:0 Link encap:Ethernet HWaddr 00:03:6D:1C:E3:3F
inet addr:192.168.9.2 Bcast:192.168.9.31 Mask:255.255.255.224
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:5 Base address:0x9000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:1639 errors:0 dropped:0 overruns:0 frame:0
TX packets:1639 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
tr0 Link encap:16/4 Mbps Token Ring HWaddr 00:20:35:86:65:5A
inet addr:192.168.8.1 Bcast:192.168.8.31 Mask:255.255.255.224
UP BROADCAST RUNNING PROMISC MULTICAST MTU:2000 Metric:1
RX packets:42078661 errors:0 dropped:0 overruns:0 frame:0
TX packets:24478956 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0x9100
And here is the result of 'route -vn' :
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.9.0 0.0.0.0 255.255.255.224 U 0 0 0
eth1
192.168.8.0 0.0.0.0 255.255.255.224 U 0 0 0 tr0
192.168.10.128 0.0.0.0 255.255.255.192 U 0 0 0
eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0
eth1
0.0.0.0 9.3.54.129 0.0.0.0 UG 0 0 0
eth0
ip_forwarding is enabled and no firewalling is done. Here is the odd
part : if I ping 192.168.9.15, tcpdump shows me the echo request and echo
reply correctly. However, if I ping 192.168.9.16, the packets are seen on
the lo0 interface instead of the eth1 interface - as they should be. Its
almost as if the machine thinks that 192.168.9.16 is a local ip address.
Yes the interface errors on eth0 and eth1 are a matter of concern, but
I didnt think they have anything to do with this problem. Chances are that
I have cabling problems, and am investigating that too. For reference, here
are the boot messages that have to do with the cards in question :
Olympic.c v0.4.0 3/10/00 - Peter De Schrijver & Mike Phillips
tr0: IBM PCI tokenring card. I/O at 9100, MMIO at c4802000, LAP at
c4804000, using irq 9
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
eth0: ADMtek Centaur-P rev 17 at 0xa000, 00:20:78:05:EA:0B, IRQ 15.
eth1: ADMtek Centaur-P rev 17 at 0x9000, 00:03:6D:1C:E3:3F, IRQ 5.
Any ideas on why I am having this problem?
Thanks,
Kenneth Stephen
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
