Seems like a mis-feature to me, but whatever.
so if you don't include -except-interface=lo then it will the loopback automatically. IP alias interfaces (eg "eth1:0") cannot be used with -inter‐įace or -except-interface options, use -listen-address listen-address options are given dnsmasq listens on all avail‐Īble interfaces except any given in -except-interface options. Dnsmasq automaticallyĪdds the loopback (local) interface to the list of interfaces to Listen only on the specified interface(s). Additional comment from Jeff Layton on 16:00:29 EST. The easiest way to have network manager run dnsmasq is adding 'dns=dnsmasq' to /etc/NetworkManager/nf and logout/login I verified that adding '-except-interface lo' to the new 0.10.2.2 dnsmasq command line generates similar lsof output to 0.10.2.1 dnsmasq command line (basically what Jeff reported above, but without the 127.0.0.1 and bits) Huh, I was hitting this too but didn't realize it was libvirt related. Additional comment from Cole Robinson on 15:41:00 EST. Note too that if I start the libvirt virtual network after starting my other dnsmasq server that it doesn't end up listening on localhost. Additional comment from Jeff Layton on 15:17:59 EST. Perhaps you still need the "-except-interface lo" in the command line as well? but I'll leave the diagnosis to others to determine. My suspicion would be this change in the changelog: That prevents my other dnsmasq server from starting and doesn't seem correct. The dnsmasq launched by libvirt used to just listen on 192.168.122.1, but now it listens on the loopback too. Nobody 12148 1 0 15:08 ? 00:00:00 /sbin/dnsmasq -strict-order -local=// -domain-needed -pid-file=/var/run/libvirt/network/default.pid -conf-file= -bind-dynamic -interface virbr0 -dhcp-range 192.168.122.2,192.168.122.254 -dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases -dhcp-lease-max=253 -dhcp-no-override -dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile -addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts That something is the dnsmasq that libvirt fires up to handle ~]# ps -ef | grep dnsmasq
Opendns updater v 2.2.1 update#
After the latest libvirt update however, I found that it failed to start because something was listening on the port. I have my VPN config into work set up to run a dnsmasq on the loopback for split DNS. +++ This bug was initially created as a clone of Bug #886663 +++
0 kommentar(er)
