Captive Portal
Kraishak Mahtha
kraishak.edu at gmail.com
Tue Sep 21 05:56:05 UTC 2021
Hi All,
I am trying to implement a captive portal with cases like where users can
be guest,authenticated and unknown-clients without restarting the dhcp
service frequently.
Initially the client will be getting the IP from the quarantine range and
the user getting a custom portal page where he can be authenticated or
accept the terms and be as a guest.
I tried to use the concept of known and unknown-clients so that using omapi
concept i can add an authenticated client as known client so that it does
not need a restart of dhcp service.
but I want to add one more case where I can differentiate the clients also
as guest users
can anyone suggest to me any config element where I can differentiate all
these three cases(non-authenticated, authenticated and guest).
My sample config
==============
subnet 172.16.0.0 netmask 255.255.255.0 {
pool {
range 172.16.0.50 172.16.0.150;
allow unknown-clients;
option domain-name-servers 172.16.0.40
default-lease-time 120;
max-lease-time 120;
option routers 172.16.0.1;
option subnet-mask 255.255.255.0;
}
pool {
range 172.16.0.151 172.16.0.200;
deny unknown-clients;
option domain-name-servers 172.16.0.45
default-lease-time 1209600;
max-lease-time 1209600;
option routers 172.16.0.2;
option subnet-mask 255.255.255.0;
}
pool {
range 172.16.0.201 172.16.0.250;
<condition to accept guest client>
option domain-name-servers 172.16.0.45
default-lease-time 1209600;
max-lease-time 1209600;
option routers 172.16.0.2;
option subnet-mask 255.255.255.0;
}
}
Any help/suggestion would be much appreciated
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20210921/5601cfe0/attachment.htm>
More information about the dhcp-users
mailing list