* Re: [LARTC] Ethernet packet loss - frame errors
2006-10-13 8:26 [LARTC] Ethernet packet loss - frame errors Justin Schoeman
@ 2006-10-13 8:34 ` Andrei Sandu
2006-10-13 8:44 ` Justin Schoeman
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Andrei Sandu @ 2006-10-13 8:34 UTC (permalink / raw)
To: lartc
[-- Attachment #1.1: Type: text/plain, Size: 1280 bytes --]
Possibly the length of the cable ?
On 10/13/06, Justin Schoeman <justin@expertron.co.za> wrote:
>
> Hi all,
>
> I have the following problem. A Linux box configured as a bridge. One
> interface connects to the router via a crossover cable, the other
> connects to a switch via the cable that used to go to the router.
>
> Now I get the following:
>
> [root@localhost net]# ifconfig eth3
> eth3 Link encap:Ethernet HWaddr 00:03:2D:07:61:5D
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:1969134 errors:0 dropped:0 overruns:0 frame:176459
> TX packets:2186662 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:492595115 (469.7 Mb) TX bytes:579725462 (552.8 Mb)
> Interrupt:17
>
> eth3 is the interface that connects to the switch. As you can see, 1 in
> 10 rx packets are framing errors.
>
> What are possible causes for this? The cable is a constant, so is not
> likely to cause problems, so what else can possibly cause such a high
> number of frame errors?
>
> Any help appreciated.
>
> Thanks,
>
> Justin
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
[-- Attachment #1.2: Type: text/html, Size: 2094 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [LARTC] Ethernet packet loss - frame errors
2006-10-13 8:26 [LARTC] Ethernet packet loss - frame errors Justin Schoeman
2006-10-13 8:34 ` Andrei Sandu
@ 2006-10-13 8:44 ` Justin Schoeman
2006-10-13 19:10 ` Stephen Hemminger
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Justin Schoeman @ 2006-10-13 8:44 UTC (permalink / raw)
To: lartc
Andrei Sandu wrote:
> Possibly the length of the cable ?
It is a 5m cable. It is also the 'common' cable - it is unplugged from
the router and plugged into the bridge (the other side stays in the switch).
-justin
> On 10/13/06, *Justin Schoeman* <justin@expertron.co.za
> <mailto:justin@expertron.co.za>> wrote:
>
> Hi all,
>
> I have the following problem. A Linux box configured as a bridge. One
> interface connects to the router via a crossover cable, the other
> connects to a switch via the cable that used to go to the router.
>
> Now I get the following:
>
> [root@localhost net]# ifconfig eth3
> eth3 Link encap:Ethernet HWaddr 00:03:2D:07:61:5D
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:1969134 errors:0 dropped:0 overruns:0 frame:176459
> TX packets:2186662 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:492595115 ( 469.7 Mb) TX bytes:579725462 (552.8 Mb)
> Interrupt:17
>
> eth3 is the interface that connects to the switch. As you can see, 1 in
> 10 rx packets are framing errors.
>
> What are possible causes for this? The cable is a constant, so is not
> likely to cause problems, so what else can possibly cause such a high
> number of frame errors?
>
> Any help appreciated.
>
> Thanks,
>
> Justin
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl <mailto:LARTC@mailman.ds9a.nl>
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [LARTC] Ethernet packet loss - frame errors
2006-10-13 8:26 [LARTC] Ethernet packet loss - frame errors Justin Schoeman
2006-10-13 8:34 ` Andrei Sandu
2006-10-13 8:44 ` Justin Schoeman
@ 2006-10-13 19:10 ` Stephen Hemminger
2006-10-14 13:18 ` Justin Schoeman
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Stephen Hemminger @ 2006-10-13 19:10 UTC (permalink / raw)
To: lartc
On Fri, 13 Oct 2006 10:26:14 +0200
Justin Schoeman <justin@expertron.co.za> wrote:
> Hi all,
>
> I have the following problem. A Linux box configured as a bridge. One
> interface connects to the router via a crossover cable, the other
> connects to a switch via the cable that used to go to the router.
>
> Now I get the following:
>
> [root@localhost net]# ifconfig eth3
> eth3 Link encap:Ethernet HWaddr 00:03:2D:07:61:5D
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:1969134 errors:0 dropped:0 overruns:0 frame:176459
> TX packets:2186662 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:492595115 (469.7 Mb) TX bytes:579725462 (552.8 Mb)
> Interrupt:17
>
> eth3 is the interface that connects to the switch. As you can see, 1 in
> 10 rx packets are framing errors.
>
> What are possible causes for this? The cable is a constant, so is not
> likely to cause problems, so what else can possibly cause such a high
> number of frame errors?
>
> Any help appreciated.
>
> Thanks,
>
> Justin
>
What speed and driver?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [LARTC] Ethernet packet loss - frame errors
2006-10-13 8:26 [LARTC] Ethernet packet loss - frame errors Justin Schoeman
` (2 preceding siblings ...)
2006-10-13 19:10 ` Stephen Hemminger
@ 2006-10-14 13:18 ` Justin Schoeman
2006-10-16 14:09 ` Justin Schoeman
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Justin Schoeman @ 2006-10-14 13:18 UTC (permalink / raw)
To: lartc
Stephen Hemminger wrote:
> On Fri, 13 Oct 2006 10:26:14 +0200
> Justin Schoeman <justin@expertron.co.za> wrote:
>
>> Hi all,
>>
>> I have the following problem. A Linux box configured as a bridge. One
>> interface connects to the router via a crossover cable, the other
>> connects to a switch via the cable that used to go to the router.
>>
>> Now I get the following:
>>
>> [root@localhost net]# ifconfig eth3
>> eth3 Link encap:Ethernet HWaddr 00:03:2D:07:61:5D
>> UP BROADCAST MULTICAST MTU:1500 Metric:1
>> RX packets:1969134 errors:0 dropped:0 overruns:0 frame:176459
>> TX packets:2186662 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:492595115 (469.7 Mb) TX bytes:579725462 (552.8 Mb)
>> Interrupt:17
>>
>> eth3 is the interface that connects to the switch. As you can see, 1 in
>> 10 rx packets are framing errors.
>>
>> What are possible causes for this? The cable is a constant, so is not
>> likely to cause problems, so what else can possibly cause such a high
>> number of frame errors?
>>
>> Any help appreciated.
>>
>> Thanks,
>>
>> Justin
>>
>
> What speed and driver?
sky 2 driver, hardcoded for 100Mbps full duplex.
-justin
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [LARTC] Ethernet packet loss - frame errors
2006-10-13 8:26 [LARTC] Ethernet packet loss - frame errors Justin Schoeman
` (3 preceding siblings ...)
2006-10-14 13:18 ` Justin Schoeman
@ 2006-10-16 14:09 ` Justin Schoeman
2006-10-16 20:00 ` Stephen Hemminger
2006-11-01 19:47 ` Stephen Hemminger
6 siblings, 0 replies; 8+ messages in thread
From: Justin Schoeman @ 2006-10-16 14:09 UTC (permalink / raw)
To: lartc
OK - Just finished more testing, and it seems to be a bug in the sky2
driver...
ping -s 1450 -f xxx.xxx.xxx.xxx
works perfectly, but
ping -s 1500 -f xxx.xxx.xxx.xxx
fails 100% with all packets being logged as frame errors.
-justin
Justin Schoeman wrote:
> Hi all,
>
> I have the following problem. A Linux box configured as a bridge. One
> interface connects to the router via a crossover cable, the other
> connects to a switch via the cable that used to go to the router.
>
> Now I get the following:
>
> [root@localhost net]# ifconfig eth3
> eth3 Link encap:Ethernet HWaddr 00:03:2D:07:61:5D
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:1969134 errors:0 dropped:0 overruns:0 frame:176459
> TX packets:2186662 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:492595115 (469.7 Mb) TX bytes:579725462 (552.8 Mb)
> Interrupt:17
>
> eth3 is the interface that connects to the switch. As you can see, 1 in
> 10 rx packets are framing errors.
>
> What are possible causes for this? The cable is a constant, so is not
> likely to cause problems, so what else can possibly cause such a high
> number of frame errors?
>
> Any help appreciated.
>
> Thanks,
>
> Justin
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [LARTC] Ethernet packet loss - frame errors
2006-10-13 8:26 [LARTC] Ethernet packet loss - frame errors Justin Schoeman
` (4 preceding siblings ...)
2006-10-16 14:09 ` Justin Schoeman
@ 2006-10-16 20:00 ` Stephen Hemminger
2006-11-01 19:47 ` Stephen Hemminger
6 siblings, 0 replies; 8+ messages in thread
From: Stephen Hemminger @ 2006-10-16 20:00 UTC (permalink / raw)
To: lartc
On Sat, 14 Oct 2006 15:18:32 +0200
Justin Schoeman <justin@expertron.co.za> wrote:
> Stephen Hemminger wrote:
> > On Fri, 13 Oct 2006 10:26:14 +0200
> > Justin Schoeman <justin@expertron.co.za> wrote:
> >
> >> Hi all,
> >>
> >> I have the following problem. A Linux box configured as a bridge. One
> >> interface connects to the router via a crossover cable, the other
> >> connects to a switch via the cable that used to go to the router.
> >>
> >> Now I get the following:
> >>
> >> [root@localhost net]# ifconfig eth3
> >> eth3 Link encap:Ethernet HWaddr 00:03:2D:07:61:5D
> >> UP BROADCAST MULTICAST MTU:1500 Metric:1
> >> RX packets:1969134 errors:0 dropped:0 overruns:0 frame:176459
> >> TX packets:2186662 errors:0 dropped:0 overruns:0 carrier:0
> >> collisions:0 txqueuelen:1000
> >> RX bytes:492595115 (469.7 Mb) TX bytes:579725462 (552.8 Mb)
> >> Interrupt:17
> >>
> >> eth3 is the interface that connects to the switch. As you can see, 1 in
> >> 10 rx packets are framing errors.
> >>
> >> What are possible causes for this? The cable is a constant, so is not
> >> likely to cause problems, so what else can possibly cause such a high
> >> number of frame errors?
> >>
> >> Any help appreciated.
> >>
> >> Thanks,
> >>
> >> Justin
> >>
> >
> > What speed and driver?
>
> sky 2 driver, hardcoded for 100Mbps full duplex.
>
In that driver, frame errors come from receiving fragments. Fragments
are any packet shorter 64 bytes and has an invalid CRC.
These might occur if you have got a duplex mismatch.
--
Stephen Hemminger <shemminger@osdl.org>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [LARTC] Ethernet packet loss - frame errors
2006-10-13 8:26 [LARTC] Ethernet packet loss - frame errors Justin Schoeman
` (5 preceding siblings ...)
2006-10-16 20:00 ` Stephen Hemminger
@ 2006-11-01 19:47 ` Stephen Hemminger
6 siblings, 0 replies; 8+ messages in thread
From: Stephen Hemminger @ 2006-11-01 19:47 UTC (permalink / raw)
To: lartc
On Mon, 16 Oct 2006 16:09:50 +0200
Justin Schoeman <justin@expertron.co.za> wrote:
> OK - Just finished more testing, and it seems to be a bug in the sky2
> driver...
>
> ping -s 1450 -f xxx.xxx.xxx.xxx
>
> works perfectly, but
>
> ping -s 1500 -f xxx.xxx.xxx.xxx
>
> fails 100% with all packets being logged as frame errors.
>
> -justin
>
Do you have an MTU mismatch? If the sender assumes it can send
large packets, and the receiver doesn't expect them it might cause it.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
^ permalink raw reply [flat|nested] 8+ messages in thread