No prob, let us know if it worked. On one of my gl-mt6000 I always just run latest stable and keep it updated via owut upgrade, it works extremely well and I recommend most people just do that. (The other one I keep bleeding edge via main snapshots with my own custom builds etc).
owut was not on my router so I tried ASU again but this time I remembered that I needed to untick the save config box. It upgraded OK but I had to then restore my previous backup (config files) to get it up and running properly again.
I will install owut and try it next time.
I'm running OpenWrt 23.05.5 on a Flint 2, and I'd like to upgrade to the latest 25 release. Would I be able to do that while retaining my configuration? If not, would I be able to install a fresh OpenWrt 25 and then restore my backed-up configuration? I'd really like to avoid having to go through all the configuration process again; I have several VLANs and SSIDs.
Got one for my friend but it ended with tomato64 instead of openwrt , works nicely since then.
Those two would be the same:
"retain config in sysupgrade" is actually just "sysupgrade + automatic restore of carried backup file".
There are not that many changes between 23 and 25, but as 23 has been deprecated already for some time, it starts to be hard to remember ancient stuff...
There are some changes, e.g. in the preferred notation of interface addresses, which might affect you negatively.
- 23 and 24 defaulted to form of ipaddr
192.168.1.1and netmask255.255.255.0, while - 25 defaults to having CIDR notation in ipaddr, meaning ipaddr
192.168.1.1/24so that the netmask bits are included in the interface ipaddr and there is no netmask config line.
See examples in e.g. here: (note that notation both in loopback and lan, and other possible interfaces)
There could be also target/device-specific changes (like swconfig to DSA) that could invalidate the config, but I do not think that there is for MT6000.
If you want to try while retaining your configuration the do one major release at a time so first go to 24 en if that works then go to 25
I personally would not keep my configuration but rebuild it manually using my old configuration as a blue print.
I do that for my main router with every major release also as a kind of spring cleaning and to familiarise myself with the new options but that is just me
Thank you all. I agree with @egc that I should rebuild every time and re-familiarize myself with everything, but I really don't feel that there's time at the moment; it took me ages last time around to get my head round everything, and though I would love to do it all again, I'd like to get the upgrade done and working before re-learning things when there's more time.
I do have one spare Flint 2 which I keep as an exact copy of the working one, so I could try first doing all the updates on that, and then swapping it out to see if everything works.
Just reporting back for anyone else facing the same upgrade:
I did a regular firmware flash with the sysupgrade image from 23 to 24, checked everything, then went from 24 to 25. It worked perfectly; all settings were retained. I don't have any non-standard packages installed, so my scenario was straightforward.
So I've done my main router, and I'll upgrade the dumb AP tomorrow. I'm very glad I took the approach of buying three of the routers; I was able to do the upgrade on a mirror of the main router, then just swap it in for the running one, and I'll do the same tomorrow with the AP. Then I'll set up the spare again as an exact dupe of the main router ready to serve as a replacement if needed.
Yes it's been a great device for the past couple years. I recommend installing the package "owut" it's a totally seamless upgrade system. Then you can simply SSH in and enter owut upgrade. It'll help you stay up to date more often.
I have a new problem. I attempted to set up the dumb AP on my spare router by restoring the configuration from the dumb AP (also a Flint 2), intending then to run the same sequence of two updates. But I was forgetting that the dumb AP was configured not to have a DHCP server running, so when it rebooted, I was unable to connect to it to continue the process. Does anyone have any suggestions on how to connect to luci (or ssh) on a Flint 2 in this state?
I don't understand how a missing DHCP server in the router would affect connectibility. You can set fixed IP on your pc, and then connect to the routers fixed ip.
If the router is set up as DHCP client, then it is a question of having the server on the main router?
Other practical solutions:
- Router has likely an automatic ipv6 link-local address.
- Use reset to reset the router to default config, with 192.168.1.1
- OpenWrt fail-safe mode sets the address temporarily to 192.168.1.1. That mode could enable you to edit selected config files. https://openwrt.org/docs/guide-user/troubleshooting/failsafe_and_factory_reset
- Use the gl-inet recovery flash to flash a brand new image, and lose the problematic config. https://docs.gl-inet.com/router/en/4/faq/debrick/
Thanks! A hard reset followed by upgrades and then restore from backup did the trick. For anyone else in this position: the backup from OpenWrt 23 restored perfectly into a fresh OpenWrt 25 install.
What's everyone's 2.4 GHz AX throughput in general to a 2x2 Smartphone? The 2.4 GHz band is very much needed to me to reach backyard, and it's very usable - so just wondering.
My medium range signal is around:
With this I get around 90-120 Mbps with SNAPSHOT r35721. But I am curious as to what others get 
Not bad for aging 2.4GHz, a couple things you can try: First simply increase 2.4GHz width to 40MHz (it's under LuCI Wireless -> Edit -> Operating Frequency set to AX / 40MHz), that should give you a speed increase.
If you want more try pesa's build which has patch to allow for QAM-256 VHT on 2GHz if you enable it. It's an unofficial patch to the wifi spec, and requires clients to support that, but Pixel 10 should and that also has a speed gain. (I don't personally use this but some people have had good results). Note that it does not affect 5GHz bands.
One reason why I was asking around on HE20 is that a big portion of smartphones and Android/Apple typically only use 20 MHz with 2.4 Ghz, hence was curious on others empirical experience about this.
In Apple’s current iPhone Wi-Fi specifications, the 2.4 GHz entries show:
Wi-Fi 7 (802.11be) @ 2.4 GHz → maximum channel width: 20 MHz
Wi-Fi 6 (802.11ax) @ 2.4 GHz → maximum channel width: 20 MHz
Wi-Fi 4 (802.11n) @ 2.4 GHz → maximum channel width: 20 MHz
From looking around, 802.11ax @ 2.4 GHz with 20 MHz I have always wondered if those 120 Mbps real throughput I get is a good number.
Ah haven't seen that. I think pretty much all my devices are on 5GHz. I would shut off my 2.4 radio if not for a Chromecast Audio I use to broadcast to an old pair of speakers, it's a cool little device so I leave it on.
I just ran some iperf3 tests from my Samsung Galaxy S10+ and got 173-175mbit on both upload and download on 2.4Ghz. About 20 feet away through 1 sheetrock wall.
My previous Asus RT-N66U (running merlin) got over 200mbit, maxing out at 230mbit to the same phone.