Ethernet Bridge bogging out

finegan · 04-26-2004, 05:33 PM

Ethernet bridging using 2.6 and 2.4, same deal. eth0 is a Tulip card on a 100 BaseT network while wlan0 is an 802.11b prism2 card in a PLX adapter... so I'm bridging 11Mbs 802.11b and 802.3 100BaseT, is that a problem? If so, is it a correctable one? I can send little stuff over the bridge, print jobs, web pages etc... but anything streaming like an ssh session hangs when I try to send a lot over it... for instance: ls on a small dir is fine, but a "dmesg" poops out halfway through.

Here's the ifconfig to make things simpler:

Code:


br0       Link encap:Ethernet  HWaddr 00:00:E8:00:20:D1
          inet addr:192.168.0.7  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3152 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2222 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:251561 (245.6 Kb)  TX bytes:545599 (532.8 Kb)
 
eth0      Link encap:Ethernet  HWaddr 00:00:E8:00:20:D1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:246367 errors:235599 dropped:0 overruns:0 frame:236825
          TX packets:306 errors:0 dropped:0 overruns:0 carrier:0
          collisions:7 txqueuelen:1000
          RX bytes:92490149 (88.2 Mb)  TX bytes:34310 (33.5 Kb)
          Interrupt:10 Base address:0xe800
 
eth1      Link encap:Ethernet  HWaddr 00:D0:B7:BE:6E:26
          inet addr:64.32.160.171  Bcast:64.32.160.175  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1501 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1681 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:333116 (325.3 Kb)  TX bytes:197771 (193.1 Kb)
          Interrupt:11 Base address:0xef00
 
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:25 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1713 (1.6 Kb)  TX bytes:1713 (1.6 Kb)
 
wlan0     Link encap:Ethernet  HWaddr 00:03:2F:01:D6:97
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3286 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2449 errors:0 dropped:4 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:312084 (304.7 Kb)  TX bytes:680225 (664.2 Kb)
          Interrupt:9 Base address:0xee80

and some brctl:

Code:

root@tenacious:/etc/rc.d# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.0000e80020d1       no              eth0
                                                                      wlan0

Spanning tree on or off, same story.... and lastly iptables:

Code:

root@tenacious:/etc/rc.d# iptables -L
Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             anywhere
ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:ftp
ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:ssh
ACCEPT     all  --  anywhere             anywhere
ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:smtp
ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:http
ACCEPT     udp  --  anywhere             anywhere
ACCEPT     icmp --  anywhere             anywhere           icmp echo-reply
ACCEPT     icmp --  anywhere             anywhere           icmp destination-unreachable
ACCEPT     icmp --  anywhere             anywhere           icmp source-quench
ACCEPT     icmp --  anywhere             anywhere           icmp echo-request
ACCEPT     icmp --  anywhere             anywhere           icmp time-exceeded
ACCEPT     icmp --  anywhere             anywhere           icmp parameter-problem
ACCEPT     icmp --  anywhere             anywhere           icmp type 30
ACCEPT     all  --  anywhere             anywhere           state RELATED,ESTABLISHED
 
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  192.168.0.0/24       anywhere
ACCEPT     all  --  anywhere             anywhere           state RELATED,ESTABLISHED
ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:2222
ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:1111
 
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Any ideas?

Cheers,

Finegan

AutOPSY · 04-26-2004, 11:47 PM

use IPTABLES or bridging 1 or the other.
That is where you are running into problems.
I see 7 collisions and 32,000+ errors on eth0 .

For instance, I have an eth0 device facing the inetrnet, I have usb0 connected to usb0 on another machine, same as vlan only different.
I use iptables to forward packets between the eth0 and usb0 device, I essentially have 2 lans behind the router. without needing bridging.

atlesn · 04-27-2004, 10:41 AM

Flush all iptables entries, and disable it totally (also on boot). Does it work now? If not, try parprouted instead (also without iptables).

finegan · 04-28-2004, 12:13 AM

From what I had read iptables and bridging shouldn't barf like this, but I zeroed out the rules and brought it up on a clean boot just for giggles, then switched the eepro and the tulip because from what I've read also some cards don't bridge well... Same with both, errors pile up on the wired part of the bridge, and if anything the eepro100 shouldn't behave like that.

Then I got to thinking... So I read up on the hostap_X driver and bridging, go figure its in the driver readme, bumped into it from the bridging pages as well:

http://lists.osdl.org/mailman/htdig/...il/000293.html

And then from the readme, my firmware is too old. This is probably one of the first half-dozen or so of these cards ever made, WPC11 version 1, circa 2001. The card never handled being bridged too well and with older firmwares its even more buggedy... so I've got to find someone with a windows laptop... more fun.

I'll tell you how it goes.

Cheers,

Finegan

AutOPSY · 04-28-2004, 04:21 AM

#!/bin/sh

IPTABLES=/sbin/iptables

#All The lines below are NAT routing

# flush any old rules
$IPTABLES -F -t nat

# turn on NAT (IP masquerading for outgoing packets)
$IPTABLES -A POSTROUTING -t nat -o eth0 -j MASQUERADE

#turn on interface forwarding
$IPTABLES -A FORWARD -i eth1 -o eth0 -j ACCEPT
$IPTABLES -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT

# enable IP forwarding (of incoming packets)
echo 1 > /proc/sys/net/ipv4/ip_forward

-------end--------
This is my rc.ipmasq file, you may be utilizing a different setup, such as your Linux machine, is ONLY a router, in which case bridging is fine.