[Dnsmasq-discuss] dnsmasq tries to start up before eth0 is ready, how to fix?

Albert ARIBAUD albert.aribaud at free.fr
Sun May 25 18:09:09 UTC 2014


Bonjour Chris,

Le Sun, 25 May 2014 19:02:18 +0100, Chris Green <cl at isbd.net> a écrit :

> I have the following in my dnsmasq.conf file:-
> 
>     listen-address=192.168.1.4
>     listen-address=127.0.0.1
> 
> In syslog when I reboot I'm seeing:-
> 
>     May 25 18:45:07 chris dnsmasq[1300]: failed to create listening socket for 192.168.1.4: Cannot assign requested address
>     May 25 18:45:07 chris dnsmasq[1300]: FAILED to start up
> 
> The reason is simple to see, eth0 (which is 192.168.1.4) only comes up
> three seconds later:-
> 
>     May 25 18:45:10 chris NetworkManager[1305]: <info> (eth0): carrier now ON (device state 20)
>     May 25 18:45:10 chris NetworkManager[1305]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
>     May 25 18:45:10 chris kernel: [   40.576716] r8169 0000:03:00.0 eth0: link up
>     May 25 18:45:10 chris kernel: [   40.576730] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> 
> 
> Is there any way to make dnsmasq wait for eth0 to be ready?  Or,
> alternatively, as I originally had (but don't seem to get by default
> on this system) how do I get dnsmasq to accept input from anywhere?

I benlieve the option --bind-dynamic can help, if it is available to
you.

Amicalement,
-- 
Albert.



More information about the Dnsmasq-discuss mailing list