how to check an ne2000 compatible card
Georgios Vetoulis
vetoulis@ne.mediaone.net
Tue Apr 25 00:21:42 2000
Hi,
I have had for several months now a stable setup consisting of
a redhat 6.[01] machine having on eth0 a 3com PCI card connected to a cable
modem, and on eth1 an ISA linksys working with the ne driver, and supporting
my LAN, consisting of various windows machines.
(I know I should have the ISA card on the cable modem...)
Anyway, I have been running all the ip masquerading, samba etc. services
with no problems. In the last month though, the LAN setup has become
unreliable, and I cannot guess what happens. Especially, since I did
not do anything to the redhat machine configuration.
IN particular, if the linux machine experiences high loads, the windows
machines behind it, cannot even ping it, and the linux machine itself
fails to ping them too. The connection to the outside world is fine.
The windows machines see each other fine, so I exclude them as problem
areas. I have changed the cables between the machines, and the problems
continue, so the hub and the cables must be OK.
Eventually, after several hours things start working again, only to fail
mysteriously again.
Pinging gives things like
Buffers Files Tools Edit Search Help
From: Georgios Vetoulis <vetoulis@ne.mediaone.net>
To: linux-vortex-bug@beowulf.gsfc.nasa.gov
Cc:
Bcc:
Subject: how to check an ne2000 compatible card
Reply-To: vetoulis@ne.mediaone.net
X-Agnohsteme: axapneis
Hi,
I have had for several months now a stable setup consisting of
a redhat 6.[01] machine having on eth0 a 3com PCI 100Mbs card connected to a
cable modem.
On eth1 I have an ISA 10Mbs linksys working with the ne driver, and supporting
my LAN, consisting of various windows machines.
(I know I should have the ISA card on the cable modem...)
Anyway, I have been running all the ip masquerading, samba etc. services
with no problems. In the last month though, the LAN setup has become
unreliable, and I cannot guess what happens. Especially, since I did
not do anything to the redhat machine configuration.
IN particular, if the linux machine experiences high disk activity, the windows
machines behind it, cannot even ping it, and the linux machine itself
fails to ping them too. The connection to the outside world is fine.
The windows machines see each other fine, so I exclude them as problem
areas. I have changed the cables between the machines, and the problems
continue, so the hub and the cables must be OK.
Eventually, after several hours things start working again, only to fail
mysteriously again later.
ping 192.168.0.3 gives
>From AXAPNEIS (192.168.0.1): Destination Host Unreachable
and the corresponding LED on the hub blinks.
Pinging the linux machine from a windows machine inside the LAN, gives
timeouts, while the corresponding LED for the windows machine blinks.
This is an excerpt from tcpdump
192.168.0.1 192.168.0.3
00:18:46.158729 lo < AXAPNEIS > AXAPNEIS: icmp: host dag unreachable [tos 0xc0]
00:18:46.158750 lo < AXAPNEIS > AXAPNEIS: icmp: host dag unreachable [tos 0xc0]
00:18:46.161150 eth1 > arp who-has dag tell AXAPNEIS (0:40:5:6c:f6:d8)
00:18:47.158643 eth1 > arp who-has dag tell AXAPNEIS (0:40:5:6c:f6:d8)
The ifconfig for eth1 gives
eth1 Link encap:Ethernet HWaddr 00:40:05:6C:F6:D8
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:1228 dropped:0 overruns:0 frame:0
TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x240
Note the RX errors... I transmit but do not receive..
and routing is
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 AXAPNEIS 255.255.255.0 UG 0 0 0 eth1
x.y.z.0 * 255.255.252.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default x.y.z.1 0.0.0.0 UG 0 0 0 eth0
Is this enough to make me go out and buy a new ISA card for eth1?
Thanks for any help..
--
G. Vetoulis
-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-vortex-bug-request@beowulf.org