[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
Hi,
I had a look at [1] and AIUI this wasn't recognized as an upstream bug.
I also can't find a relevant Debian bug about this issue. The bug
description says it affected Xenial, which is now in Extended Security
Maintenance, so it's a Won't Fix there.
For >= Bionic we need confirmation from an a
Hi Christian,
Simon, the dnsmasq developer and Debian maintainer, frequently answers here in
launchpad as well (and there's no upstream bug tracker).
In any case, I did forward the report to the dnsmasq mailing list:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2016q4/011010.html
Tha
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => High
--
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/1651044
Title:
ProxyDHCP replies on invalid range
Status i
Hi Alkis,
thank you for your report and your help to make Ubuntu better.
I like your preanalysis and agree to your assumption of some sort of bad
initialization.
This bug is present in Debian too, and Ubuntu currently doesn't make any
changes over the Debian package. So this bug would be best fi
I did another test:
* I unplugged the network cable so that the ltsp-server didn't have an ip.
* I ran `service dnsmasq restart`.
* I plugged the network cable back in.
* ...and the problem came back again, i.e. dnsmasq replied on invalid range.
This again suggests that it's some kind of wrong
6 matches
Mail list logo
