Hello all,
Looking at my Flint 2, I don't see any configuration backup/restore menu.
At the same time, switching to luci (I see it's not even installed by default in 4.8-BETA), you see a disclaimer warning that GL-iNet is not responsible for your actions when using luci.
What is the logic behind this?
There is a backup utility under LuCi itself : System - Backup/Flash Firmware. They are not saying they're not responsible for your actions (though they're not 
) , just that they do not maintain anything in LuCi. Their interface is a frontend to LuCi, so they are responsible for their front end maintenance but not that of LuCi.
Their interface should have backup/restore options. There's no better excuse for that.
Is that also why in 4.8 (BETA), installation of luci is left to the user? 
LuCi is installed, but it sits in the "back", "under" the Gl.inet interface.
Leaving Luci also easier for users to install some third-party plugins with Luci (luci-app-xxx) management pages.
The backup/restore options of GL GUI, this requirement has been submitted to PM for evaluation.
It would be nice if Backup & Restore could be prioritized. This has been a regularly requested feature going back to at least 2017:
The standard response to simply use LUCI is not a good solution, as by default, LUCI only recognizes what OpenWRT needs to back up. Because of that, it does not include everything that GL iNet modifies.
I have my own scripts for backing up my GL iNet routers.
We are trying to use uci for all of our config actually. Otherwise it is a bad design.
Would you be willing to share the scripts?
I need to configure 4 Flint 2's identically and thought that it woulbe easy to just configure one then backup the config and restore it on the others and save time.
How is it that this geature has been requested since 2017 and is not implemented? How much work does it take?
If everything is now truly managed solely through uci, what is preventing the release of a backup and restore tool?
Sorry, no, I am not releasing my backup and restore scripts as they must be modified depending on the GL iNet firmware version, sub-version, and the model of the router. I end up modifying them almost every time I upgrade. I also run a modified GL iNet configuration that supports the SoftEther VPN and other open source tools that GL iNet does not install.
Replication, as you have requested, differs from backup and restore. You must handle components that should be unique, such as keys and certificates, and these files should be regenerated on the first boot.
GL.iNet previously provided a tool called ImageBuilder, allowing users to create custom firmware images for their routers and deploy them across multiple devices. Unfortunately, like many useful features, this option is no longer available.
Formal statement on Gl.iNet software going closed source? - #6 by alzhao
