Hi
from what i can tell is the overun is because you have had a
buffer overrun on the network card
eg more data has been sent to the card from another computer than
the computer can process.
except you should not get 1 on the TX stats.
these are more common on a 486sx33 or so :)
eth0 Link encap:Ethernet HWaddr 00:A0:24:83:2E:15
inet addr:192.168.1.6 Bcast:255.255.255.0 Mask:255.255.255.0
inet6 addr: fe80::2a0:24ff:fe83:2e15/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:838304 errors:219 dropped:0 overruns:227 frame:219
TX packets:758826 errors:0 dropped:0 overruns:0 carrier:4
collisions:1443 txqueuelen:100
RX bytes:224044357 (213.6 Mb) TX bytes:124675867 (118.9 Mb)
Interrupt:5 Base address:0x220
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:145682 errors:0 dropped:0 overruns:0 frame:0
TX packets:145682 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11293779 (10.7 Mb) TX bytes:11293779 (10.7 Mb)
----- Original Message -----
From: "Casey Carter" <Casey@Carter.net>
To: <linux-net@vger.kernel.org>
Sent: Friday, December 07, 2001 7:45 PM
Subject: Re: How do I find the cause of these errors?
> That's one of the cool things about us Linux geeks. Show me a Windows
> user who will put effort into tracing down the source of 1 error in 11
> million packet transmissions...
>
> Kenneth Stephen wrote:
> > Hi,
> >
> > Here is the output of my ifconfig :
> >
> > eth0 Link encap:Ethernet HWaddr 00:20:78:05:EA:0B
> > inet addr:X.y.54.140 Bcast:X.Y.54.191 Mask:255.255.255.192
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:9162662 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:11040532 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:X.Y.19.1 Bcast:X.Y.19.31 Mask:255.255.255.224
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:613065 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:586288 errors:1 dropped:0 overruns:1 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:X.Y.19.2 Bcast:X.Y.19.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:42 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> >
> > The kernel used is 2.2.20 and the driver is (for both cards) the
> > tulip driver (Comet chip). Packet forwarding takes place between eth0
and
> > eth1. Given that the one error seems to be on the TX line for both
> > interfaces, it seems that the errors originated from this machine. Are
> > there any tools I could use / parameters for the driver which I could
set
> > to allow me to track down what is the cause of these errors?
> >
> > Thanks,
> > Kenneth
> >
> > -
> > : 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
> >
>
>
>
> --
> Casey Carter
> Casey@Carter.net
> ccarter@uiuc.edu
> AIM: cartec69
>
> -
> : 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
-
: 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
