Currently we launch dnsmasq with a command line looking like: dnsmasq --keep-in-foreground --bind-interfaces --pid-file --conf-file --except-interface lo --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254
This causes DNSMASQ to listen on any network interface configured with an IP address of '192.168.122.1', except for loopback. I know it would be kind of unusual, but it is possible two interface might be both configured with the same address. I think it may be safer if we explicitly tell it to use virbr0 instead eg --interface virbr0 --except-interface lo Yes, the --except-interface lo is still needed due to wierd ass dnsmasq rules which make it always use loopback unless you tell it not to. I'm also not clear why we use --conf-file - we're not actually telling it about any config file so this seems redundant ? Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list