Hello Erich, thank's for your answer, I commented out background in dhcpcd.conf and voila ! it works as before, great ! , here is the daemon.log: (I changed my IP address .111)
Sep 19 13:16:43 firewall dhcpcd[11715]: version 6.7.1 starting Sep 19 13:16:43 firewall dhcpcd[11715]: eth0: soliciting a DHCP lease Sep 19 13:16:43 firewall dhcpcd[11715]: eth0: offered 96.23.216.111 from 10.23.113.85 Sep 19 13:16:48 firewall dhcpcd[11715]: eth0: leased 96.23.216.111 for 3600 seconds Sep 19 13:16:48 firewall dhcpcd[11715]: eth0: adding route to 96.23.216.0/24 Sep 19 13:16:48 firewall dhcpcd[11715]: eth0: adding default route via 96.23.216.1 Sep 19 13:16:48 firewall dhcpcd[11715]: forked to background, child pid 11742 Sep 19 13:16:48 firewall dnsmasq[11767]: started, version 2.75 cachesize 150 Sep 19 13:16:48 firewall dnsmasq[11767]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify Sep 19 13:16:48 firewall dnsmasq-dhcp[11767]: DHCP, IP range 192.168.1.100 -- 192.168.1.199, lease time 12h Sep 19 13:16:48 firewall dnsmasq[11767]: using local addresses only for domain private.network Sep 19 13:16:48 firewall dnsmasq[11767]: reading /etc/dhcpc/resolv.conf Sep 19 13:16:48 firewall dnsmasq[11767]: using local addresses only for domain private.network Sep 19 13:16:48 firewall dnsmasq[11767]: using nameserver 23.233.128.16#53 Sep 19 13:16:48 firewall dnsmasq[11767]: using nameserver 24.225.128.17#53 Sep 19 13:16:48 firewall dnsmasq[11767]: using nameserver 24.202.72.13#53 Sep 19 13:16:48 firewall dnsmasq[11767]: read /etc/hosts - 8 addresses Sep 19 13:16:50 firewall mini_httpd[12153]: bind 0.0.0.0 - Address already in use Sep 19 13:16:50 firewall mini_httpd[12154]: started as root without requesting chroot(), warning only Sep 19 13:16:50 firewall mini_httpd[12154]: mini_httpd/1.19 19dec2003 starting on firewall, port 80 Sep 19 13:16:50 firewall heyu_relay: relay setting up- Sep 19 13:16:46 firewall init: starting pid 12184, tty '/dev/tty1': '/sbin/getty 38400 tty1' Sep 19 13:16:46 firewall init: starting pid 12185, tty '/dev/tty2': '/sbin/getty 38400 tty2' Sep 19 13:16:47 firewall dnsmasq-dhcp[11767]: DHCPDISCOVER(eth1) a4:77:33:ea:6e:7e Sep 19 13:16:47 firewall dnsmasq-dhcp[11767]: DHCPOFFER(eth1) 192.168.1.118 a4:77:33:ea:6e:7e Sep 19 13:16:47 firewall dnsmasq-dhcp[11767]: DHCPREQUEST(eth1) 192.168.1.118 a4:77:33:ea:6e:7e Sep 19 13:16:47 firewall dnsmasq-dhcp[11767]: DHCPACK(eth1) 192.168.1.118 a4:77:33:ea:6e:7e Chromecast Have a good day, jrb. Le 2016-09-18 à 18:28, Erich Titl <erich.t...@think.ch> a écrit : > Hi Jean-Roch > > Am 18.09.2016 um 22:55 schrieb Jean-Roch Blais: >> Hello list, sorry for the hard to read previous post ... >> > ... > >> >> I can also use the original BUC 5.2.5 dhcpcd.lrp but I have to add in >> /etc/default/local.start: >> >> sleep 5 >> dnsmasq >> >> and it works again ! >> >> facinating :-( !!! > > Well possibly dnsmasq is the culprit and not necessarily dhcpcd. I would like to understand why dnsmasq might be the culprit, please ! > > The only thing I would like to suggest is to verify the following > setting in dhcpcd.conf > > background > > This causes dhcpcd to fork into background immediately and continue with > execution of the init scripts without waiting for dhcpcd to get an > uplink address and without a reasonable resolv.conf file. > Can you explain why this feature is there ? I guess it works fine with the other breeds of dhcp clients, but not with dhcpcd in combination with dnsmasq ... > this can be seen in your log file > > Sep 18 15:28:14 firewall dnsmasq[11765]: directory > /etc/dhcpc/resolv.conf for resolv-file is missing, cannot poll > Sep 18 15:28:14 firewall dnsmasq[11765]: FAILED to start up > > The setting for resolv.conf in dhcpcd IMHO is debatable anyway. > >> I can also use the original BUC 5.2.5 dhcpcd.lrp but I have to add in >> /etc/default/local.start: >> >> sleep 5 >> dnsmasq > > Of course, as this only does what your manual invocation of dnsmasq is > doing. > Yes I knew that, I was simply trying to point out, a work around in case someone inexperienced might have this problem... my humble contrib. :-) > So I if your uplink dhcp server is sufficiently slow, this may happen > anytime, it can probably be mitigated by removing the background keyword > from dhcpcd.conf > > cheers > > Erich > > > ------------------------------------------------------------------------------ > ------------------------------------------------------------------------ > leaf-user mailing list: leaf-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ ------------------------------------------------------------------------------ ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
