[Dnsmasq-discuss] Interface-only binding not properly

[richardvoigt at gmail.com]

On Thu, Jun 10, 2010 at 3:50 PM, clemens fischer
<ino-news at spotteswoode.dnsalias.org> wrote:
> On Fri-2010/06/04-20:41 Richard Voigt wrote:
>
>> I assume you're referring to the fact that dnsmasq bound to the
>> wildcard address for dhcp service?  This is necessary to receive
>> incoming dhcp broadcasts such as the initial DHCPREQUEST packet, when
>> the client doesn't yet know the address of the dhcp server.
>
> He shows that even domain ports are listening on the wildcard address.

No they aren't.

Both his and yours bind wildcard addresses for dhcp (port 67) and
specific addresses for dns (port 53).

>
> I'm running dnsmasq-2.55 with, among others, these switches:
>
>    --interface=wlan --bind-interfaces
>
> and my config contains:
>
>    except-interface=nic1
>    except-interface=nic2
>    except-interface=lo
>    no-dhcp-interface=nic1
>    no-dhcp-interface=nic2
>    no-dhcp-interface=lo
>
> because I want to provide DHCP and a DNS forwarder only to clients on
> the wlan interface.  Here "lsof -i -nP" shows:
>
>    COMMAND    PID    USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
>    ...
>    dnsmasq   3201  nobody    5u  IPv4  10933      0t0  UDP *:67
>    dnsmasq   3201  nobody    6u  IPv6  10947      0t0  TCP [fe80::21f:1fff:fe52:9dbd]:53 (LISTEN)
>    dnsmasq   3201  nobody    7u  IPv6  10948      0t0  UDP [fe80::21f:1fff:fe52:9dbd]:53
>    dnsmasq   3201  nobody    8u  IPv4  10949      0t0  TCP 192.168.3.1:53 (LISTEN)
>    dnsmasq   3201  nobody    9u  IPv4  10950      0t0  UDP 192.168.3.1:53
>    ...
>
> ie, it does bind specific IPs.
>
>
> clemens
>
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>