RE: [Wlug] weird ethernet problem...
here's what netstat -i gives me...
Thanks,
Tim.
Iface: eth0
mtu: 1500
met: 0
rx-ok: 0
rx-err: 0
rx-drp: 0
rx-ovr: 0
tx-ok: 0
tx-err: 0
tx-ovr: 3
flg: BMRU
-----Original Message-----
From: Charles R. Anderson [mailto:cra@WPI.EDU]
Sent: Thursday, May 30, 2002 10:51 AM
To: 'wlug@wlug.org'
Subject: Re: [Wlug] weird ethernet problem...
On Thu, May 30, 2002 at 10:08:52AM -0400, Keller, Tim wrote:
Tim.Keller> NETDEV WATCHDOG: eth0: transmit timed out status 7088 0c00 at
241/301
Tim.Keller> command 001c000
Tim.Keller>
Tim.Keller> the box has a Intel 10/100 Pro card running at 100 full duplex.
Is the port the card is plugged into also running at full duplex? If
autonegotiation is disabled on only one end of the link, you will have a
duplex mismatch since the other end will fall back to half duplex.
Always use autonegotiation on both ends, or on neither end.
Any other errors? What does netstat -i show?
Tim.Keller> I hooked up a win2k laptop configured it to the proper ip in the
DMZ and it
Tim.Keller> worked fine, so I know it's not the link.
Try running tcpdump or ethereal on the link. I usually use tcpdump to
write to a file, then copy it to my workstation and load it into ethereal
there:
server# tcpdump -i eth0 -s 1500 -w capture.pcap
(the -s 1500 makes sure it captures the whole ethernet frames)
I usually see these errors due to one of three reasons:
1. the netcard and/or driver is misconfigured (duplex, interrupt, etc.)
2. the netcard and/or driver is buggy or bad (usually seen on 3c503's :)
3. there is a TON of traffic on the network which is causing the card
to not be able to keep up with the reception and transmission of all
the packets.
--
Charles R. Anderson
On Thu, May 30, 2002 at 11:16:48AM -0400, Keller, Tim wrote:
Tim.Keller> here's what netstat -i gives me...
Tim.Keller> Thanks,
Tim.Keller> Tim.
Tim.Keller>
Tim.Keller> Iface: eth0
Tim.Keller> mtu: 1500
Tim.Keller> met: 0
Tim.Keller> rx-ok: 0
Tim.Keller> rx-err: 0
Tim.Keller> rx-drp: 0
Tim.Keller> rx-ovr: 0
Tim.Keller> tx-ok: 0
Tim.Keller> tx-err: 0
Tim.Keller> tx-ovr: 3
Tim.Keller> flg: BMRU
That's a strange netstat. I've never seen output formatted like that
before. tx-ovr (overruns) is the statistic to watch out for.
What does lspci -v -v say about your ethernet card? Any other relavent
dmesg output?
--
Charles R. Anderson
participants (2)
-
Charles R. Anderson
-
Keller, Tim