New firmware version 4.6 being released for beta testing

Flint 2. Installed 4.6 beta 3. After turning on Adguard Home, the UI became frozen and doesn't accept any inputs. I can still click Settings to reach the Adguard console.

I mentioned that here too New firmware version 4.6 being released for beta testing - #162 by Pro4TLZZ


When will the MT2500 firmware be available?

1 Like

It's online at the official download repo: GL.iNet download center

When will be Puli, Opal? Is there any approximate timeline?

Please don't rush this! Take your time working out the bugs before you start releasing this to other devices. Happy to wait till bugs are squished!

1 Like

@hansome Please check it.

It is available now.

They will start upgrading after the first firmware stable releases. There is no specific point in time yet. My guess would be at the end of July.

waits patiently for owrt24 firmware to test

Am I right in thinking that any snapshot on the brume 2 that is released / dated after the beta should have more fixes than the beta - I am currently running the snapshot version from around 4 days ago as there wasn't a beta in the brume 2 downloads section. Since checking again the beta is listed however it's dated older than then snapshot I installed.

Can you please check if the "AllowedIPs" parameter in your wireguard conf file has if it doesn't the the DNS is omitted by design in auto detect mode.

if you check the mt3000 download page, both mt2500 and mt3000 have the same date for the snapshot

Yes for the snapshot they do, however I'm talking about the beta that appeared in the brume 2 page. It wasnt there a few days but now a beta image has appeared however it's dated older than the snapshots.

Can you confirm me if Tailscale will have a native exit node option on the GL.iNET GUI? I want to know if things have changed regarding it, the website says this: Note: GL.iNet router is not yet available as an exit node, this feature is still under development.

1 Like

It have merged more fixes into the code, but it may also have other bugs. snapshots are like that.

It's not in the immediate plans yet. Where did you read that this feature is in development?

Here: Tailscale - GL.iNet Router Docs 4

Would be a great feature I hope it comes out sooner than I expect

Hi there, I am running 4.6.0 beta2 on Beryl AX (GL-MT3000) and had an issue with logging into a hotel captive portal.

With the new "Auto-Enable Login Mode For Public Hotspots" option enabled, it detected the captive portal and gave me a link to log in.

When I clicked the link, it opened a new Chrome browser window in Android, but was unable to resolve the DNS for the captive portal page.

I tried all possible combinations of the DNS settings, I think, but nothing worked.

The help screen that pops up for the new "Auto-Enable Login Mode For Public Hotspots" says that enabling it may cause data leaks to the provider of the hotspot. Therefore, I thought that enabling this would allow the captive portal login to work without any changes to the other settings (the ones that I had to make to get logged into a captive portal, using previous versions of firmware).

In the end, in VPN "Global Options", to get the DNS working in order to log into the captive portal, I had to disable "Block Non-VPN Traffic" (which is intended to block leaks - perhaps beyond just leaks to the provider of the hotspot).

This might just be a documentation issue. That is: I had expected, based on the help screen, by enabling "Auto-Enable Login Mode For Public Hotspots", that leaks (only) to the hotspot provider might occur, and it never occurred to me that I also needed to disable "Block Non-VPN Traffic" as well (so it took me about 20 minutes to figure it out (der!)).

Having to disable "Block Non-VPN Traffic" for the captive portal DNS to work is probably fine. Maybe. (On the one hand it kind of defeats the purpose of having the new "Auto-Enable Login Mode For Public Hotspots" disable VPN temporarily and allow (limited) leaks, while the user logs in, but on the other hand, if super critical to avoid any kind of leak whatsoever, some users would probably want "Block Non-VPN Traffic" to do so in all cases and not be overriden by any other feature).

If the help screens for both "Block Non-VPN Traffic" and "Auto-Enable Login Mode For Public Hotspots" could be updated to refer to one another to explain how they interact, the user could make well informed choices when enabling/disabling these options. (Just a note in the "Auto-Enable Login Mode For Public Hotspots" help screen that, to allow captive portal DNS to work, the user may need to temporarily disable "Block Non-VPN Traffic", would have helped me a lot!).



Thanks for the suggestions. Seems the kill switch is not disable temporarily in Auto-Enable login mode, which it should.

For leaks, during captive portal login, seem it is difficult to prevent any leak. But definately we can investigate and improve step by step.