I have openvswitch-switch, which did required from me to apply some
changes to systemd service file that seems not to be aware of virtual
devices up.
So, bottom line, /etc/network/interface files are taking action in a way
that smashes the rush to boot up, so dnsmasq also become a victim, and
for me the solution above was not compatible.
So I had to add to dnsmasq.service the follow lines:
Requires=sys-subsystem-net-devices-<needed device>.device
After=sys-subsystem-net-devices-<needed device>.device
Wants=sys-subsystem-net-devices-<needed device>.device
Got the above info from
systemctl --full | grep subsystem
Best regards!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531184
Title:
dnsmasq doesn't start on boot because its interface isn't up yet
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
