On 15.08.2016 16:30, Louis Munro wrote: > >> On Aug 14, 2016, at 4:51 PM, [email protected] >> <mailto:[email protected]> 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 [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
