Comment 8 for bug 1531184
Revision history for this message
| John Radley (jradxl) wrote Re: dnsmasq doesn't start on boot because its interface isn't up yet | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I have found I needed to add
After=
to dnsmasq.service
to ensure my ethernet port, ens18, is available, on boot.
Using Ubuntu 16.04.2
In my case, I am using dnsmasq as per the PiHole installation where the IP is static and dhcpclient is turned off. But this is clearly not a PiHole problem as it just installs Dnsmasq.
Rather surprised I need to add this report, and that this Bug report isn't a higher Importance and not resolved in 3 months.
Surely loads of users will have this issue?
Kind Regards