*** This bug is a duplicate of bug 1531184 ***
https://bugs.launchpad.net/bugs/1531184
Hi Terrence, yeah and while yours is still NetworkManager specific it is
still essentially the same as bug 1531184 - making this a dup to have
all on one.
** This bug has been marked a duplicate of bug 1531
In respect to my above post, the correct target of the sed expression
should be as follows:
sed -i 's/After=network.target/After=NetworkManager-wait-online.service/'
/lib/systemd/system/dnsmasq.service
Please note the fix remains nonetheless valid and ensures that dnsmasq rises up
correctly o
The problem lives in the [Unit] section in the After= directive which
when modified as follows raises dnsmasq.service unbroken on boot:
sed -i 's/After=network.target/After=NetworkManager-wait-
online.service/' /etc/systemd/system/multi-
user.target.wants/dnsmasq.service
That's a fairly tidy, and
[Expired for dnsmasq (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bu
[Expired for netplan.io (Ubuntu) because there has been no activity for
60 days.]
** Changed in: netplan.io (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
http
On Tue, Jun 19, 2018 at 9:41 AM Hadmut Danisch 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 v
dnsmasq _after_ networking?
Isn't it part of networking and should be running and ready for other
services depending on networking?
(my guess is that Ubuntu has never defined the targets very precisely. it
should distinguish between low level /interface level configuration and
networking servi
I see, interesting. The dnsmasq.service does not wait for
network-online.target;
This appears to be a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1531184
In addition to the netplan config to ensure it waits for your bridge
to come up, you need to delay dnsmasq.service u
setting optional: false does not solve the problem, a systemctl
restart dnsmasq is still required.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1777094
Title:
dnsmasq
https://netplan.io/faq#example-for-an-ifupdown-legacy-hook-for-post-
uppost-down-states
You can use a networkd-dispatcherd to hook on vlan0 becoming routeable
and then start/restart the dnsmasq service;
On Fri, Jun 15, 2018 at 12:36 PM, Hadmut Danisch wrote:
> So it is not possible to have an i
So it is not possible to have an interface as optional (for other
reasons beyond that example) and still have a dnsmasq running for it?
In former versions of ubuntu I had my bridges (some containing usb
ethernet interfaces to bridge virtual with physical machines) configured
in /etc/network/if-up.
In your netplan example config, keyword 'optional' means that systemd-
networkd won't wait until this interface is up before declaring to
systemd that the network is online. THis means dnsmasq is starting
before the vlan0 interface is created.
If you remove the optional value that should ensure i
12 matches
Mail list logo
