On Fri, Mar 09, 2007 at 02:29:08PM +0000, Mark McLoughlin wrote:
On Fri, 2007-03-09 at 03:17 +0000, Daniel P. Berrange wrote:
> 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
Yep, that sounds good to me. I don't know why I didn't do it that way.
Ok, I'll do a patch for that.
> I'm also not clear why we use --conf-file - we're not
actually telling it
> about any config file so this seems redundant ?
I'm basically telling it "don't use /etc/dnsmasq.conf" AFAIR. All
configuration to it should be on the command line.
Ok that makes alot of sense - I was puzzled because the manpage seems to
suggest its compulsory to supply a filename :-)
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 -=|