GL-AR300M16 Mini

I see that you bought a Flint 2, but you have not fixed your real problem. What you need for travel is redundancy and to get rid of any single point of failure, like having only 1 remote router. Remember that any single device or location can fail or go offline. Having multiple routers at multiple s

You need your Wireguard UDP packets to fit inside the Ethernet packet, or the UDP packets fragment, and depending on the network, can be dropped on the floor. On the AR300M, try dropping your MTU in your Wireguard config file down to 1280. If that works, you can try stepping it up, but I normally ju

I have friends and family who let me put VPN servers in their houses/Apt. I pay for the routers, I manage them, and give them accounts on them, so they can also remotely use their home IP address when traveling. Most of them are GL iNet AR300M routers, running OpenWrt. Not fast, but cheap and depend

If you are looking for cheap and reliable, go with a pair of AR300M16. Unlike the Opel, it has great support for OpenWrt, so you will have an option for firmware with security fixes after GL iNet drops their support, and it's a bit faster than the Mango, at around the same price. Set it up with Wire

I purchased my first GL iNet router in 2019. Firmware inconsistency across their line of routers, along with poor QA, has been the norm for me with their products. I have basically given up on using their stock firmware. Hardware-wise, though, they have been great. My first device, an AR300M, is sti

I have it on my truck and use a GL-AR300M16 on my 2nd wan on a UDM router. The GL-AR300M16 will connect to the mini on the truck when I'm in range and use it as fallover. I have a solar on my truck with a controller that shuts it off if the batteries get anywhere near low.It works really well, I've

GL iNet keeps building and selling bigger, heavier, and more power hungry routers. I no longer consider them true travel routers, and I am currently refusing to buy anything new from them until they release something like a Mango 2. That said, their hardware is usually solid, and I am still using mu

I own multiple older GL iNet routers including AR300M, AR300M16, AR750 and AR750S. In my testing of the 4.x firmware on any of these routers, I found them much more sluggish and flaky than when I run GL iNet 3.x firmware or OpenWrt firmware on the same routers. I do not think it is due to using up a

File sharing is just one example. On multiple GL iNet routers, it was listed as an out of box feature as shown in the 3.x documents. See: https://docs.gl-inet.com/router/jp/3/tutorials/file_sharing/ Per the 4.x release notes it was pulled in many models. Here is just 1 example. https://dl.gl-inet.co