I'm a but stuck at the moment, wifi at work uses a captive portal to signin (or onboard to BYOD).
After some google-research, it looks like I need to do something with resolvconf but at present this is missing on my machine.
Did the trick with networkmanager & creating some [connectivity] settings... but no luck.
Any idea how to fix this?
Most captive portal will try to redirect HTTP requests to the captive portal for non authorised devices.
HTTPS may or may not work depending on the portal system.
I'm currently working away staying in a hotel with a flaky internet system and the captive portal is problematic here with the PBP.
My homepage on chromium is google so HTTPS which the portal doesnt intercept.
if I try an http page eg
http://bbc.co.uk the portal intercepts and I can authorise
The following morning if I try to connect again i have no internet until i authorise at which point bbc.co.uk noo longer works and i have to try an alternate http page to be captured to the portal.
I havent really dug into it yet, do you have any details about the changes you need to make.
NetManager sets up profiles for all your wifi networks and there is a Netmanager global config file, so somewhere in those files maybe a way to tweak the settings that you are trying to perform in resolvconf.
Linux n00b trying to learn.
Brute force and ignorance sometimes works!
| Pinebook Pro + Toshiba OCZ RC100 240GB |
network-manager will update resolv.conf upon connection with dhcp resolved nameservers. You don't edit this manually.
Strangely enough since I messed up the debian install (building a kali image), I've created a Manjaro SD card to boot from... Manjaro doesn't have this issue?
Nevermind my previous post. Think I'm sort of on the right track. I installed Resolvconf.
Did a dpkg-reconfigure resolveconf. Followed the steps & reboot.
After that it won't load the browser automaticatly but i'm able to enter 1.1.1.1 and reach the captive portal
Glad you got it working! I have a similar problem with the debian bullseye image. I don't see a portal notification from network manager, which the bug explains, but the portal detection in Firefox works: if there's a browser window open, it will show a bar at the top with a button to connect to the portal. After clicking whatever the captive portal page wants me to click, however, I have to turn wifi off and then on again before traffic is routed properly, which is definitely a bug. Fortunately, the particular captive portal I use frequently remembers the machine for a few hours so reconnecting is ok. Tedious though!
I haven't tried with the default image.
on debian sid arm64: connect to captive portal SSID, open a web browser, browse to any url, and be redirected to captive portal page.
I didn't do much testing, so it may be simpler.
Found it might be browser related. Firefox has no issues with the captive portal. Chrome doesn't want any of it. Both came from the default debian image.
