That is not entirely true. Captive portal can be done without any
support in DHCP, but there is RFC support for DHCP:
https://www.rfc-editor.org/rfc/rfc8910.html#name-the-captive-portal-option
That option is useful for providing clients some expected URL.
DHCP option codes 114 (ipv4) and 103 (ipv6) are not recognized by
dnsmasq. I think it would be good to be added.
On 29/05/2017 14:13, Leonardo Rodrigues wrote:
absolutely not related with DHCP. Yes you'll need DHCP on yout
hotspot, but the captive portal is in no way done by the DHCP service.
Google exactly for 'captive portal' and you'll find solutions for
that, lots free and paid options if you want to.
Em 29/05/17 08:12, Jorge Bastos escreveu:
Howdy,
I think this is done by DHCP, and if not let me know it.
I want to put the some devices to open the browser to signin in my
hotspot via captive portal.
That is, when the devices connect to the WIFI network, the browser
automatically open's, this on smartphones/tablet/similar (i've seen
windows doing it aswell).
Is this done by an DHCP option, if yes any ideia on how to?
--
Petr Menšík
Software Engineer, RHEL
Red Hat, https://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
_______________________________________________
Dnsmasq-discuss mailing list
[email protected]
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
