This is a _very_ old platform, running 2.47.
What happens is that a client requests it's previous address in the DHCP
DISCOVER packet, and that's ack'd as ok by dnsmasq, even though it differs
from the address as specified in the dhcp-hosts file that's in use.
On a much newer build of dnsmasq, I
Good idea. If I think about it I'll trace this next time I'm in a
hotspot.
On May 27, 2014 2:54 AM, "Albert ARIBAUD" wrote:
> Hi Donald,
>
> Le Mon, 26 May 2014 21:23:27 -0300, Donald Chisholm
> a écrit :
>
> > Hi all,
> >
> > Recently I have noticed that on connect some wifi hotspots provide a
Thanks Alex. I was able to confirm that both my Android and Windows
machine on a new dhcp lease the machine makes a request for a particular
url and if that is redirected presents the captive portal message.
I'm going to take a closer look at the dhcp messages to confirm when this
is happening.
On 26/05/14 08:23 PM, Donald Chisholm wrote:
> Recently I have noticed that on connect some wifi hotspots provide a popup
> message indicating that the user must login to obtain Internet access.
> Since the user has not yet opened a browser I figure this feature is
> implemented via a DHCP option.
I think I have finally fathomed out why my new dnsmasq installation on
my desktop machine didn't work whereas an apparently idetical setup on
a small server did work.
I *think* it's because Network Manager puts a file in /etc/dnsmasq.d
that just has one directive in it:-
bind-interfaces
I beli
