Comment 10 for bug 1777094
Revision history for this message
| Ryan Harper (raharper) wrote Re: [Bug 1777094] Re: dnsmasq started too early, not getting all interfaces | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
On Tue, Jun 19, 2018 at 9:41 AM Hadmut Danisch <email address hidden> wrote:
>
> dnsmasq _after_ networking?
>
> Isn't it part of networking and should be running and ready for other
> services depending on networking?
Yes, but it's complicated; see below.
>
>
> (my guess is that Ubuntu has never defined the targets very precisely. it should distinguish between low level /interface level configuration and networking services.)
>
This is rather precisely defined; not by Ubuntu but by the init
system. In systemd there are many targets that indicate various state
of the system during boot[1][2]
For networking, the ones that matter are:
network-pre.target (before systemd has attempted to bring the network up)
network.target (systemd has started to bring network up; for
Artful/Bionic, this means systemd-
network-
configured, routable)
Dnsmasq itself is a networking service, so arguably, it is fine to run
at After=network.
all of networking has been configured. Dnsmasq has two choices. 1)
it can run later, at network-
done with creating and configuring interfaces. 2) start at
After=network.
when a
configured interface is present and ready for it to use.
Since dnsmasq does not watch dbus or netlink for new interfaces and
when they're configured, then the only solution is to run after such
a time that the configured interfaces are ready for use by dnsmasq.
1. https:/
2. https:/
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> dnsmasq started too early, not getting all interfaces
>
> To manage notifications about this bug go to:
> https:/