[Dnsmasq-discuss] FreeBSD vs. "bind-interfaces" and "except-interface"
Simon Kelley
simon at thekelleys.org.uk
Thu Feb 17 10:31:22 GMT 2011
Matthias Andree wrote:
> Am 16.02.2011 17:41, schrieb Simon Kelley:
>
>>> in that case, dnsmasq binds to 192.168.0.4 according to lsof.
>>>
>>>
>>> Is this a known issue on FreeBSD? What means are there to resolve this
>>> so that users don't fall into this trap?
>>>
>> The behavior is the same on all platforms.
>>
>> Without bind-interfaces:
>>
>> Bind INADDR_ANY, implement --interface, --address, --except-interface by
>> examining incoming packets and discarding those we shouldn't answer.
>
> Apparently there is something that doesn't work here. Either dnsmasq
> doesn't see the request, or discards it when it shouldn't. I'm going to
> try and find out later. There's a couple of reasons this could fail,
> but the reason is _not_ that FreeBSD 8.2 couldn't bind INADDR_ANY with
> named bound to 127.0.0.1:53 TCPv4 and ::1/53 TCPv6.
>
I'd expect that sequence to result in EADDRINUSE on Linux.
Simon.
More information about the Dnsmasq-discuss
mailing list