-
Notifications
You must be signed in to change notification settings - Fork 41
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
5ghz network drops on R7800 #169
Comments
just happened again hostapd:
and dmesg
|
on further investigation, this appears to be a DFS event handling issue. Is that a hostapd problem? |
Maybe your system is just detecting radar and acting appropriately? Try using a non-dfs channel? Use smaller bandwidth in hopes that dodges whatever frequency DFS is detecting? |
I was on a static channel-which apparently kills the dynamic switching.
Seems to be functional on auto/160 as of right now. Will keep updated
…On Tue, Nov 3, 2020, 12:55 PM Ben Greear ***@***.***> wrote:
Maybe your system is just detecting radar and acting appropriately? Try
using a non-dfs channel? Use smaller bandwidth in hopes that dodges
whatever frequency DFS is detecting?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#169 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFNSCPEGH7X4FSWPYIJQLLSOA7XHANCNFSM4TGXGQHQ>
.
|
Yeah. that was the issue. My bad. |
@theAeon I'm having this exact same issue happening once in a blue moon on a similar hardware QCA9880. I have 3 mesh APs all on a non-DFS channel (149 in US) with 80Mhz width, running the latest Openwrt with the CT firmware. I'm not seeing that " hostapd: could not get valid channel" in my logs. How did you conclude that it was a hostapd issue? Switching to auto channel selection is not an option for me in this case. |
If I remember correctly I needed to enable verbose logging for hostapd.
…On Fri, Mar 26, 2021, 1:23 AM jonozzz ***@***.***> wrote:
@theAeon <https://github.com/theAeon> I'm having this exact same issue
happening once in a blue moon on a similar hardware QCA9880. I have 3 mesh
APs all on a non-DFS channel (149 in US) with 80Mhz width, running the
latest Openwrt with the CT firmware. I'm not seeing that " hostapd: could
not get valid channel" in my logs.
How did you conclude that it was a hostapd issue? Switching to auto
channel selection is not an option for me in this case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#169 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFNSCP7PLG6MWOX3QWLR23TFQK5NANCNFSM4TGXGQHQ>
.
|
Please provide this info. See this link for more info on how to gather debug
info: http://www.candelatech.com/ath10k-bugs.php
Description of the problem (how to configure, how to reproduce, how often it happens).
5Ghz radio stops broadcasting around once a day or so, module doesn't crash and 2.4ghz radio continues working. Only noticed this w/ DFS VHT80/160, but I have not tried other combinations.
Software (OS, Firmware version, kernel, driver, etc)
Openwrt r14694-e788e9bd87, hnyman's R7800 build, kernel/driver 5.4.70, firmware 10.4b-ct-9984-fW-13-795874169
Hardware (NIC chipset, platform, etc)
R7800, QCA8894/IPQ8065
Logs (dmesg, maybe supplicant and/or hostap)
dmesg:
I just bumped the debug verbosity and enabled hostapd debug logging, will update when it happens again.
The text was updated successfully, but these errors were encountered: