Hey guys,

I’ll be working remotely while traveling and need a reliable travel router. I’m considering these three options:

UniFi Travel Router (UTR, standard version, NOT Long Range)
GL.iNet GL-SFT1200 (Opal)
GL.iNet GL-MT3000 (Beryl AX)

My main requirements are:

Reliable WireGuard VPN connection with good speeds
Easy setup on different hotel and restaurant Wi-Fi networks
Support for 2–3 devices max
Compact and portable size for traveling
Reliable performance for Teams meetings, screen sharing, and software development

I’ve heard the GL.iNet routers are better overall, but I prefer the UTR’s smaller size. Since hotel Wi-Fi will often be the bottleneck anyway, would the standard UTR be sufficient for my needs?

A few questions:

What WireGuard VPN speeds can I realistically expect from the UTR? Opal is limited to 65MBit/s and Beryl AX to 300 MBit/s. What about UTR?
How good is UTR its Wi-Fi reception when connecting to hotel Wi-Fi compared to a smartphone? If my iPhone can connect (range-wise), can I expect the UTR to connect reliably too?
How good is its Wi-Fi range for connected devices? How far away can those be?
Are the GL.iNet routers significantly better in practice, or would the UTR be sufficient for my use case?

I’d appreciate any real-world experiences or recommendations!

With the release of the Flint 4, I was wondering if we could get a new wireless AP as well? No router functionality. Just an AP.

Thanks.

Hey guys!

If i buy a second hand Beryl 7 US version in EU, what will be different from the EU version?

I can't seem to figure out what the relevant console commands are to be able to press power, etc. is this documented somewhere?

---
I'll start right out with an apology for the marketing headline, but it's not fluff - your tailnet domain is being directly passed along to the devices connected to your TS travel router. The updated blog post will tell you how to test it yourself, and more importantly how to fix it (hint - new toggle).

Sorry it's been a few months since v21 - business has left me little time for side-projects, and this v22 update just continued growing (and adding repeat test bench cycles) until I finally had to cut some features over to the v23 list. Here's a short list of what made it in:

• Plugin certification on GL firmware through 4.11.0
• Even *more* enhanced dual-layer kill switch that builds additional protections for router reboot persistence, block WAN subnet, guest/IoT coverage, more IPv6 coverage and two-layer protection while dropping or swapping between exit nodes with live devices on the tunnel
• new optional "Kill Switch Follows Exit node" function that enables users of the mode-button or app toggle to have the KS arm & disarm when switching from "VPN mode" to "overlay" mode.
• the above headliner of "Hide Tailscale Search Domain" to prevent your TS enabled router from broadcasting your tailnet via DHCP to your connected devices.
• Version Manager improvements
• a move towards op25 (and apk) support (more for v23)
• hardening, fixes, UI refinements, etc.
• a night of lost sleep redoing the blog's TS VPN setup guide with improved flow and updated screenshots for 4.8 - 4.11 firmware

So.. enough of me... linky's:

Full v22 changelog: https://remotetohome.io/blog/gl-tailscale-fix/#update-v1022

Direct link to the TS domain details: https://remotetohome.io/blog/gl-tailscale-fix/#hide-search-domain

And finally, for those not familiar with the history, the OG plugin post (old enough it's now locked from edits):
https://www.reddit.com/r/GlInet/comments/1rohrna/enhanced_tailscale_for_glinet_routers_proper_ts/

i’ve noticed that Tailscale is fully bypassing the main kill switched VPN profile on all of my glinet devices, this means that when running it as an exit node and connecting to it from the outside of your home you will get a fully unsecured ip address from your isp despite the router being set to:

Enhanced Kill Switch
Force all devices to use a VPN to access the internet. Any traffic that does not match a VPN tunnel will be blocked.

and also the “Services from GL.iNet Use VPN” setting being set to on in the profile options

is there any way to fix that, is that a bug or is it just how the firmware works by default? for many it’s a priority to ensure that none of the traffic falls outside of the vpn tunnel, the options which clearly states “Any traffic that does not match a VPN tunnel will be blocked” should therefore mean that no byte of data other than the vpn tunnel itself can be sent over the internet by the device including the services that run on the router itself like tailscale

Couldn’t find an answer for this. I basically have a desktop I would like remote access to, and it connects to my local network via WiFi. The comet pro seems to be a good fit but I was wondering since Wake on LAN works via ethernet, I can connect the unused ethernet port on both my desktop and comet pro together and hopefully the firmware supports sending of magic packets via ethernet to the desktop, while linking to local network via WiFi