Easy to configure in a GL.iNET with OpenWRT under the hood. For a more flexible router at the cost of a steep learning curve go with Mikrotik.
post
Wireguard on OpenWRT is pretty much set it and forget it.
I have a GL.iNET Flint 6 router running OpenWRT with multiple WG interfaces, both client and server. The client tunnels reconnect automatically and it just works. A Pi 4 in one location is set to reboot every night and the WG tunnel reconnects every time. An older router running OpenWRT is just as reliable.
Unifi gear can run both a Wireguard server, as well as a Wireguard client.
I have a GL.iNET 4G router that I've configured WG for, and it worked exactly as expected. In my case, I had a requirement that when roaming onto a new tower, the tunnel had to recover automatically. And it seemingly did. Even though the router itself was mostly stationary, the mobile carrier's CGNAT endpoint would change and the router gracefully adapted to that
I would have preferred to use IPv6 -- which the router also supports, but off by default -- to avoid CGNAT but the opposite end of the WG tunnel had complexities which precluded that.
Was there a noticeable disruption between towers? It's taking resolvd a good 10 seconds to catch up when turning the client on and off. Maybe I should disable cache all-together.
Have the slate 7 and mudi 7.
Both great and capable little devices.
You can sometimes snipe a deal on AliExpress.
Of not, Amazon or their own store.
all 14 comments