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 Petr Menšík <pemen...@redhat.com> wrote: > 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 to hwaddr or even DHCP options used should be possible. I > think captive portal web server should be able to make dynamic responses > based on who is asking. I expect using dhcp-script like libvirt does > should allow the captive-portal service make customized responses with > single URL. But the complexity would be at the web service, I think they > are usually better prepared for that than DHCP services. > > On 5/26/23 17:27, Simon Kelley wrote: > > 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. It's not even clear to me that it > > needs to be unique to a client. Enlightenment on this matter would be > > appreciated. > > > > One thing that should be done and it very easy is to add the RA option > > in the same way that others are just derived from the corresponding > > DHCPv6 option. > I think we should add a way to add RA options similar way to DHCP. I > were looking at RFC 8781 PREF64, it does not define any related DHCPv6 > option. So instead of relying on re-using option6: for RA, could we add > possibility to directly add --ra-option? Specification via dhcp-option > is often okay, but not always. Ideally with ability to encode even > unsupported option like dhcp can, making it ready for future options too. > > > > Simon. > > > > > > > > On 26/05/2023 13:20, Florian Baaske via Dnsmasq-discuss wrote: > >> 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 <pemen...@redhat.com > >> <mailto:pemen...@redhat.com>> wrote: > >> > >> 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 09:16, Florian Baaske via Dnsmasq-discuss wrote: > >>> > >>> Hi, > >>> I would like to setup a Guest network with DNSMASQ. For that Guest > >>> network, I would like to use CAPPORT or RFC8908. > >>> To make this work, the DHCP server needs to send option 114, which > >>> should not be a problem, but option 114 should have the URL to the > >>> CAPPORT server including the MAC address of the client. > >>> So, my questions would be, is it possible to include the clients > >>> MAC address in the DHCP response? > >>> I have found a solution for ISC DHCP but was not able to find > >>> anything for DNSMASQ. If someone could help, this would be much > >>> appreciated. > >>> > >>> BR > >>> Florian > >>> > >>> > -- > Petr Menšík > Software Engineer, RHEL > Red Hat, https://www.redhat.com/ > PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB > > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss >
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
