Xenial has reached end of standard support.
** Changed in: dnsmasq (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
** Tags added: network-online-ordering
--
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/1531184
Title:
[SRU] dnsmasq doesn't start on boot because its interface isn't up
The Debian maintainer suggested to also add a WantedBy= entry in the
Install section:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774970#32
** Also affects: dnsmasq (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: dnsmasq (Ubuntu Xenial)
Importance:
For my case, I simply cannot update the systemd to solve this problem
since the address I want to bind belongs to virtual tunnel device which
only gets added when there is a new tunnel connection. Oops!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Terrence Houlahan's fix also works for me on 18.04 Many thanks!
--
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/1531184
Title:
[SRU] dnsmasq doesn't start on boot because
For my installation, I found that dnsmasq is running with -7
/etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new arguments.
/etc/dnsmasq.d/libvirt-daemon specified bind-interfaces, causing dnsmasq
trying to bind to each interface on startup, which was unfortunately not
available yet.
Comment out the
On Tue, Sep 24, 2019 at 04:57:59PM -, Benjamin Bach wrote:
> @Robie Basak
>
> > Will this delay boot for laptop users who are offline, for example?
>
> If someone has installed the dnsmasq package with the dnsmasq.service
> file, they already intend to run this as a network-dependent
Adding to my previous message: After=NetworkManager-wait-online.service
will not work, as it doesn't respect for instance setups where networkd
handles connections.
@Robie Basak
> Will this delay boot for laptop users who are offline, for example?
If someone has installed the dnsmasq package
Thanks Christian. This bug was already on my list.
More details here:
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
It is not obvious to me that adding After/Wants=network-online.target to
the packaging for _all_ users, or anything similar, is the correct fix
here. Will this
@Robie - I subscribed you as I wondered if this is another one for your
list of bugs related to "binding to IPs available late".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
The fix by Terrence Houlahan works for me on 18.04. Thanks!
However, I'm wondering if adding this "After" clause is a problem since
the package doesn't currently depend on Network Manager? Does
"NetworkManager-wait-online.service" satisfy a more generic SystemD
target?
>From the dnsmasq package:
** Description changed:
[Impact]
- TBD
+ dnsmasq will fail to respond on network devices that weren't up when its
+ service started, thus not binding as expected.
[Test Case]
TBD
[Regression Potential]
The fix is just configuring the order of service startup, so is unlikely to
The reference paelzer references is related to Ubuntu 14.04. In Ubuntu
18.04, "/etc/netplan/01-network-manager-all.yaml" defaults all network
device management to NetworkManager. Therefore any solution will have
to be to NetworkManager's systemd service file.
My solution which I've tested and
Added bug 1777094 as a dup which is about the same issue (and
essentially the same suggested solution).
Also related on askubuntu:
https://askubuntu.com/questions/536787/dnsmasq-starting-before-eth0-is-ready-and-therefore-not-binding
--
You received this bug notification because you are a
** Description changed:
[Impact]
TBD
[Test Case]
TBD
[Regression Potential]
+ The fix is just configuring the order of service startup, so is unlikely to
create any regressions. Things to watch would be service related misbehaviors
and general availability of the dnsmasq
** Description changed:
+ [Impact]
+ TBD
+
+ [Test Case]
+ TBD
+
+ [Regression Potential]
+
+ [Fix]
+
+ [Discussion]
+
+ [Original Report]
+
My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is
managed manually in /etc/network/interfaces.
During boot, dnsmasq is
** Summary changed:
- dnsmasq doesn't start on boot because its interface isn't up yet
+ [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in
17 matches
Mail list logo
