[Dnsmasq-discuss] Question about the error message
richardvoigt at gmail.com
richardvoigt at gmail.com
Fri Aug 8 23:55:40 BST 2008
On Wed, Aug 6, 2008 at 5:56 AM, Saori Fukuta
<fukuta.saori at jp.fujitsu.com> wrote:
> On Wed, 6 Aug 2008 04:53:47 +0000 "richardvoigt at gmail.com" wrote:
>> On Mon, Aug 4, 2008 at 11:26 AM, Saori Fukuta
>> <fukuta.saori at jp.fujitsu.com>wrote:
>>
>> > Hello,
>> >
>> > I got the following message at /var/log/messages,
>> > dnsmasq[13884]: no address range available for DHCP request via eth3
>> > when I have the following steps with dnsmasq-2.39-2.el5 (on RHEL-5.2):
>> > 1. start the dnsmasq, which is started by libvirt, with the
>> > following option.
>> > # /usr/sbin/dnsmasq --keep-in-foreground --strict-order
>> > --bind-interfaces --pid-file --conf-file --listen-address 192.168.122.1--except-interface lo --dhcp-leasefile=/var/lib/libvirt/dhcp-default.leases
>> > --dhcp-range 192.168.122.2,192.168.122.254
>> > 2. change the network address of eth3 to '0.0.0.0'.
>> > # ifconfig eth3 0 up
>> > 3. dnsmasq receives the DHCPINFORM message from DHCP servers of
>> > Windwos 2003 server.
>> > # tethereal -i eth3
>> > 5.521471 10.123.234.11 -> 255.255.255.255 DHCP DHCP Inform -
>> > Transaction ID 0xbe180000
>> >
>> > Do you know why the message appeared ? Please tell me the meaning of
>> > this message.
>>
>> If you are serving DHCP addresses on that subnet from a Windows 2003 server,
>> you should not enable dnsmasq's dhcp listener on that interface. Right now,
>> you're asking for DHCP operation of every interface except 'lo'.
>
> Thank you for your replying ! I understood that I should not enable
> that option with Windows 2003 server, but why should not dnsmasq's
> dhcp listen from Windows 2003 server ?
> Is there any difference between Linux server and Windows server ?
Are you trying to get an address for eth3, or give out addresses to
other computers in the subnet?
In the first case, you should use dhclient or dhcpc, as dnsmasq does
not request an address from other computers.
In the second case, you should use either dnsmasq or Windows to give
out addresses, but not both. If dnsmasq is not meant to give out
addresses, do not enable dnsmasq's dhcp server on that interface.
>
> In such a case, how can I specify the dnsmasq's option ?
> For example, should I specify "--interface" option with the interface
> which is not served DHCP addresses from a Windows 2003 server ?
You should use the --no-dhcp-interface option, as in --no-dhcp-interface=eth3
>
> thank you
>
> Saori.
>
>
>
>
More information about the Dnsmasq-discuss
mailing list