[Dnsmasq-discuss] domain-search option "." (Re: Announce: dnsmasq-2.55)
clemens fischer
ino-news at spotteswoode.dnsalias.org
Fri Jun 11 16:25:17 BST 2010
Simon Kelley wrote:
> clemens fischer wrote:
>
>> I'm running 2.55 here. I had always set the empty domain in option 119:
>>
>> dhcp-option = tag:wlan, option:domain-search, .
>>
>> The log contains:
>>
>> sent size: 4 option:119:domain-search ff:ff:ff:ff
>>
>> and I think this has always been like this. Is this correct or is my
>> configuration wrong? Tcpdump logs it thusly:
>>
>> T119 Option 119, length 4: 4294967295
>>
>> Everything else works fine, but obviously I'm not good at triggering
>> bugs.
>>
>
> Well, this is real one. The heuristics that determine the data-type of
> the option data get confused by "." and decide that it's an IP address.
> (I was testing the change with a list of search domains, which was
> enough to make things work.)
>
> http://www.thekelleys.org.uk/dnsmasq/test-releases/dnsmasq-2.56test2.tar.gz
>
> Does a better job by a) making a better guess based on the text of the
> option value and b) Using information about the expected data type for
> known options.
Thanks. What's the cheapest way to test the DHCP part? I have only one
wlan device operating as an ad-hoc node providing DHCP and DNS to
clients. Obviously I cannot connect invoking DHCP. When I last tried
dhcpcd on the same host and interface, it wouldn't let me issue fake
dhcp requests routing them over the loopback AFAIR.
clemens
More information about the Dnsmasq-discuss
mailing list