Hi Petr,
this might be true, but for the setup, I'm looking for the captive portal
service will be an appliance which is not able to talk to the DHCP service,
running on a different service. Thats why they need the information using
the provided URL.
BR
Florian
On Tue, May 30, 2023 at 3:26 PM
I would expect the captive-portal service should be able to fetch
low-level data from DHCP server doing the address assignment for it. It
would guess the service is always operated by the same entity of they
are cooperating. Very often they would be running on the same device. So
mapping of IP
Hi Simon,
thanks for your reply.
The mac address is required by the CAPPORT implementation I would like to
use. I will not say that the mac address is always required when using
CAPPORT but for the selected implementation (Aruba ClearPass) it is
required.
Many thanks,
Florian
On Fri, May 26,
What I can't get from a quick reading of the RFCs it how the
captive-portal URI is derived from the client characteristics. The RFCs
imply that the final, encoded part of the URI is an opaque identifier
that's returned by the DHCP part of the captive portal and then accepted
by the http part.
Hi Pert,
thanks for the help. Much appreciated.
I found something in regards to ISC as the DHCP server and thought that
DNSMASQ might have the same feature.
BR
Florian
On Fri, May 26, 2023 at 12:26 PM Petr Menšík wrote:
> Added captive-portal DHCP option to database.
>
> But I am afraid
Added captive-portal DHCP option to database.
But I am afraid dnsmasq can serve different URLs only for explicitly
registered clients with separate options. It cannot make the url
dynamically based on incoming request. There is no script able to
customize offered options online.
On 5/26/23
