ethernet card error

Aaron Tustin (booboojan@yahoo.com)
Mon, 21 Jun 1999 16:00:52 -0700 (PDT)


Hello,

I wrote to this mailing list last night regarding
a problem with my LAN. I received many helpful
replies but I still was unable to isolate the problem.
Basically, my machine has two ethernet cards, eth0 and
eth1, with eth0 connected to a cable modem and eth1
connected to a LAN via an ethernet hub. I was unable
to communicate using TCP/IP with any of the other
computers on my LAN.

Today as a last resort I tried to switch the cables;
eth0 is now connected to the cablemodem and eth1 is
connected to the LAN. Then, I was able to reach the
LAN, but not the cablemodem. This led me to believe
that there is a problem with eth1. It is a LinkSys
Ether16 10BaseT ISA LAN card (Ne2000 compatible).
The card is PnP, so I had to use isapnp to configure
it, but initially I thought it was working fine because
it is detected at boot-up. Today, after switching
eth1 back to the LAN hookup, I rebooted and immediately
did "ifconfig":

eth1 Link encap:Ethernet HWaddr 00:40:05:70:79:0A
inet addr:192.168.100.101 Bcast:192.168.100.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x240

(For brevity I have omitted the eth0 and lo output).

I then tried to ping 192.168.100.84 (one of the other
computers on my LAN), which didn't work, and typed
"ifconfig" again.

eth1 Link encap:Ethernet HWaddr 00:40:05:70:79:0A
inet addr:192.168.100.101 Bcast:192.168.100.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x240

The only difference is that "errors" is now 1 rather
than 0.

I am at a loss as to what to do; again, eth0 works
perfectly whether it is talking to the cablemodem or
LAN, but eth1 doesn't seem to want to talk to either.
(Both cards work fine with Win 98). Can anyone
tell me why eth1 is detected and seems to initialize
properly, but is unable to function? Are there any
other diagnostics I can do to figure out what's going
on?

Thanks in advance,
Aaron Tustin
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu