[Freedombox-discuss] UPDATE: Dnsmasq starting again, after updates and reboot, but only on one interface.

A. F. Cano afc54 at comcast.net
Sun Aug 29 19:32:22 BST 2021

On Mon, Aug 09, 2021 at 08:19:29AM -0400, I wrote:
> Hi,
> I have no idea why this issue keeps coming back, gets fixed, works
> again, and now, after the latest reboot last night, dnsmasq is again not
> starting.  Can someone shed some light? 

After an update where network-manager, freedombox and other packages got upgraded,
dnsmasq now starts again, but only on one interface.  I have two internal interfaces.

$ ps aux | grep dns
nobody   1888964  0.0  0.1  13792  4268 ?        S    Aug24   0:00 /usr/sbin/dnsmasq --conf-file=/dev/null --no-hosts --keep-in-foreground --bind-interfaces --except-interface=lo --clear-on-reload --strict-order --listen-address= --dhcp-range=,,60m --dhcp-lease-max=50 --dhcp-leasefile=/var/lib/NetworkManager/dnsmasq-enp3s0.leases --pid-file=/run/nm-dnsmasq-enp3s0.pid --conf-dir=/etc/NetworkManager/dnsmasq-shared.d

There used to be another such entry for the 192.168.224.* sub-net.  Any
idea why this is occuring?  Thsnks.


More information about the Freedombox-discuss mailing list