Modify

Opened 10 years ago

Closed 8 years ago

#2674 closed defect (fixed)

AR7: acx-mac80211 - Bridging wireless with lan results in unusable networking

Reported by: heruan Owned by: florian
Priority: high Milestone:
Component: packages Version:
Keywords: ar7 Cc:

Description

Using eth0 and wlan0 separately works perfectly, but bridging these two interfaces leads to unusable networking:

root@OpenWrt:/$ brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.000d08000302       no              wlan0
                                                        eth0

root@OpenWrt:/$ ifconfig br0
br0       Link encap:Ethernet  HWaddr 00:XX:XX:XX:XX:02  
          inet addr:192.168.11.5  Bcast:192.168.11.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1386 (1.3 KiB)  TX bytes:1610 (1.5 KiB)

root@OpenWrt:/$ iwconfig wlan0
wlan0     IEEE 802.11b  ESSID:"Testing"  
          Mode:Managed  Frequency:2.422 GHz  Access Point: 00:XX:XX:XX:XX:27   
          Bit Rate=1 Mb/s   Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B   
          Encryption key:off
          Link Quality:28  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@OpenWrt:/$ ping 192.168.11.254
PING 192.168.11.254 (192.168.11.254): 56 data bytes
phy0: tx error 0x20, buf 07! (excessive Tx retries due to either distance too high or unable to Tx or Tx frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or 'retry')
phy0: tx error 0x20, buf 08! (excessive Tx retries due to either distance too high or unable to Tx or Tx frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or 'retry')
phy0: tx error 0x20, buf 09! (excessive Tx retries due to either distance too high or unable to Tx or Tx frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or 'retry')

Notice that removing eth0 from the bridge resolves this issue, so wireless connectivity works well alone.

Attachments (0)

Change History (9)

comment:1 Changed 10 years ago by nbd

  • Resolution set to wontfix
  • Status changed from new to closed

Bridging a client mode interface does not work due to a limitation in 802.11
This is not acx-mac80211 specific

comment:2 Changed 10 years ago by nabcore

  • Resolution wontfix deleted
  • Status changed from closed to reopened

I'm seeing this master mode with the acx driver. I think one needs to do the following to fix it:

ebtables -t nat -A POSTROUTING -o wlan0 -j snat --to-src <macadress of wlan0> 

Will test this in a bit. Also see http://forums.gentoo.org/viewtopic-t-430571-highlight-wireless+nat.html

comment:3 Changed 10 years ago by nabcore

hmmm just tested it, it does not work :(

comment:4 Changed 10 years ago by nabcore

ok.... after looking at this for ages, I've concluded that for some random reason, when an acx interface is part of a bridge, it will bluntly rebroadcast traffic that it has just received that was meant for the other interface in the bridge. It also does this in cleartext, even if your network has WEP enabled... I've no idea why this happens, but here's an example:

rx: DATA/DataOnly time:1015985378 len:92 signal:44 SNR:0 macstat:83 phystat:10 phyrate:110 status:4
rx: 802.11 buf[92]: 
	08 41  (TO DS:1, FRom DS:0)
	02 01 
	00 12 0E 2A FC C3 (BSSID)
	00 0F B5 DC 1A F6 (Source address (desktop USB)
	00 0F B5 DB F6 8D (eth0 on DG834G(v2))
	60 08 
	AA AA 
	03 
	00 00 00 
	08 00
	45 00 00 3C C2 E3 00 00 80 01 F6 1B (IP stuff)
	C0 A8 00 70 (source IP 192.168.0.112)
	C0 A8 00 01 (target IP 192.168.0.1)
	08 (ping)
	00 (code 0)
	49 5C (checksum)
	03 00 (identifier)
	01 00 (sequence number)
	61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69 (data)

(** THIS IS WEIRD ****)
tx: pkt (DATA/DataOnly): len 92 rate 0001 status 4
tx: 802.11 [92]: 
	08 02 (TO DS:0, FRom DS:1)
	02 01 
	00 0F B5 DB F6 8D (destination) <---- Why is this coming out here!
	00 12 0E 2A FC C3 (BSSID)
	00 0F B5 DC 1A F6 (SA)
	60 08 
	AA AA 
	03 
	00 00 00 
	08 00
	45 00 00 3C C2 E3 00 00 80 01 F6 1B (IP stuff)
	C0 A8 00 70 (source IP 192.168.0.112)
	C0 A8 00 01 (target IP 192.168.0.1)
	08 (ping)
	00 (code 0)
	49 5C (checksum)
	03 00 (identifier)
	01 00 (sequence number)
	61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69 (data)

There is something wrong (that I've not worked out yet) with acx with respect to bridging. However... there is a REALLY simple fix:

ifconfig br-lan hw ether <MAC ADDRESS of the WLAN device>

This works.

comment:5 Changed 10 years ago by agb

  • Keywords ar7 added

comment:6 Changed 9 years ago by florian

  • Owner changed from developers to florian
  • Status changed from reopened to new

comment:7 Changed 8 years ago by florian

Can you check if r20015 fixed this?

comment:8 Changed 8 years ago by thepeople

  • Status changed from new to assigned

comment:9 Changed 8 years ago by florian

  • Resolution set to fixed
  • Status changed from assigned to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.