Page MenuHomeFreeBSD

dhclient-script: store the Captive Portal URI
ClosedPublic

Authored by bapt on Fri, Oct 2, 8:13 PM.
Tags
None
Referenced Files
F176304566: D60259.id188967.diff
Sat, Oct 17, 7:12 PM
Unknown Object (File)
Fri, Oct 16, 9:53 AM
Unknown Object (File)
Fri, Oct 16, 8:00 AM
Unknown Object (File)
Fri, Oct 16, 2:43 AM
Unknown Object (File)
Wed, Oct 14, 12:11 AM
Unknown Object (File)
Tue, Oct 13, 11:26 AM
Unknown Object (File)
Sun, Oct 11, 7:42 AM
Unknown Object (File)
Sun, Oct 11, 4:32 AM

Details

Summary

Write the URI received in DHCP option 114 to
/var/run/captive-portal.IFACE atomically, with the legacy option 160 as
a fallback, and remove the file on EXPIRE and FAIL.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

bapt requested review of this revision.Fri, Oct 2, 8:13 PM
bcr added a subscriber: bcr.

OK for the man page part of the change.

This revision is now accepted and ready to land.Sat, Oct 3, 5:43 PM

Thanks for RFC 8910 support in dhclient. Can we count on such an enhancement for rtosld(8)? Are there any ongoing efforts to implement point 2.3 from tis RFC "The Captive-Portal IPv6 RA Option" ?

I have it, but I had no way to test it hence why I haven't pushed, it, do you have a test env for that?

It seems that testing this properly requires relatively modern network equipment that supports the Captive-Portal IPv6 RA Option. On the other hand, net/radvd in the FreeBSD ports tree supports the option, so I should be able to set up a test environment. I will most likely have some time to prepare it and run the tests before the upcoming RIPE 93.