When upgrading to 26.1.6, the function of captiveportal not authenticating addresses and subnets in this list becomes ineffective,What happened?
Can you please be a lot more specific?
Thanks,
Franco
Thanks, Before upgrading avoid authentication for addresses and allow access the network，But now these addresses unable to access the network. it also cannot authenticate portal web pages.
Great！When I disabled the Client roaming , the captiveportal whitelist returned to normal.
Thanks for the hint. This makes it a lot easier to look for the issue.
GitHub PR (assume you created it too) is https://github.com/opnsense/core/issues/10124
Cheers,
Franco
Quote from: ly.hu on April 13, 2026, 06:35:09 AMGreat！When I disabled the Client roaming , the captiveportal whitelist returned to normal.
Thanks! Both for the thread and for the work-around hint.
I was confounded. The firewall seemed to be starting perfectly, it was just refusing to talk to me. No ping, no web portal access, no nothing it seemed. But the console showed everything looked normal. Damned Captive Portal catches me out every time!
I had trouble at first because I had restored to 26.1.5 to get portal access again and (of course) there was no Client Roaming option there to disable. Finally realised I had to upgrade and then do a captive portal login from a system that wasn't on the allowed list, then I could disable the Client Roaming option and everything started working again! (Adding this last note for anyone else seeing this thread.)