How to Configure GL.iNet Router to host Tailscale Exit Node

[DeifiedNinja]

Looking forward to this update

[will.qiu]

This issue has been fixed in the v4.8.5 beta version of MT5000:
Download link:

GL.iNet download center

Upgrade guide:

Local Upgrade - Upgrade - GL.iNet Router Docs 4

[Marv]

@will.qiu

MT5000

@will.qiu thanks for letting us know!

Question on the overall versioning across the products - is there a target timeframe to align most/all versions?

For example, I purchased the GL-MT5000 Brume 3 to use it as a main router, relieving the main GL-BE9300 Flint 3 (out of a 3-node mesh) off the routing duties.

By the time I setup the Brume 3, I saw the Flint 3 got bumped to 4.9.0 Beta 2026-04-11 (and also now has DPI, etc), while the Brume 3 latest beta you just mentioned is at 4.8.5 Beta 2026-03-31 .

It makes it hard to map which features get added at what version, especially when the latest products released within the same quarter come out of fairly different versions and features.

If I’m on the beta path (I’m fine with that), do I pull the Brume 3 out of the network, so I can enjoy the latest 4.9.0 Beta codebase has to offer, or that’s not really “the latest” as Brume 3’s 4.8.5 Beta from 2 weeks before that already had the fix reported here, and also the same features, regardless of the “older” version?

[Marv]

I’m sure you’re aware as your ipk is not on the repo but let me drop it here while it’s on my screen.

I did upgrade to the latest beta as per @will.qiu post from earlier today (EDT) and ran opkg update && opkg install $(cat /etc/backup/installed_packages.txt). As expected, it ended with:

….
Configuring python3.
Configuring python3-pkg-resources.
Configuring python3-speedtest-cli.
Collected errors:

• opkg_install_cmd: Cannot install package gl-tailscale-fix.

[rthco]

Hi @Marv - Yes, that would be expected. The plugin is set to be persistent on all firmware prior to 4.9.x series, but we set it to automatically de-install with the 4.9 series given how GL has significantly changed the OEM TS functionality, and I’ve had no ability to test against it.

I believe 4.9.x now automatically takes care of the IP Masq functions, but I have no idea if it contains a proper killswitch like the plugin provides. The default GL TS implementation up through 4.8.x series (without the plugin) leaves you completely unprotected from leaks during TS OOM kills or restarts (even just changing exit nodes or other TS options meant you would be leaking real IP for 8+ seconds).

[will.qiu]

@Marv

Question on the overall versioning across the products - is there a target timeframe to align most/all versions?

Most hardware models that support newer firmware versions will gradually be updated to the same version over time. For example, at present, most of our devices have already reached v4.8, except for a few that cannot support it due to hardware limitations.

@Marv

It makes it hard to map which features get added at what version, especially when the latest products released within the same quarter come out of fairly different versions and features.

You can distinguish feature sets by the minor version—for instance, moving from v4.8 to v4.9 brings more significant changes (such as the addition of DPI, VPN Dashboard restructuring, etc.).

@Marv

If I’m on the beta path (I’m fine with that), do I pull the Brume 3 out of the network, so I can enjoy the latest 4.9.0 Beta codebase has to offer, or that’s not really “the latest” as Brume 3’s 4.8.5 Beta from 2 weeks before that already had the fix reported here, and also the same features, regardless of the “older” version?

Brume 3 has already received some of the new features from v4.9, such as AWG 1.0 and DPI. However, if you’re eager to experience the full set of v4.9 features, then using the Flint 3 would indeed be necessary.