Re: [Dnsmasq-discuss] dnsmasq on FreeBSD not listening on specified interfaces
Thanks, that did the job. Apologies for not reading the man page more carefully. On 21 September 2017 at 13:55, Chris Novakovic wrote: > On 21/09/2017 12:19, Jason Mann wrote: > > I have tried to configure dnsmasq to listen only on 'lan' and 'lan.129' > > (plus the implicit 'lo0') with the following directives: > > > > interface=lan > > interface=lan.129 > > > > However, after a restart, dnsmasq is still listening on all interfaces > (*) > > From the man page: > > > -z, --bind-interfaces > > On systems which support it, dnsmasq binds the wildcard address, > even when it is listening on only some interfaces. It then discards > requests that it shouldn't reply to. This has the advantage of working even > when interfaces come and go and change address. This option forces dnsmasq > to really bind only the interfaces it is listening on. About the only time > when this is useful is when running another nameserver (or another instance > of dnsmasq) on the same machine. Setting this option also enables multiple > instances of dnsmasq which provide DHCP service to run in the same machine. > > Try adding "bind-interfaces" to your configuration. (The man page also > describes a "bind-dynamic" option, but this won't work under FreeBSD.) > ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] dnsmasq on FreeBSD not listening on specified interfaces
Hi list. I'm running dnsmasq 2.77 on FreeBSD-11.1-RELEASE. dnsmasq was installed from FreeBSD's package repository. It's running on a gateway host with two Intel interfaces, originally named igb0 and igb1 by the kernel. I've made use of FreeBSD's interface renaming feature to rename these 'lan' and 'wan'. I've also created a lan.129 vlan interface. # ifconfig -l lan wan lo0 pflog0 lan.129 I have tried to configure dnsmasq to listen only on 'lan' and 'lan.129' (plus the implicit 'lo0') with the following directives: interface=lan interface=lan.129 However, after a restart, dnsmasq is still listening on all interfaces (*) # sockstat -l | grep "USER\|dnsmasq" USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS nobody dnsmasq43007 4 udp4 *:67 *:* nobody dnsmasq43007 8 udp4 *:53 *:* nobody dnsmasq43007 9 tcp4 *:53 *:* nobody dnsmasq43007 10 udp6 *:53 *:* nobody dnsmasq43007 11 tcp6 *:53 *:* I also tried 'except-interface=wan', with the same result. I can try setting the interfaces back to their original names, but that will be service disrupting for my users. Before I try that can anyone suggest what might be wrong here? Kind regards, Jason ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] Leases file fields
Hello list, I'm about to write a simple CGI script to parse my dnsmasq.leases file and present the information in a web page, with MAC address vendors looked up and included. I'd just like to know the exact definition of the last field on each line. It is either a single asterisk for hosts whose MAC addresses are known (in /etc/ethers) or it's a repeat of the MAC address of the device with the ethertype included, for example: 1493791865 9c:5c:8e:xx:xx:xx 192.168.128.125 jm-desktop * 1493751088 48:5a:b6:xx:xx:xx 192.168.128.145 jm-chromebook 01:48:5a:b6:xx:xx:xx Is there a more precise description? I couldn't find any details in the man page. Thanks. Jason ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
