fff-wireless: add workaround for wifi configuration after update #324

fbl · 2024-03-17T22:20:02+01:00

fbl commented

2024-03-17 22:20:02 +01:00

Introduce a workaround for an OpenWrt bug on the Xiaomi Mi 4A (Gigabit
Edition). After an update of the firmware, the wireless interfaces are
not properly created as configured.

When configuring the WiFi interfaces via uci and applying the
settings using reload_config, hostapd reports errors and no WiFi
interfaces are created.

It seems like OpenWrt tries to dynamically reload the settings instead
of restarting hostapd, but hostapd fails to properly apply them.

To work around this regression until the root cause is found, restart
the wifi interfaces manually after a firmware upgrade.

Fixes: #319

Introduce a workaround for an OpenWrt bug on the Xiaomi Mi 4A (Gigabit Edition). After an update of the firmware, the wireless interfaces are not properly created as configured. When configuring the WiFi interfaces via uci and applying the settings using reload_config, hostapd reports errors and no WiFi interfaces are created. It seems like OpenWrt tries to dynamically reload the settings instead of restarting hostapd, but hostapd fails to properly apply them. To work around this regression until the root cause is found, restart the wifi interfaces manually after a firmware upgrade. Fixes: #319

fbl added this to the 20240401-beta milestone 2024-03-17 22:20:02 +01:00

fbl added 1 commit 2024-03-17 22:20:03 +01:00

fff-wireless: add workaround for wifi configuration after update

ci/woodpecker/pull_request_closed/woodpecker Pipeline is pending

Details

ca4fd83317

Introduce a workaround for an OpenWrt bug on the Xiaomi Mi 4A (Gigabit
Edition). After an update of the firmware, the wireless interfaces are
not properly created as configured.

When configuring the WiFi interfaces via uci and applying the
settings using reload_config, hostapd reports errors and no WiFi
interfaces are created.

It seems like OpenWrt tries to dynamically reload the settings instead
of restarting hostapd, but hostapd fails to properly apply them.

To work around this regression until the root cause is found, restart
the wifi interfaces manually after a firmware upgrade.

Fixes: #319

Signed-off-by: Fabian Bläse <fabian@blaese.de>

ArchTux commented

2024-03-18 19:31:27 +01:00

Working on my router now without manually restarting the router.

fbl commented

2024-03-21 21:57:09 +01:00

Applied.

fbl closed this pull request

2024-03-21 21:57:09 +01:00

fbl commented

2024-03-24 20:33:33 +01:00

Der Workaround scheint auch auf der node-Variante einwandfrei zu funktionieren. Es ist unklar, ob das Problem dort vorher überhaupt bestand, oder ob es nur auf der layer3-Variante aufgetreten ist.

ArchTux commented

2024-03-24 22:32:09 +01:00

O.K. wobei ich schon glaube das Node da auch betroffen war. Oder ist Node was das WLAN angeht so viel anders gebaut?

adschm commented

2024-03-24 22:43:08 +01:00

Soweit ich mich erinnere starten die WiFi Treiber asynchron. Es ist also grundsätzlich denkbar, dass hier die beiden FF-Firmware-Varianten sich durch unterschiedliche Timings auch unterschiedlich verhalten.