Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#2286 - ath79 client mode fails when bridged #7186

Closed
openwrt-bot opened this issue May 15, 2019 · 6 comments
Closed

FS#2286 - ath79 client mode fails when bridged #7186

openwrt-bot opened this issue May 15, 2019 · 6 comments
Labels

Comments

@openwrt-bot
Copy link

Greybeard:

When client mode (plain client or WDS client) is bridged with a local interface on (so far) wr842v1/3 and archer c7 v5 the wifi link fails with the following log entries on the associated AP.

Thu May 9 14:13:17 2019 daemon.notice hostapd: ap1: WDS-STA-INTERFACE-ADDED ifname=ap1.sta1 sta_addr=b0:be:76:e9:d4:47
Thu May 9 14:13:17 2019 kern.info kernel: [11074.049392] br-lan: port 4(ap1.sta1) entered blocking state
Thu May 9 14:13:17 2019 kern.info kernel: [11074.055244] br-lan: port 4(ap1.sta1) entered listening state
Thu May 9 14:13:19 2019 kern.info kernel: [11076.132112] br-lan: port 4(ap1.sta1) entered learning state
Thu May 9 14:13:21 2019 kern.info kernel: [11078.211994] br-lan: port 4(ap1.sta1) entered forwarding state
Thu May 9 14:13:21 2019 kern.info kernel: [11078.217946] br-lan: topology change detected, propagating
Thu May 9 14:13:26 2019 daemon.info hostapd: ap1: STA b0:be:76:e9:d4:47 IEEE 802.11: deauthenticated due to local deauth request
Thu May 9 14:13:26 2019 kern.info kernel: [11082.850945] device ap1.sta1 left promiscuous mode
Thu May 9 14:13:26 2019 kern.info kernel: [11082.856048] br-lan: port 4(ap1.sta1) entered disabled state
Thu May 9 14:13:26 2019 daemon.err hostapd: nl80211: NL80211_ATTR_STA_VLAN (addr=b0:be:76:e9:d4:47 ifname=ap1 vlan_id=0) failed: -2 (No such file or directory)
Thu May 9 14:13:26 2019 daemon.notice hostapd: ap1: WDS-STA-INTERFACE-REMOVED ifname=ap1.sta1 sta_addr=b0:be:76:e9:d4:47

If the client isn't bridged then the connection is as expected.

Tried this on Truck last thursday 9th May (WST) and on OpenWrt SNAPSHOT r9992-86fd8cb with the same result.

Thread on forum discusses this further. [[https://forum.openwrt.org/t/ath79-client-mode-unwell-broken/36661|External Link]]

@openwrt-bot
Copy link
Author

sq-bb:

I think I ran into the same bug with a ramips (Netgear EX2700) device that is used as a simple wifi to ethernet bridge (with the wifi interface in 4addr mode). The device was unable to connect to its AP after being updated to a recent master build (having worked just fine on a previous build). I tracked the problem down to the kernel 4.14.114 bump and have since tested [[https://github.com//pull/2048|PR#2048]] from the openwrt github repo. This has resolved the problem, so if it is indeed the same bug, that PR may be a suitable fix. :)

@openwrt-bot
Copy link
Author

Greybeard:

@openwrt-bot
Copy link
Author

Greybeard:

wr703 wds wifi client link also fails when bridged with physical interface similar result to devices described above.

@openwrt-bot
Copy link
Author

@openwrt-bot
Copy link
Author

xback:

Should be fixed in latest master/18.06
Could you please test this and report back?

Thanks,

Koen

@openwrt-bot
Copy link
Author

Greybeard:

Tested with OpenWrt SNAPSHOT r10170-de1431b
On wr842 v1 & v3 wds clients and archer c7 v5 wds ap. reported issue appears to be resolved. Clients connected as expected and connection established ok an remained connected when bridged.
Rebooted all devices and connections established as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant