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#605 - LuCI wireless associated stations doesn't show noise dbm in some channels (5 GHz @ AC 80 MHz width) #8227

Closed
openwrt-bot opened this issue Mar 7, 2017 · 4 comments
Labels

Comments

@openwrt-bot
Copy link

howl:

With an Archer C7 v2 the list shows up the noise level in the associated stations doesn't show up, instead it shows 0dBm and the bar icon shows empty bars. The noise level is display correctly inside the wifi configuration under the device options.

This only happens at least with the channel 112, I have tried all the channels below from 36-104 (44 and 108 jumps to 48 and 112 respectively because other nearly stations).

Can't try the 4 channels above because radars and the next 4 above because in my country doesn't exist channel 144.

I will try to test with less width than 80 MHz.

I set it to low because it seems that it only affect to the associated stations tables visualization and the wifi network works as it should.

@openwrt-bot
Copy link
Author

howl:

This is strange, I have test just now at 20 MHz all the channels from 36 - 112, and only 36 shown up the noise level in the associated stations, but, just one time, I set up channel 36 a second time and it doesn't shown the noise level.

It seems random.

@openwrt-bot
Copy link
Author

howl:

Forget to mention I'm using LEDE 17.01.0 with LuCI updated to the actual in packages 17.063.

@openwrt-bot
Copy link
Author

howl:

I have found also that the 5 GHz Ratio TX is always "6.0 Mbit/s, 20MHz" for all the clients, only the Ratio RX changes based on the data transferred between clients and the router. Perhaps is an ath10k issue and not a LuCI one.

@openwrt-bot
Copy link
Author

howl:

Actually ath10k-ct is being used and this doesn't happen, the issue is in the ath10k module. This can be closed.

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