„not keeping“ means „don't use a backup“
So more like a fresh installation where you configure everything from scratch again.
Chiming in to state that the "keep settings" option during firmware upgrade is likely problematic.
My situation, I had adguard with extra filters. I think this broke during the upgrade and caused my network outage.
Haven't tested backup settings + restore settings manually. I think it would be a good idea to put a disclaimer or something on the "keep settings" button during firmware upgrade.
I transitioned to Pesa's build for now for MT6000 and the difference in latency is astronomical compared to the latest "stable" build. The 2.4ghz problem on mobile devices was also now fixed (at least on my side) since it got the same speed compared to the stable (proprietary drivers) but again with huge difference in latency. On stable, unloaded was 25ms while on Pesa's build was only 12ms. Loaded latency was also very stable on this build where you almost doesnt need to use SQM anymore. Im just sharing this since the Op24 development seems to be in halt, and I really hope that GL inet team should really look at this build. Currently, I'm on his 3.1.0 firmware. I really love GL inet's firmware but the improvements in performance is big factor. Will get back once we receive new patches.
7 Likes
Can you provide a link please.
There is a trick you can do with backups btw 
You can open it with 7zip, and then you can delete everything you want to not keep especially in a situation which does corrupt your setting, then save the modified archive by closing it.
Then re-upload as backup after the update (when choosing to not keep settings)
Also you can also cherry pick files over scp (winscp) and upload them for each.
Also another trick for when things aren't right but you hate to do a full reset over one config:
You can grab the default config from the read only mount of the original upgrade, by going to /rom/etc/config its 1:1 representation of your current path except you use /rom/ in front.
I installed AdGuard Home and immediately the Update Lists.... options in OpenWrt stopped working, any idea what could be the cause and how to fix it:
*** Failed to download the package list from https://downloads.openwrt.org/releases/23.05.4/targets/mediatek/filogic/packages/Packages.gz
Your DNS seems to be broken. You should check your AGH settings.
I am not sure if this is a bug but since upgrading to 4.6.2 I seem to have a 5Ghz DFS issue.
I have my router set to use DFS channel 100, bandwidth 160Mhz, mainly due to congestion lower down the 5Ghz band. I have noticed recently it seems to revert back down to Channel 36, throwing all the 5Ghz devices offline until it reconnects.
I know the router has some kind of built in radar detection but this has not been an issue previously.
Has anyone else experienced this?
Is there a way of seeing why it is dropping 5Ghz and reconnecting on CH 36?
Maybe there is a new radar at your location, or due to other reasons the signal reaches you now. The best way to avoid this is by just using channel 36 then, since it seems to be working without issues.
The log should tell you when a radar was detected.
The problem I have is sometimes it happens when I am not in, so I don’t know when the 5Ghz drops.
I could check the lease times on the devices I guess.
Is there a WLAN log on LuCI I can dig into?
You will find the logs here: Log - GL.iNet Router Docs 4
They are combined, so you will need to search for whatever might help. I would guess searching for '36' should at least point to the line where to channel changes.
Logs will be wiped on reboot / power loss.
1 Like
I have 18 days of uptime yet my SYSLogs only go back to 7am today.
Is there a reason for that? Do I need to extend the logging period?
Hypothetical scenario:
- I updated the firmware with the "Keep settings" ON. Then the router crashed.
Does the router will crash also if I update it with "Keep settings" OFF and I manually load a backup from Lucy?
Indeed, same mechanism.
2 Likes
1 Like
Looking to his repo, Rany2 did quite some work I'm gonna try to build on his build aswell and see if my ayaneo crash
68 posts were merged into an existing topic: GL-MT6000 VPN Problem
https://fw.gl-inet.com/firmware/mt6000-open/testing/openwrt-mt6000-4.6.3-op24-0815-1723696806.bin
4.6.3-op24
today I'm using the openwrt snapshot.
but the ease of activating some things on gl.inet is unmatched lol
7 Likes
Yey, can't wait to get back home from vacation to test it.
1 Like