Does the openwrt dhcp server support dhcp option 160, captive portal identification (https://tools.ietf.org/html/rfc7710)? I don't see it in the docs but figured it's worth asking since the related rfc is in proposed standard status...and since I don't see any other viable options for captive portal these days.
You can use dhcp options.
https://openwrt.org/docs/guide-user/base-system/dhcp.dnsmasq#configuring_dnsmasq_to_broadcast_external_dns_server_information
I have not tried 160 but others work, so give it a try.
3 Likes
DHCP Option 160 has been super-ced by 114.
Setting dhcp_option_force doesn't seem to have intended effect on dnsmasq.
dhcp.@dnsmasq[0].dhcp_option_force='114,http://local-captive-portal'
Can someone tell what is right way to send this dhcp option to WiFi AP clients?
2 Likes
It is a list parameter and the name is dhcp_option not dhcp_option_force.
This is the special case for when the network is not a captive portal. This can lead to faster connections since the endpoint may not probe for the Internet.
list dhcp_option '114, urn:ietf:params:capport:unrestricted'
4 Likes