-
Notifications
You must be signed in to change notification settings - Fork 16
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
RSSI Led device setting #169
Conversation
If there is a rssid_$WLAN section in the system config, make sure to set the dev to the wifi mesh device. Signed-off-by: pmelange <[email protected]>
If there is a rssid_$WLAN section in the system config, make sure to set the dev to the wifi mesh device. Signed-off-by: pmelange <[email protected]>
If there is a rssid_$WLAN section in the system config, make sure to set the dev to the wifi mesh device. Signed-off-by: pmelange <[email protected]>
please cherry-pick into 1907 and 2102 |
@PolynomialDivision The "Test Build" check is failing, and it has nothing to do with the commits in this PR. Can you fix it? |
The wizard, mesh-settings page, and migration has been run-tested on a CPE210 v1 (a device with rssileds) and a WDR4900 V1 (a device without rssileds). |
set the rssiled device to the wireless mesh interface. If there are no rssid_$WLAN sections, then nothing happens. While at it, fix a typo in function r1_1_0_ffwizard Signed-off-by: pmelange <[email protected]>
cherry-picked into 1907 and 2102 |
Run tested CPE210-v2, Freifunk Berlin falter vsnapshot - b0db9f0, working ;) |
Maintainer: me
Compile tested: None, only run tested
Run tested: TP-Link CPE210 V1, Falter Firmware 1.1.0
Description:
The RSSI Leds will cause a high load when the referenced device (system.rssi_$WLAN.dev) is not set to a proper wlan interface. These commits will set the RSSI Leds device to the wireless mesh interface (either adhoc or 802.11s).
Fixes: #142