dhcp-server: implement captive portal option (RFC8910) #176
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Clients observing the URI value "urn:ietf:params:capport:unrestricted" may forego time-consuming forms of captive portal detection.
https://datatracker.ietf.org/doc/html/rfc8910
Another option is to provide an URL to an Captive Portal API (RFC8908). This can be static JSON. In the Freifunk context the
venue-info-url
is probably the most interesting part. When set Users of Android 11 an up are getting a Notifcation which links to the URL provided viavenue-info-url
. Also it's visible in the Details of the Wifi. For iOS the Link will also be visible there.https://developer.android.com/about/versions/11/features/captive-portal?hl=de
Providing an actual Captive Portal API hoewer comes with the drawback of requiring a request to the Captive Portal API until a client knows it isn't restricted. Not worse then the current check most clients will presumably do currently but also not better.
For an example of an Captive Portal API see https://darmstadt.freifunk.net/captive