Opened 4 years ago

Last modified 3 years ago

#15296 new defect

bridge does not forward pakets to a specific wifi interface

Reported by: lynxis Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: kernel Version: Trunk
Keywords: bridge wifi lost forward Cc:


The bridge does not forward frames into one direction to a wifi interface.


1x AP (hostname: wlan / wdr4300 | rev39770)
1x router (hostname: rfa / wdr4300 / dhcp server)
1x hw switch (tplink 24port)

2.4ghz ->|AP <br-wlan/eth0.3> hw switch <br-wlan/eth0.3> router
5ghz ->|


A wifi station is connected to 5ghz network and tries to get a dhcp release. Dhcp discover is sent to the router 'rfa'. The router received the paket and send an offer back. The dhcp offer gets lost on the bridge br-wlan@wlan.

pcaps attached. You can see the paket is arrived on eth0.3@wlan, but not send to the wlan1(5ghz) nor wlan0.

The station can disconnect and reconnect - nothing changed. Other station also have this problem on that essid/interface. 2.4ghz which is connected to the same bridge is working!

cat /sys/devices/virtual/net/eth0.3/brport/port_no

cat /sys/devices/pci0000:00/0000:00:00.0/net/wlan1/brport/port_no

cat /sys/devices/platform/ar934x_wmac/net/wlan0/brport/port_no
port no mac addr        is local?   ageing timer
  2 00:24:d7:04:e2:60   no       104.64 < station
  3 3c:e0:72:xx:xx:xx   no        13.88
  1 64:70:02:3e:aa:a8   no         0.03 < router / dhcp
  3 78:e4:00:xx:xx:xx   no         0.42
  3 84:29:99:xx:xx:xx   no        29.46
  3 88:c6:63:xx:xx:xx   no       113.11
  3 a0:88:b4:xx:xx:xx   no         0.06
  1 a0:f3:c1:49:3a:4e   yes        0.00
  3 a0:f3:c1:49:3a:4f   yes        0.00
  2 a0:f3:c1:49:3a:50   yes        0.00


ubus call network.wireless down
ubus call network.wireless up

recover the AP/essid

Any thoughts how to debug this problem any further?

Attachments (6)

lazus.pcapng (2.3 KB) - added by lynxis 4 years ago.
wifi station
rfa.pcap (3.5 KB) - added by lynxis 4 years ago.
rfa dhcp server
wlan_brwlan.pcap (3.6 KB) - added by lynxis 4 years ago.
wlan_wlan1.pcap (1.9 KB) - added by lynxis 4 years ago.
wlan_eth03.pcap (3.6 KB) - added by lynxis 4 years ago.
wlan_wlan0.pcap (2.1 KB) - added by lynxis 4 years ago.

Download all attachments as: .zip

Change History (9)

Changed 4 years ago by lynxis

wifi station

Changed 4 years ago by lynxis

rfa dhcp server

Changed 4 years ago by lynxis


Changed 4 years ago by lynxis


Changed 4 years ago by lynxis

Changed 4 years ago by lynxis

comment:1 Changed 4 years ago by anonymous

I am seeing the same issue, and it is extremely annoying when it happens. However, there can also be days between it happening.

I just updated to r40420, and the issue is still there, unfortunately. Taking wifi down and up again fixes it (until it randomly happens again):

/sbin/wifi down
/sbin/wifi up

comment:2 Changed 4 years ago by anonymous

This issue is still there in the latest trunk. I'd really like to get it fixed, but it is a bit difficult to debug. Any suggestions for things to try the next time one of the clients experiences this?

From the client side (on Windows clients) the visible symptoms are that the connections gets the yellow rectangle saying that the connection is "Limited", due to the lack of an IP address. The client's DHCP request reaches the router as it should, but the offer never gets back to the client.

comment:3 Changed 3 years ago by anonymous

i have the same issue with latest trunk

Add Comment

Modify Ticket

as new .

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

Note: See TracTickets for help on using tickets.