On 17/02/2025 13:47, jean-christophe manciot wrote: >> In order to allow multiple dnsmasq instances (for instance in the >> libvirt case) dnsmasq sets REUSEPORT on DHCP sockets, and, if exactly >> one interface is specified in the configuration, it sets SO_BINDTODEVICE. > No, it does not work: if dnsmasq systemd service starts first, libvirtd > cannot start its own dnsmasq instance(s) and **no** VM can be assigned any IP > address. > >> 1) The behaviour you are asking for doesn't work. >> 2) This is not a regression: it has always been done this way. > It used to work in all previous ubuntu releases and yes, it is a regression: > it is the first time I cannot use dnsmasq **and** libvirtd. >
Whatever change caused the regresssion, it's not binding the DHCP socket to INADDR_ANY, since dnsmasq has always done that. So stop telling us that dnsmasq does that, and start giving useful information. What configuration is in use on the systemd-started dnsmasq? What configuration is available on the libvirt dnsmasq instance? What error messages are seen? Don't assume that the problem is a dnsmasq change. What configuartion differences are there between a working system and a broken one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2098119 Title: dnsmasq opens DHCP server ports on all interfaces instead of just on the interface(s) defined in interface= setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2098119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
