When you are in a hotel when there is a captive portal, you have to disable your vpn and dns protection to get you authenticated via the portal. At that time, you data is leaked. Also, most user has difficult to set up and it is boring.
We have a daemon that detect if there is a captive portal. When there is, it will disable vpn and dns protection without leaking your data. When you get authenticated via the portal, vpn and dns will be restored.
We tested and it works in our testing environment. But the problem is that it is not efficient (like it may takes 30 to 40 seconds to detect) and does not work in all situations. So we do not have this in our default firmware.
Now because we have our smartphone app, we would rather to get this work with the app. So when there is a captive portal, your app will notify you and you need to use your smartphone to let the router works in portal detection mode. Using this it can improve user experience:
- The user knows what is happening when there is no Internet.
- The user can decide and get the portal page pop up quickly.
- The user data is not leaked.
Does the GL smartphone app work with the E750 for captive portal authentication?
would need exactly that also for the B1300
Not yet. This will be added later.
@alzhao Oh thank you. If you call the firrmwares “captive portal detect” it could be much more easy to know this. “portal” is not really specific.
It could also be really good to have explanations for each firmwares. Just small documents so peoples don’t always have to be guessing every time.
Just to get things clear. Portal detection is not implemented to latest Slate .100 firmware and i need to use that Portal Detect firmware?
Currently at the hotel and unable to see hotel captive portal at all. Ive used cellphone and MAC clone as trick to get internet for my Slate, but it isnt very effextive way
I just should revert firmware to Portal Detextion from test firmwares?
Well no. You can use the “normal” firmware and just disable DNS Rebind Protection from the DNS settings menu. The portal detect firmware was trying to avoid that manual setting, to act like your phone does, popping up the login webpage automatically for you, but it didn’t work well and was scrapped.
DNS Rebind is disabled, but im not able to enter portal credentials.
For me portal detect has been fine everytime, but for this trip updated the latest .100 firmware
If you still want to use the portal detection feature, it will need to be compiled manually unfortunately. You will have to follow the guide here:
Thanks @Johnex! Your link did lead me to the third thing, DNS encryption to be disabled and now getting the portal popup!
So, all good and not going to need custom firmware
Just a note if anyone else having the ”issue”.
- Disable all VPN connections in the router.
- Disable DNS rebind protection. This is generally true but not for all portal.
- Disable DNS encryption. In GL.iNet routers there are CloudFlare DNS.
would be nice if we can optional use that feature in future „offical“ firmware releases. example at least for Slate or Beryl?
I mean, can you put it in official firmware „disabled“ so the user can quickly decide to test it (enabling it)???
maybe i am simplifying things but i have been dealing with captive portals for many years.
the procedure is quick and easy, not cellphone app, no complex software/firmware in the gl-inet needed.
i connect to the captive portal via my cellphone using web browser.
then on my gl-inet usb150, i set its macid to the macid of the cellphone using mac clone.
Portal detecting is difficult. We have the source code on GitHub. Now it is COVID-19 everywhere and no way to test in different portals.
It also takes some time to detect the portal and not as efficient as manually set up.