I have a Beryl AX (MT3000) on Firmware 4.8.1 (newest stable). I cam currently at a location which has a free Telekom hotspot - one of the most frequent public wifi providers in Germany.
I have the Beryl in Repeater Mode and enabled “Auto-Enable Login Mode for Public Hotspots”.
DNS set to Automatic, no VPN, etc.
It works when I access the portal through a client device and agree to the terms.
However before activation, the portal is never detected. So I can’t really use features like encrypted DNS or VPN.
It shows the “connected but no internet” warning but does not switch to “Login Mode”. When I have encrypted DNS on, I cannot accress the portal. The logs contain the following line which indicates that it is not detected as a captive portal:
daemon.info gl-repeater[2575]: (repeater-portal.lua:418) not found portal
Staff looking into this would be appreciated as it looks like a bug in portal detection. If there is more I can provide, I am happy to do so. Just tell me what you need - I’m ok with using the command line on the device.
Hi,
Thank you for the information.
Since the router is able to connect to the Telekom hotspot, but the captive portal is not detected automatically.
Could you please refer to the following guide and check the captive portal troubleshooting steps?
After these settings, please reconnect to the Telekom hotspot and check whether the captive portal can be detected and opened normally.
If the issue still occurs after following the guide, please let us know and we can continue investigating it with you.
Hi,
as I said - when I follow the troubleshooting steps I can connect to the portal and subsequently the internet. The point is that portal detection does not work. Login mode and automatic login mode are never triggered, so the feature set that can be used with this hotspot is reduced.
Best regards
Hannah
Hi,
Thank you for the clarification.
Since your Beryl AX is currently running firmware v4.8.1, could you please try upgrading to the latest v4.9.0 Beta firmware for GL-MT3000 and check whether the same issue still occurs with the Telekom hotspot?
The v4.9.0 firmware includes fixes for some related captive portal/repeater scenarios on the MT3000, so we would like to check whether the newer firmware also improves the behavior in your Telekom hotspot environment.
You can download the firmware here:
If the captive portal is still not detected automatically after the upgrade, could you please reproduce the issue before manually logging in to the Telekom portal, and then connect to the router via SSH and run the following commands:
curl -v http://captive.apple.com/hotspot-detect.html
nslookup captive.apple.com
logread | grep -iE "portal|captive|gl-repeater"
Please share the command outputs with us. If possible, please also export the system log after reproducing the issue; you may send the system log to us via private message.
Thank you again for your patience and cooperation.
