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

[A. F. Cano]

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.

Augustine