I originally bought a GL.iNet travel router because it was rated high and ran a customized version of OpenWrt. To me that meant when GL.iNet EOL'd or stopped supporting the router with software updates, I could move to the OpenWrt official version. That's what I've recently done.
But the thought occurred to me that the newer GL.iNet travel routers are far faster with better features that my old one, so I should just get one when they go on sale.
What is the recommended time to move a GL.iNet travel router to OpenWrt official? Any downsides to doing it when you unbox it?
Thanks, but I have a requirement for a travel router that it must be easy to setup at a public WiFi location and not take all day. I have my OpenWrt setup working on USB Tether, WAN-ethernet and WiFi repeater all working but it took a day to configure it. I had to install a lot of drivers and modules to get the tethering working. Same for TravelMate.
I'm sure it will be easier next time, but the standard web setup for an out of the box GL.iNet travel router can be done by anyone easily.
That's why I usually stick with the Standard GL.iNet software and upgrade it via their update methods. But I want the security fixes that OpenWrt include probably faster than GL-iNet.
I have no idea how long it takes GL.iNet to patch security issues. I'm guessing OpenWrt is fastest.
As a rule when out in public, I just use my phone as a hotspot for my other devices since 5G on T-Mobile, or Verizon mobile data networks is more secure than public WiFi where you definitely need a travel router.
For my home router, I did it immediately pretty much.
I don't think you need to worry about security fixes if it's not a shared connection. I didn't bother updating the home router between 18.x to 25.x and nothing happened, so if you're comfortable with what you have, then just keep using that.
This is extremely ill-advised. It is incredibly important to keep your home router up-to-date (on official OpenWrt or whatever firmware you're running), as newly discovered security vulnerabilities can be used to compromise your network even from the wan or wifi.
The learning curve on official OpenWrt is something to consider, and if you find the vendor firmware to be both sufficient for your needs and faster/easier to setup, go ahead and use that as long as it's still supported and up-to-date.
That said, I personally bought an MT3000 and updated it literally minutes after unboxing it so that I could use official OpenWrt with all of the features and flexibility. I use this travel router on the go and I'm able to be up and running in 2-3 minutes.
Unfortunately, I'm doing my testing and learning on an old AR750S. I've set it up for 2 different AP for repeater function and I've tested Ethernet WAN to a internet modem. I've also tested and got working USB tethering to a cell phone. My issues seem to be switching setup. It takes more than enabling and disabling a AP in TravelMate. I seem to also have to reboot the router and sometimes I have to go to the wireless page and enable the interface there. I seem to be in a confused state where I don't have a defined sequence to switch between APs for repeating. Maybe I'll figure it out.
I guess one of the advantages of the GL.iNet is you can reload the factory firmware any time you want and installing OpenWrt using the sysupgrade.bin is easy.
Yes, and I don't disagree, but commercial routers are abandoned so quickly and we don't see stories about how they are being widely exploited every day. Then again, we did see that news story this year about how new routers aren't allowed to be sold in the US anymore (old shelf stock is still OK) if they are designed or manufactured outside the US so that implies something is known and they are just keeping it quiet. Probably more of the same situation as when they pulled out all the Huawei 5G networking hardware. My router is Chinese hardware, it runs OpenWrt. Am I at risk? Maybe.
I stopped doing Windows updates because I grew tired of Microslop breaking everything. So I just disable obvious things and update key things like the browser.
So yes, nobody should do what I do, this is an official policy that makes sense.
I always upgrade the to OpenWRT it right away, and I specifically pick the routers I buy to do it
right away. But I usually don't need to have the latest and greatest.
My latest devices are:
3 Belkin RT3200 I bought in February 2022
3 Zyxel M1 I bought in August 2023
2 Cudy AX3000 I bought in August 2025
1 Raspberry Pi 5 I bought in May 2025
I run
the Raspberry as the actual router/gateway,
6 "routers" configured as "dumb AP" around my house for coverage,
one of the Cudys as a travel device, since it's decently small and cheap.
And one of the Zyxels is boxed up in a closet just in case something breaks
and I need to replace a device.
Every now and then I decide to replace something. Then I lock onto some
well-recommended devices around here, put them on a keepa.com watch list, and wait
for them to go on sale.
Are you kidding??? This is most certainly a major issue and yes, we do see this all the time.
Again, while I agree that windows updates can break things, not updating windows is a recipe for disaster. Where I work, devices are entirely locked out of all corporate resources if they are not up to date (across all platforms, windows included, but including all others).
I've solved the Windows update problem by removing Windows. When I retired 12 years ago, I had to turn in my Windows Laptop. I run Linux at home, usually Debian, so updates are not an issue. Because my NVME drives all use BTRFS, I have instant snapshots to get back to before an update if it fails, but one has never done that.
Exactly this for me, too. The only reason I acquire new routers, switches and APs is to immediately install OpenWrt, often to give them away in their improved state.
I have.. for years it wasn't good enough for DE, but it's good enough now. I'm typing this on my Deck's Plasma DE. I still use my Windows previous main desktop on my TV because I have my video renderer configured great (and Windows is better at changing refresh rates and stuff), and it's still better for certain things because of all the software that was made for it, like CD/DVD ripping, etc. but for everything else, I agree, Linux is good enough. I still wouldn't recommend it to Joe Public though.. Linux has papercuts that Joe Public isn't smart enough to fix on their own.
How exactly do you fix the issue without updating the binary if the issue is due to code that has been compiled (a distinctly different issue than, for example, a problematic run-time configuration)?
Code patching is not always so simple and requires other infrastructure to perform that patching. Releasing updated packages and or full OpenWrt releases is pretty straight forward and installing them is easy.
I see you're middle aged. Think of it this way: how much time do you want to spend relearning new UX ? For me it's owrt until i die or am sent to a care home.
)