OK AI bot I have been playing with the flint 4 wifi and had to use the ssh command to restore the 3 wifi bands but now I do not have the option to congigure / use MLO - the option is not in the GUI.
How do I enable MLO or get the MLO option back in the wireless GUI.
Please provide the exact SSH command(s) used to restore the three Wi‑Fi bands and the Flint 4 firmware version shown under SYSTEM → Upgrade. The MLO entry can disappear when the wireless configuration is rebuilt or changed outside the GL.iNet interface; these details will determine whether the change can be reversed safely or whether the wireless configuration must be regenerated.
Avoid making further SSH changes for now. A factory reset may restore the default MLO configuration, but it would erase your settings, so it should not be the first step.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
wifi config rebuilt /etc/config/wireless as a basic OpenWrt configuration; it does not recreate the GL.iNet MLO configuration and GUI metadata. Since you made a backup first, test restoring it:
Wi-Fi will disconnect briefly. Refresh the Admin Panel and check whether WIRELESS → MLO Wi-Fi returns. This also restores the previous wireless state, so the missing-band issue may return. If that happens, keep both files and avoid running wifi config again; firmware 4.11.0 beta3 will likely need its vendor wireless configuration regenerated through a factory reset or firmware reinstallation without retaining settings, which erases the current configuration.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
root@FLINT_4_Main:~# cp /etc/config/wireless /etc/config/wireless.generated root@FLINT_4_Main:~# cp /etc/config/wireless.backup /etc/config/wireless cp: can't stat '/etc/config/wireless.backup': No such file or directory
root@FLINT_4_Main:~# wifi reload killall: mapd: no process killed killall: p1905_managerd: no process killed killall: bs20: no process killed root@FLINT_4_Main:~#
The copy failed before changing /etc/config/wireless, so wifi reload only reloaded the current generated configuration. The killall messages are harmless in this context. Also, you are correct: restoring the old file would have restored the original broken Wi‑Fi state, so that was not a suitable next step.
There is no backup available at the stated path, and wifi config cannot reconstruct Flint 4’s GL.iNet MLO configuration. The reliable recovery is now to reinstall the Flint 4 firmware through SYSTEM → Upgrade → Local Upgrade with Keep Settings disabled, then configure the router again manually. This erases the current configuration but allows the firmware to regenerate its vendor Wi‑Fi and MLO defaults. Do not restore a full configuration backup afterward, because it may restore the damaged wireless configuration. Keep the router powered on throughout the installation.
This reply was generated by AI. Please verify its accuracy.
GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.
Thanks Charles - I can file that scrpit for future reference.
I have since factory reset the router which did restore the WiFi, but recently something went wrong with AdGuard and Unbound - I determined I was unable to resolve any DNS when using AdGuard beta + Unbound.
I have once again done a factory reset but this time I did not restore any setting from file and manually set up again. I am still using the AdGUard beta without Unbound for the time being - I will reinstall Unbound soon….