[Dnsmasq-discuss] Announce: dnsmasq-2.53 release candidate 1

[Kyle Kienapfel]

Since you're issues trouble I'll pipe up and mention something I'm
poking at as time permits.

I've been having trouble with dnsmasq and gpxe. gpxe 0.9.9 works with
dnsmasq 0.51 but not version 0.52
gpxe 1.0.0 works with 0.52 since it listens on port 4011 as well as
the regular dhcp port.

I flashed a few network cards with gpxe 0.9.9, so an upgrade would
take awhile. Right now as a kludge I can run dnsmasq 0.51 regularly
and dnsmasq 0.52 with --dhcp-alternate-port=2 as with
--dhcp-alternate-port=4011 it tried to open port 4011 twice and failed
the second time :)

Is there something i can set to make the newer dnsmasq builds work
with me olde gpxe roms?

On Mon, May 24, 2010 at 2:20 PM, Simon Kelley <simon at thekelleys.org.uk> wrote:
> clemens fischer wrote:
>> Simon Kelley wrote:
>>
>>> clemens fischer wrote:
>>>
>>>> I have this line in the config:
>>>>
>>>>   dhcp-generate-names=tag:wlan
>>>>
>>>> dnsmasq-2.53rc1 complains:
>>>>
>>>>   dnsmasq: extraneous parameter at line 720 of /etc/dnsmasq.conf
>>> Thanks for that: a one-line fix needed. I'll push out 2.53rc2 later today.
>>
>> While you're at it:
>>
>> I have this:
>>
>>     # -ino: 100524-2051 XXX doesn't work! use static host alloc!
>>     # option 12: hostname
>>     #dhcp-option = tag:XXX,12,xxx
>>     #dhcp-option = tag:wlan,51,30m
>>
>> I wanted to send some hostname and set the lease time depending on that
>> fabulous tag system, but both are obviously ignored.  I could not
>> discern is the original
>>
>>     dhcp-host=tag:XXX,xxx,192.168.3.5,30m
>>
>> did its thing, though.  The log doesn't mention sending that "xxx"
>> hostname.  Then again:  the host didn't request one and the manual
>> doesn't say I can use tags like this.
>
> The hostname and lease time are both data that dnsmasq uses locally,
> they are not just opaque data that's passed through to the client. I
> think there's code which explicitly blocks setting those options. It
> would be bad if you sent an option 51 that told the client that it had a
> lease for a day, but dnsmasq expired the lease after an hour and the
> host disappeared from the DNS.
>
>
>>
>> BTW:  this is confusing (re. "--dhcp-host" option):
>>
>>     Addresses allocated like this are not constrained to be in the range
>>     given by the --dhcp-range option, but they must be in the same
>>     subnet as some valid dhcp-range.  For subnets which don't need a
>>     pool of dynamically allocated addresses, use the "static" keyword in
>>     the dhcp-range declaration.
>>
>> Does this mean I don't have to put some host into the range it was
>> allocated from, but into any other range specified?  I just don't get
>> it.
>
>
> An example helps: if you have an network which is 192.168.1.0/24 and you
> specify
>
> dhcp-range=192.168.1.100,192.168.1.200
>
> then clients will get addresses in the range specified. Unless
> you have
>
> dhcp-host=00:11:22:33:44:55,192.168.1.20
>
> which is valid because 192.168.1.20 is within the 192.168.1.0/24 subnet,
> so a client with that mac-address will get 192.168.1.20.
>
> On the other hand
>
> dhcp-host=00:11:22:33:44:55,192.168.2.20
>
> would be ignored because the IP address is not within the subnet.
>
> HTH
>
> Simon.
>
>
>
>>
>>
>> clemens
>>
>>
>> _______________________________________________
>> Dnsmasq-discuss mailing list
>> Dnsmasq-discuss at lists.thekelleys.org.uk
>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>>
>
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>