No need to reboot. I just need a new MAC every xx minutes/hours. There are still several Hotspots that allow 1/2/3 hours of online time.
At the moment i am using a script to bring the interface down / change MAC / interface up.
This is a new requirement and we will seriously consider it, thank you for your feedback!
1 Like
Is this the new 4.7 beta 3? Release date today but looks the same as beta 2 to me according to the notes.
I cannot see any justifiable reason to update my MT2500 from 4.6.4
Hello,
Is it possible to add in future release a backup functionality into GL.iNet interface?
For now, I don't find anything about this, except in LUCI.
I am using the latest beta on MT6000 (v4.7.0 - published in 30/09/2024) in DHCP mode. When clicking on settings Page, instead of directing to the Adguardhome page, it redirects to address 192.168.8.1
When its available on Flint and Slate AX as well?
2 Likes
Yes, you've been very observant, we've updated a version and this one fixes a few issues.
Could you please describe in detail what you mainly want to back up?
Thanks for your feedback, this may be a bug, please let us check it.
We have plans to update Flint and Slate AX, please be patient, we'll do it soon.
3 Likes
Hello,
I thought about all settings we can change, like address reservation (ip and mac), vpn server configuration, clients customisation, wireless settings, port forwarding, lan settings , guest network, schedule tasks , Time zone, etc…)
Also can tou add a settings to add ssh key to connect in ssh ? Currentely this is only possible with luci.
1 Like
So your requirement is to make a backup of all the configurations that can be set up and add ssh key setting to connect in ssh , not sure if I understand correctly.
2 Likes
Nope, just one going to my modem and the other to my PC.
I have tried making LAN1 into a WAN port and the same issue still happens.
You understood correctly 
Backup everything from GL.iNet interface and maybe not luci in order to not have duplicate.
And I suggest to add a way to add a ssh-keys into GL.iNet interface as LUcI have.
Drop LuCi? Yeah, NO. There is a lot more to LuCi than Backups and SSH keys that I like having access to. I have no need to complicate the UI any more than it needs to be. I don't understand why this even needs to be considered honestly since it is already something that can easily be done using LuCi. I'd rather have the developers work on other things than reinventing something that the router already does just fine.
*You can actually add any file to your backup that you need by adding it to the configuration list in the flash operations.
1 Like
The main issue, imho: The backups are only great if you stay on the same version of OpenWrt.
As soon as there are major changes, backups will break more than they fix.
So for having a good way of creating backups, the backups should utilize the GL GUI API instead of plain copying config files or running uci commands. There is a need for a unify backup approach where the OpenWrt version doesn't matter.
3 Likes
No no no !
My dumbphone correct the not into drop 
I edited !
Sorry 
From what I'm seeing, GL.iNet seldom seems to change the version of OpenWrt that the router runs on, if at all! Actually, I've never seen it happen on any router, but I'm running a GL-X3000, and if they did update OpenWrt on it, I'd just start it over from scratch so I don't have issues and still use LuCi's backup. But you definitely have more experience in their routers then I do so I'll roll with it if it's a +1 on everyones list. But again, I'd rather see the developers put their time into updating the version of OpenWrt that the router runs on then to add a backup feature so I hope we can agree on that point for sure.
1 Like
Where do you think the GL GUI API gets its configuration files from? They don't keep separate system files for their GUI, they utilize the same config files that OpenWRT needs to operate. If there are major changes in OpenWRT, the GL GUI API would need to get corrected to point to the new file locations. This is just simply redundant and I can see where it is not a good use of a programmers time.
I know that the GL GUI API has it's own files that don't get backed up. One example is the /www/views/ directory. I have made my own changes to some of those files. But I can easily add the /www/views/ directory to the backup configuration list and restore it at any time. Same can be done for any single configuration file that you would like to have backed up and restored.