Hi Christian, I saw both, the close and your question. I'd assume that Steve is updating those in a semi-automated fashion, there is no way he could read all those bugs.
Per bug status this one is marked fixed and only had a bug task open to backport to Precise. In fact the upstream commit that fixes this: commit 9380ba70d67db6b69f817d8e318de5ba1e990b12 Author: Simon Kelley <[email protected]> Date: Mon Apr 16 14:41:56 2012 +0100 Set SO_BINDTODEVICE on DHCP sockets when doing DHCP on one interface only. Fixes OpenSTack use-case. Has landed in 2.61. And all Ubuntu release are >2.61 nowadays dnsmasq | 2.68-1 | trusty | source dnsmasq | 2.68-1 | trusty/universe | all dnsmasq | 2.68-1ubuntu0.2 | trusty-security | source dnsmasq | 2.68-1ubuntu0.2 | trusty-security/universe | all dnsmasq | 2.68-1ubuntu0.2 | trusty-updates | source dnsmasq | 2.68-1ubuntu0.2 | trusty-updates/universe | all dnsmasq | 2.75-1 | xenial | source dnsmasq | 2.75-1 | xenial/universe | all dnsmasq | 2.75-1ubuntu0.16.04.10 | xenial-security | source dnsmasq | 2.75-1ubuntu0.16.04.10 | xenial-security/universe | all dnsmasq | 2.75-1ubuntu0.16.04.10 | xenial-updates | source dnsmasq | 2.75-1ubuntu0.16.04.10 | xenial-updates/universe | all dnsmasq | 2.79-1 | bionic | source dnsmasq | 2.79-1 | bionic/universe | all dnsmasq | 2.79-1ubuntu0.4 | bionic-security | source dnsmasq | 2.79-1ubuntu0.4 | bionic-security/universe | all dnsmasq | 2.79-1ubuntu0.4 | bionic-updates | source dnsmasq | 2.79-1ubuntu0.4 | bionic-updates/universe | all dnsmasq | 2.79-1ubuntu0.5 | bionic-proposed | source dnsmasq | 2.79-1ubuntu0.5 | bionic-proposed/universe | all dnsmasq | 2.80-1.1ubuntu1 | focal | source dnsmasq | 2.80-1.1ubuntu1 | focal/universe | all dnsmasq | 2.80-1.1ubuntu1.4 | focal-security | source dnsmasq | 2.80-1.1ubuntu1.4 | focal-security/universe | all dnsmasq | 2.80-1.1ubuntu1.4 | focal-updates | source dnsmasq | 2.80-1.1ubuntu1.4 | focal-updates/universe | all dnsmasq | 2.84-1ubuntu2 | hirsute | source dnsmasq | 2.84-1ubuntu2 | hirsute/universe | all dnsmasq | 2.84-1ubuntu2.1 | hirsute-security | source dnsmasq | 2.84-1ubuntu2.1 | hirsute-security/universe | all dnsmasq | 2.84-1ubuntu2.1 | hirsute-updates | source dnsmasq | 2.84-1ubuntu2.1 | hirsute-updates/universe | all dnsmasq | 2.85-1ubuntu2 | impish | source dnsmasq | 2.85-1ubuntu2 | impish/universe | all Therefore, yes the assumption would be that it is fixed in all remaining active releases. I've not done a practical check with a full testbed setup, but code-wise it should indeed be good now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006898 Title: [SRU] dnsmasq fails at leasing issues when using vlan mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1006898/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
