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#558 - 5GHz interface drops to channel 36 -- DFS? #5586
Comments
jch: No, this is not a duplicate. FS#506 is about DFS being disabled on the reporter's hardware. On my hardware, the DFS working fine, but it's never switching back to the original channel after seeing (what it interprets as) a radar pulse. DFS support for macVersion = 0x80, macRev = 0x2: enabled |
dlang: that sounds like "works as designed", it detected that there is radar operating on that channel, so it won't let you use it. The fact that the radar detection may be faulty is a different topic. |
sumpfralle: In this specific case (indoor channel 60 -> indoor channel 36) the (permanent) change is acceptable from the point of regulation and law. Sadly this switch also happens when trying to use an outdoor channel. In this case it is not allowed to use indoor channels, but nevertheless the outdoor->indoor switch can happen due to DFS. But this is a problem common for all DFS implementation (also proprietary ones). This topic is probably too broad for being handled within LEDE. Upstream (hostapd?) is probably the proper communication partner. |
jch: For what it's worth, I've now switched to a different channel (108), and this one sticks. (I'm still slightly puzzled by LEDE's behaviour, but the problem is solved for me. |
jch:
I'm running 17.01 on a WNDR3700v2. The 5Ghz interface is set up to use a 40MHz channel width on channel 60 (5300MHz). This channel requires DFS in my locale.
Once in a while, the router drops to channel 36; I attribute this to a DFS false positive. What is more, the router never recovers — it stays on channel 60 until I manually restart the WiFi interface.
I'm fine with the router switching to channel 36 on a DFS false positive — but shouldn't it recover at some point and switch back to channel 60? I could of course set up a cron job that restarts the WiFi at 4am every night, but that seems like a rather inelegant workaround.
The text was updated successfully, but these errors were encountered: