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 fixed directly in Debian, and then Ubuntu will pick up the fix automatically. The only delta you see in Xenial is a security fix, so not a lot of "Ubuntu special" that could break it. Also the versions are pretty much up to date - 2.76 as in Yakkety is the latest upstream. I checked the changelog but there is no mentioning of the issue you are facing, yet if easily possible for you it might be worth checking the same on Yakkety or even Zesty. I almost assume that it might be an upstream issue with dnsmasq itself, but in that case as well Debian should be notified to be able to pick it up as well. You clearly have the best setup to reproduce if any more questions come in, therefore would you mind filing a bug with Debian and/or upstream and link it here please? ** Tags added: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651044 Title: ProxyDHCP replies on invalid range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1651044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
