<div dir="ltr">Hi Simon,<div><br></div><div>thanks for your reply. </div><div><br></div><div>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. </div><div><br></div><div>Many thanks,</div><div>Florian</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 26, 2023 at 6:21 PM Simon Kelley <<a href="mailto:simon@thekelleys.org.uk">simon@thekelleys.org.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">What I can't get from a quick reading of the RFCs it how the <br>
captive-portal URI is derived from the client characteristics. The RFCs <br>
imply that the final, encoded part of the URI is an opaque identifier <br>
that's returned by the DHCP part of the captive portal and then accepted <br>
by the http part. It's not even clear to me that it needs to be unique <br>
to a client. Enlightenment on this matter would be appreciated.<br>
<br>
One thing that should be done and it very easy is to add the RA option <br>
in the same way that others are just derived from the corresponding <br>
DHCPv6 option.<br>
<br>
Simon.<br>
<br>
<br>
<br>
On 26/05/2023 13:20, Florian Baaske via Dnsmasq-discuss wrote:<br>
> Hi Pert,<br>
> <br>
> thanks for the help. Much appreciated.<br>
> <br>
> I found something in regards to ISC as the DHCP server and thought that <br>
> DNSMASQ might have the same feature.<br>
> <br>
> BR<br>
> Florian<br>
> <br>
> On Fri, May 26, 2023 at 12:26 PM Petr Menšík <<a href="mailto:pemensik@redhat.com" target="_blank">pemensik@redhat.com</a> <br>
> <mailto:<a href="mailto:pemensik@redhat.com" target="_blank">pemensik@redhat.com</a>>> wrote:<br>
> <br>
> Added captive-portal DHCP option to database.<br>
> <br>
> But I am afraid dnsmasq can serve different URLs only for explicitly<br>
> registered clients with separate options. It cannot make the url<br>
> dynamically based on incoming request. There is no script able to<br>
> customize offered options online.<br>
> <br>
> On 5/26/23 09:16, Florian Baaske via Dnsmasq-discuss wrote:<br>
>><br>
>> Hi,<br>
>> I would like to setup a Guest network with DNSMASQ. For that Guest<br>
>> network, I would like to use CAPPORT or RFC8908.<br>
>> To make this work, the DHCP server needs to send option 114, which<br>
>> should not be a problem, but option 114 should have the URL to the<br>
>> CAPPORT server including the MAC address of the client.<br>
>> So, my questions would be, is it possible to include the clients<br>
>> MAC address in the DHCP response?<br>
>> I have found a solution for ISC DHCP but was not able to find<br>
>> anything for DNSMASQ. If someone could help, this would be much<br>
>> appreciated.<br>
>><br>
>> BR<br>
>> Florian<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Dnsmasq-discuss mailing list<br>
>> <a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a> <mailto:<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a>><br>
>> <a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a> <<a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a>><br>
> <br>
> -- <br>
> Petr Menšík<br>
> Software Engineer, RHEL<br>
> Red Hat,<a href="https://www.redhat.com/" rel="noreferrer" target="_blank">https://www.redhat.com/</a> <<a href="https://www.redhat.com/" rel="noreferrer" target="_blank">https://www.redhat.com/</a>><br>
> PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB<br>
> <br>
> _______________________________________________<br>
> Dnsmasq-discuss mailing list<br>
> <a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
> <mailto:<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a>><br>
> <a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a> <<a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a>><br>
> <br>
> <br>
> _______________________________________________<br>
> Dnsmasq-discuss mailing list<br>
> <a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
> <a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a><br>
<br>
_______________________________________________<br>
Dnsmasq-discuss mailing list<br>
<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br>
<a href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a><br>
</blockquote></div>