Intermittent disconnects using SXK80 in AP Mode with VLAN Tagging

[treasy]

Hello, I've been having a very frustrating problem with the orbi pros while in AP mode with VLAN tagging enabled.  I have done some research and have narrowed it down to a few log messages that I see only when VLAN tagging is enabled (and the dropouts occur)

[129650.768817] br-lan: port 9(ath2) received tcn bpdu
[129650.768845] br-lan: topology change detected, propagating
[129651.238617] br-lan: port 9(ath2) received tcn bpdu
[129651.238646] br-lan: topology change detected, propagating
[129652.352782] br-lan: port 9(ath2) received tcn bpdu
[129652.352813] br-lan: topology change detected, propagating
[129857.600694] br-lan: port 9(ath2) received tcn bpdu
[129857.600725] br-lan: topology change detected, propagating
[129886.923583] wlan: [15506:I:ANY] ieee80211_autoselect_infra_bss_channel: 3995: ACS started: vap:0xffffffc02a700000
[129887.224851] wlan: [10844:I:ANY] ieee80211_acs_scan_evhandler: 3732: lock held duration: 0(ms)
[129905.365917] eth5: PHY Link is down
[129905.366151] br-lan: port 5(eth5) entered disabled state
[129905.370683] br33: port 5(eth5.33) entered disabled state
[129905.374047] br40: port 5(eth5.40) entered disabled state
[129905.494759] wlan: [17111:I:ANY] ieee80211_autoselect_infra_bss_channel: 3995: ACS started: vap:0xffffffc02a700000
[129905.797014] wlan: [10844:I:ANY] ieee80211_acs_scan_evhandler: 3732: lock held duration: 0(ms)
[129906.365353] eth1: PHY Link up speed: 1000
[129906.365588] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[129906.368603] br-lan: port 1(eth1) entered listening state
[129906.374910] br-lan: port 1(eth1) entered listening state
[129906.380690] IPv6: ADDRCONF(NETDEV_CHANGE): eth1.33: link becomes ready
[129906.385884] br33: port 1(eth1.33) entered forwarding state
[129906.392008] br33: port 1(eth1.33) entered forwarding state
[129906.397946] IPv6: ADDRCONF(NETDEV_CHANGE): eth1.40: link becomes ready
[129906.403325] br40: port 1(eth1.40) entered forwarding state
[129906.409755] br40: port 1(eth1.40) entered forwarding state
[129908.365071] br-lan: port 1(eth1) entered learning state
[129910.364959] br-lan: topology change detected, propagating
[129910.365002] br-lan: port 1(eth1) entered forwarding state
[129914.587816] wlan: [17974:I:ANY] ieee80211_autoselect_infra_bss_channel: 3995: ACS started: vap:0xffffffc02a700000
[129914.889229] wlan: [10844:I:ANY] ieee80211_acs_scan_evhandler: 3732: lock held duration: 0(ms)
[129918.040451] kernel msg: ebtables bug: please report to author: Wrong nr of counters
[129918.080279] kernel msg: ebtables bug: please report to author: Wrong nr of counters
[129918.087063] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129918.177706] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129918.215567] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129929.365139] eth1: PHY Link is down
[129929.365602] br-lan: port 1(eth1) entered disabled state
[129929.367866] br33: port 1(eth1.33) entered disabled state
[129929.373367] br40: port 1(eth1.40) entered disabled state
[129940.365603] eth1: PHY Link up speed: 1000
[129940.365878] br-lan: port 1(eth1) entered listening state
[129940.368660] br-lan: port 1(eth1) entered listening state
[129940.374575] br33: port 1(eth1.33) entered forwarding state
[129940.379534] br33: port 1(eth1.33) entered forwarding state
[129940.385599] br40: port 1(eth1.40) entered forwarding state
[129940.390428] br40: port 1(eth1.40) entered forwarding state
[129942.364971] br-lan: port 1(eth1) entered learning state
[129944.364967] br-lan: topology change detected, propagating
[129944.365009] br-lan: port 1(eth1) entered forwarding state
[129947.093877] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129947.135427] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129947.150141] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129947.235367] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129947.523559] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129947.589810] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129966.275977] br-lan: port 9(ath2) received tcn bpdu
[129966.276011] br-lan: topology change detected, propagating
[129968.365420] eth1: PHY Link is down
[129968.365665] br-lan: port 1(eth1) entered disabled state
[129968.368112] br33: port 1(eth1.33) entered disabled state
[129968.373643] br40: port 1(eth1.40) entered disabled state
[129983.365090] eth1: PHY Link up speed: 1000
[129983.365613] br-lan: port 1(eth1) entered listening state
[129983.368122] br-lan: port 1(eth1) entered listening state
[129983.374036] br33: port 1(eth1.33) entered forwarding state
[129983.379009] br33: port 1(eth1.33) entered forwarding state
[129983.384800] br40: port 1(eth1.40) entered forwarding state
[129983.389951] br40: port 1(eth1.40) entered forwarding state
[129985.364959] br-lan: port 1(eth1) entered learning state
[129987.364967] br-lan: topology change detected, propagating
[129987.365013] br-lan: port 1(eth1) entered forwarding state
[129989.425511] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129989.442376] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129989.582130] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129989.680864] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129989.693419] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129989.700755] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129989.718554] kernel msg: ebtables bug: please report to author: Wrong nr. of counters requested
[129999.702191] br-lan: port 9(ath2) received tcn bpdu
[129999.702224] br-lan: topology change detected, propagating
[129999.793098] br-lan: port 9(ath2) received tcn bpdu
[129999.793126] br-lan: topology change detected, propagating
[130001.423266] br-lan: port 9(ath2) received tcn bpdu
[130001.423297] br-lan: topology change detected, propagating

I only ever see these errors when vlan tagging is enabled.  If there's no vlan tagging enabled, then the br-lan interface seems to have much fewer topology changes and dropouts cease.

I've got an open case with support but they claim the problem is "not reproducible"

Thanks

[treasy]

My network toplogy:

solid lines are physical media, dashed lines are wireless

firmware is 4.20.122

[RaghuHR]

Hi @treasy  Could you please upload the complete debug logs into cloud storage and send me a link download via PM. Please collect the logs from router and all satellites.

Thanks,

Raghu.

[JamesJohnson]

Was this resolved and if so may I ask how ?

We're experiencing the same thing...
A single physical connection between our pfSense router and SXR80 in AP mode in trunk mode.
That physical connection carries a default VLAN (1, aka untagged) and 3 others (10, 20, 40).

These 3 VLANs are assigned to Wifi1, 2 and 3 respectively (all different subnets).
Clients are intermittently being dropped and the only message we can see at the time is
<6>Dec 6 14:15:12 kernel: br-lan: port 7(ath2) received tcn bpdu
<6>Dec 6 14:15:12 kernel: br-lan: topology change detected, propagating

Apart from the intermittent drop outs everything else is working fine.

[justinhow1]

I am also having disconnection problems. Any news on this?

I have a 3 node 1 x SXR30 and 2 x SXS30 all system running V4.2.3.102. I have to reboot the WiFi Orbi's every two weeks or so as devices start dropping off the network. I am also using VLANs on the wifi network.

[justinhow1]

FYI  I back revved the firmware on all mt 3 SRX/SRS30 devices from V4.2.3.102 to V4.2.2.130 and the problem went away.

[hermesromeror]

Interesting, I might try that on my SXR80. Where did you get it? @justinhow1 

Thank you

[justinhow1]

Sorry for late reply I did not get notofied of reply.

If you did not find it, all the old revisions are available on Netgear website where you get the latest.

https://www.netgear.com/support/product/sxk30b3.aspx#download

I can't say I have no problems (now running V4.2.2.130) with devices having trouble connecting to the WiFi but it is less requently.

Still wish you could schedule a reboot every x weeks.

[hermesromeror]

Thank you..  I think im going to return my orbis. AP + Vlan is completely broken..  I've worked 2 times with the engineers in debugging sessions, no luck yet. They asked me to disable the "network isolation", it helped a bit but is still broken.  @RaghuHR @MrJoshW