I'm currently using the MT3000 (Beryl AX) router while staying at a hotel that uses a captive portal system for internet access (Centre Point Hotel, SSID: CENTREPOINT). The router successfully connects to the hotel's Wi-Fi network in Repeater (WISP) mode, and it receives a valid IP address from the hotel’s DHCP server, but the captive portal login page never appears.
The router enters "Login Mode for Public Hotspots" as expected, and I’ve tried both clicking “Go to Login” in the admin panel and manually navigating to HTTP sites like http://neverssl.com, but still no portal is shown. Client devices connected to the router cannot access the internet.
Here’s what I’ve already tried:
Disabled DNS Rebinding Attack Protection
Disabled VPNs and AdGuard
Tried MAC cloning using a device that already logged in directly to the hotel Wi-Fi
Switched between 2.4GHz and 5GHz bands
Rebooted both the router and client devices
Tested with different browsers (mobile and desktop)
Device Info:
Model: GL.iNet MT3000 (Beryl AX)
Firmware Version: 4.8.1
Hotel Wi-Fi SSID: CENTREPOINT
Issue: Captive portal login page not appearing, no internet access for clients
It was working before on the same network but an older Firmware version.
Please advise how I can force the captive portal to appear, or whether there are firmware updates, debug tools, or workarounds specific to the MT3000 to resolve this issue.
as I can see in your screenshots, you´ve changed the kill switch at the VPN Dashboard. This is not what we´ve meant. At the bottom of the Dashboard there´s an option “All Other Traffic”. Please disable all VPNs and enable this option.
Well, you´ve written in your first post, that it worked with an older firmware (4.7.4?). Is it important for you to get quick access to that hotspot? If yes, you can make a backup of your current config (via LuCi) and downgrade the MT3000 to the old firmware. I know that this will take some time to do this because you would have to configure the whole router.
If this works, we can exclude a problem with a new firmware of the hotel AP. And it would be a hint for GL.Inet support for a problem with the 4.8.1. It´s only a suggestion of me.
Maybe the wrong place to say this. I haven't faced a captive portal in several years, and my Beryl AX is set up for four rules with two VPN tunnels: Any client trying to reach this net, rule 1; Any client trying to reach this other net, rule 2; These particular clients trying to reach anything, rule 3; anything else, rule 4. Works fine.
I've now used the Beryl in three places with captive portals (not requiring payment), and the captive portal function has worked kind of magically. I thought I was going to have to do the same kind of steps as my Mango.