Captive Portal with Windows 11
Next DNS does not work in public wifis with captive protals: The login page does not show up, and it's not possible to go online at all. The only solution I found for this problem is to uninstall the windows client: There is an urgend need for a temporary disable feature!
5 replies
-
This is also an issue with windows 10. I was able to go into task manager and disable the nextdns service to get by this issue but it is definitely a problem.
I also don't like that the tray icon disappears when using UI=0. It would be better to have the tray there and have an option for the user to disable nextdns for 3 minutes to allow capitve portal login first. Cloudflare client has this, but I ran into more issues with that client anyways.
This is a pretty big deal I think for anyone that travels (all of us) so it would be nice to be able to provide some feedback and improve?
-
Having to remove nextdns until I find a consistent solution.
turning off dns rebinding does not work. Managed to get the link for one of the captive portals and add it to white list during deployed install... no go. Thought about adding the SSID, but thats not really what I want (no filtering at all when connected?)
Alternative hack atm is to disable, connect, then reenable. Option B to this is a scheduled task that disables the service at boot, waits 10 min, then starts service again.
Any other suggestions most welcome.
Content aside
- 2 mths agoLast active
- 5Replies
- 360Views
-
5
Following