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,
On 26/05/2023 17:19, Simon Kelley wrote:
The long delay awaiting a connection from a non-responsive server may be
improved by reducing the value of the TCP_SYNCNT socket option, at least
on Linux.
Setting TCP_SYNCNT to 2 limits the delay for a non responsive address to
about 8 seconds,
On 25/05/2023 20:32, Petr Menšík wrote:
This problem is best tested by an example, taken from [2] but a bit
modified.
Let's create hepothetical network issue with one forwarder, which worked
fine a while ago.
$ sudo iptables -I INPUT -i lo -d 127.0.0.255 -j DROP
Now start dnsmasq and
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
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
