Re: dnsmasq dhcp failure

I am trying the bind-interfaces option as  I use ppp


-z, --bind-interfaces 

On systems which support it, dnsmasq binds the wildcard address, even when it 
is listening on only some interfaces. It then discards requests that it 
shouldn't reply to. This has the advantage of working even when interfaces 
come and go and change address. This option forces dnsmasq to really bind only 
the interfaces it is listening on. About the only time when this is useful is 
when running another nameserver (or another instance of dnsmasq) on the same 
machine. Setting this option also enables multiple instances of dnsmasq which 
provide DHCP service to run in the same machine.





On Saturday, 26 November 2022 9:02:06 AM AEDT Erich Titl wrote:
> Hi Folks
> 
> News on the dhcp front
> 
> As reported before my dnsmasq installation would not hand out leases to 
> my winblows 10 over Wifi, well through a bridged configuration and an 
> external AP. Funny enough Android could get an address.
> 
> It may be noted that the system is _very_ old, a WRAP with really little 
> memory.
> 
> Also I found that for a certain time dhcp would run fine after system 
> boot. After some time it just degenerated.
> 
> Now I disabled dhcp in dnsmasq and installed the good old isc-dhcpserver 
> aka dhcpd, configured it accordingly and bingo, my win10 system gets its 
> address reliably and my Android system gets it _fast_.
> 
> I have seen this behaviour only on old systems with _very_ little 
> memory, I tend to still use them.
> 
> For the moment this configuration appears to be stable, but time will tell.
> 
> cheers
> 
> ET





------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/