[Freedombox-discuss] UPDATE: After latest reboot dnsmasq no longer starts on any interface.
Sunil Mohan Adapa
sunil at medhas.org
Fri Oct 15 23:54:53 BST 2021
On 10/15/21 11:57 AM, A. F. Cano wrote:
> 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.
A recent bug report was filed because backup action starts bind9 daemon
even when it is not explicitly enabled[1]. Could you please check if
bind is running on your machine. Competing for the 53 port would explain
some of your symptoms. You can ensure that bind9 daemon does not start
by running:
systemctl mask named.service
Please confirm a fix with a few reboots (to ensure that dnsmasq is
running as expected). Thanks for the detailed reporting and your
patience with the issue.
--
Sunil
More information about the Freedombox-discuss
mailing list