HI all, Sorry to bump an old ish topic, but this is an issue we're seeing a lot of. Users are seeing the HSTS error when trying to connect to our Guest network and I'm not sure the best way around this, if there's any way at all.
In our config (6.2.1) we have both captive portal detection bypass and WISPr enabled. However to my understanding one is in contradiction to the other. Don't we want the device to recognise that it's in a captive portal in order to display the WISPr page? The snippet from our pf.conf shows: [captive_portal] # # captive_portal.detection_mecanism_bypass # # Bypass the captive-portal detection mechanism of some browsers / end-points by proxying the detection request. detection_mecanism_bypass=enabled # # captive_portal.detection_mecanism_urls # # Comma-delimited list of URLs known to be used by devices to detect the presence # of a captive portal and trigger their captive portal mechanism. detection_mecanism_urls=http://connectivitycheck.gstatic.com/generate_204 Cheers, Andi From: g4-l...@tonarchiv.ch [mailto:g4-l...@tonarchiv.ch] Sent: 16 August 2016 01:36 To: packetfence-users@lists.sourceforge.net Subject: Re: [PacketFence-users] Captive Portal and SSL - Unresolvable task? On 15.08.2016 16:30, Louis Munro wrote: On Aug 14, 2016, at 4:51 PM, g4-l...@tonarchiv.ch<mailto:g4-l...@tonarchiv.ch> wrote: Can you please explain me in a few words what the option captive_portal.wispr_redirection does? What happens on a WISPr capable device when we use packetfence with captive portal, and this option is enabled? It will return a XML WISPr payload to the device instead of an html page, telling it where to login. The device should then open it's WISPr client and connect to the provided URL. If you disable that option, WISPr will not be detected or acted upon. So what we see in the end is our captive portal nevertheless? But it is not possible to tell a WISPr client to open a real browser and redirect him to a page at the end, when Internet has been granted? And - last question - : This captive portal detection mechanism and WISPr are depending on each other? I.e. when i enable the option "Captive Portal detection mechanism bypass" then WISPr ability of Packetfence can not be triggered? Thank you for your help, I appreciate this very much! Till
------------------------------------------------------------------------------
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
