Re: Captive Portal

Hi Greg,

I am using the latest version of dhcpd 4.4.2 so I guess I can use this
concept, I tried checking the ISC documents but somehow I missed this page
but again thanks for the suggestion
>>I'd recommend testing/tinkering on a VM/test server that's non-production
to see if it actually does what you want. :)
---> Sure I will test it on my test server first
--Kraishak

On Thu, Sep 23, 2021 at 10:09 AM Gregory Sloop <[email protected]> wrote:

> Google is your friend...
>
>
>
> Depending on what dhcpd version you're using, it sure looks like OMAPI
> classes support exists.
>
>
>
> https://kb.isc.org/docs/aa-01092
>
>
>
> Since I can never get OMAPI to do what I want the first time (or even the
> forty-third time), I'd recommend testing/tinkering on a VM/test server
> that's non-production to see if it actually does what you want. :)
>
>
>
> -Greg
>
>
>
>
> Hi Simon,
>
> Thank you for the suggestions, but to add the subclasses statements into
> the config I need to stop the service and start the service, when I get
> multiple clients request it may lead to crash of my dhcp service because of
> multiple stops and starts
> do we have any way where I can include the statements into some other file
> and include that into the main config file? or can we use any omapi to load
> the statements dynamically without restarting the service
>
> Thanks
>
>
> On Tue, Sep 21, 2021 at 11:26 AM Kraishak Mahtha <[email protected]>
> wrote:
>
>> 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
>>
>
> --
> Gregory Sloop, Principal: Sloop Network & Computer Consulting
> Voice: 503.251.0452 x121
> EMail: [email protected]
> http://www.sloop.net
> ---
>

_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users