-
Notifications
You must be signed in to change notification settings - Fork 275
Description
Hello,
I'm opening a new issue concerning RFC8910/RFC8908 . From what I read:
If the API server needs information about the client identity that is not otherwise visible to it, the URI provided to the client during provisioning SHOULD be distinct per client. Thus, depending on how the Captive Portal system is configured, the URI will be unique for each client host and between sessions for the same client host.
The problem is that currently it seems that Coova-Chilli does not allow to give any specific paramters to the API url, that are specific to the client. From what I read
if (_options.captiveportalapi_uri) {
o[pos++] = DHCP_OPTION_CAPTIVE_PORTAL_URI;
o[pos++] = strlen(_options.captiveportalapi_uri);
memcpy(&o[pos], _options.captiveportalapi_uri, strlen(_options.captiveportalapi_uri));
pos += strlen(_options.captiveportalapi_uri);
if (_options.debug)
syslog(LOG_DEBUG, "%s(%d): DHCP Captive Portal API URI %s\n", __FUNCTION__, __LINE__, _options.captiveportalapi_uri);
}
https://github.com/coova/coova-chilli/blob/master/src/dhcp.c
The problem with that is that no distant API could work correctly without any information to identify the client. It would be good to have the possibility to customize the url of the API, with the mac of the client and/or a random ID, and possibly specify as well the nasid of the Coova-chilli instance, and possibly other infos.