The solution proposed by Alecz20 (alexguzu) works for me :)
--
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 n
I also see this issue after installing pihole which uses dnsmasq.
As a solution until we have a fix available, would it not be better to run
`sudo systemctl edit dnsmasq` and add the three lines:
[Unit]
After=network-online.target
Wants=network-online.target
rather than edit /lib/systemd/system/
** Changed in: dnsmasq (Ubuntu)
Status: In Progress => Confirmed
** Changed in: hundredpapercuts
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531184
T
** Changed in: dnsmasq (Debian)
Status: Unknown => New
--
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
Submitted patch upstream, will revisit in a couple weeks before taking
on an extra deviation in Ubuntu (since currently we do not have any
delta).
** Changed in: hundredpapercuts
Assignee: David Britton (davidpbritton) => (unassigned)
** Changed in: dnsmasq (Ubuntu)
Assignee: David Brit
** Also affects: dnsmasq (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774970
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531184
Tit
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => In Progress
** Changed in: hundredpapercuts
Status: Confirmed => In Progress
** Changed in: hundredpapercuts
Assignee: (unassigned) => David Britton (davidpbritton)
--
You received this bug notification because you are a me
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774970
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => David Britton (davidpbritton)
** Bug watch added: Debian Bug tracker #774970
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774970
--
You received this bug notification b
> 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?
dnsmasq (as opposed to dnsmasq-base) is not in main in Ubuntu, so relies
entirely on community support. It is not installed
I have found I needed to add
After=network-online.target
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
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
04:47 stgraber: do you have an opinion on the proposed fix for
bug 1531184 please?
04:49 rbasak: it's probably fine. Note that anyone who
actually has the dnsmasq package installed on their system is likely to
run into other problems, so not a big priority for us.
04:49 rbasak: (dnsmasq-base i
yeah, Immatix! Thanks so much
added
After=network-online.target
Wants=network-online.target
to the [Unit] section of /lib/systemd/system/dnsmasq.service
waiting for the fixed to be release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => High
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New => Confirmed
** Changed in: hundredpapercuts
Importance: Undecided => High
--
You received this b
I believe I was having the same problem, I use the --bind-interfaces
option as well as a few --interface options for different interfaces,
and dnsmasq would regularly fail to start during boot because one of the
interfaces wasn't present yet. Logs show dnsmasq was being started
before network.targ
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New => Confirmed
--
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:
dn
Adding the following to the [Unit] section of dnsmasq.service fixes the
problem:
After=network-online.target
Wants=network-online.target
--
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:
17 matches
Mail list logo
