[Freedombox-discuss] UPDATE: After latest reboot dnsmasq no longer starts on any interface.

[A. F. Cano]

On Sun, Oct 10, 2021 at 02:12:38PM -0400, A. F. Cano wrote:
> On Fri, Oct 08, 2021 at 10:39:04PM -0400, A. F. Cano wrote:
> > ...
> > And now, after some updates last night, but not a reboot, dnsmasq is
> > again running but on only one interface.
> > 
> > $ ps aux | grep dns
> > nobody   1039716  0.0  0.1  13952  4204 ?        S    06:25   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=192.168.200.27 --dhcp-range=192.168.200.36,192.168.200.254,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
> > 
> > It's not running on the second internal interface.
> > 
> > This is what "about" says:
> > 
> > You are running Debian GNU/Linux bookworm/sid and FreedomBox version
> > 21.10. FreedomBox is up to date.
> 
> And now, after the latest reboot, dnsmasq doesn't start at all, in
> neither of the 2 internal interfaces.

The unpredictable behavior continues.  After the latest update to 21.11,
without a reboot, dnsmasq was running on the 2 internal interfaces, but
the "nothing goes through the firewall" issue is still not resolved.  To
see if this could possibly need a reboot, I did so.  It didn't fix it,
and furthermore, after the reboot dnsmasq doesn't start on either
internal interface.

Augustine