Linux Ethernet Bridging - Mar 2008 - [Bridge] router interface errors

Hi

 

I have created a simple bridge with 6 interfaces and connected it in between
a router and a switch. In the router fastEthernet interface I can see errors
with CRC. Also in the bridge interfaces like below.

 

eth5      Link encap:Ethernet  HWaddr 00:10:F3:11:43:AC  

          inet6 addr: fe80::210:f3ff:fe11:43ac/64 Scope:Link

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:142300474 errors:0 dropped:0 overruns:0 frame:0

          TX packets:156954048 errors:1040733 dropped:0 overruns:0
carrier:1040733

          collisions:2070157 txqueuelen:100 

          RX bytes:2942761069 (2.7 GiB)  TX bytes:3367976736 (3.1 GiB)

          Base address:0xb000 Memory:df100000-df120000 

 

eth6      Link encap:Ethernet  HWaddr 00:10:F3:11:43:AD  

          inet6 addr: fe80::210:f3ff:fe11:43ad/64 Scope:Link

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:157287078 errors:0 dropped:0 overruns:0 frame:0

          TX packets:142138508 errors:620885 dropped:0 overruns:0
carrier:620885

          collisions:3261727 txqueuelen:100 

          RX bytes:3390946046 (3.1 GiB)  TX bytes:2932101998 (2.7 GiB)

          Base address:0xb400 Memory:df140000-df160000 

 

In some environment the switch side is ok. But the router side is always
gives errors like above. There was ebtables enabled and I disabled it in
/proc/sys/net/bridge/bridge-nf* files by putting 0. Is this the problem or
are there anything else.
 
Thanks

 

 

signature

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.linux-foundation.org/pipermail/bridge/attachments/20080326/22e7924e/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 12607 bytes
Desc: not available
Url :
http://lists.linux-foundation.org/pipermail/bridge/attachments/20080326/22e7924e/attachment.jpeg

At 21:09 yesterday, thusitha wrote:
>          TX packets:156954048 errors:1040733 dropped:0 overruns:0
> carrier:1040733
>          TX packets:142138508 errors:620885 dropped:0 overruns:0
> carrier:620885
That's unrelated to the bridging driver.  Bad network cable / NIC? 
Mismatched duplex?

-- 
Malcolm Scott
Research Assistant
University of Cambridge Computer Laboratory