[Freedombox-discuss] HELP! BIND/dnsmasq not working again.
A. F. Cano
afc54 at comcast.net
Sun Aug 1 22:54:07 BST 2021
On Sat, Jul 31, 2021 at 01:50:33PM -0400, A. F. Cano wrote:
> Ealier, something got fixed:
> On Fri, May 21, 2021 at 04:08:58PM -0400, A. F. Cano wrote:
> > I'm not sure what happened, but BIND is now working. ...
>
> But now freedombox got upgraded and rebooted and dnsmasq is no longer
> running like it used to:
> > > ...
> > > FreedomBox runs on an apu1d4, with 2 local interfaces, statically assigned
> > > (192.168.224.x and 192.168.200.x).
> > >
> > > ...
> > > bind 2572083 0.1 1.3 402876 53876 ? Ssl 13:44 0:05 /usr/sbin/named -f -u bind
> >
> > Now I get more
> >
> > $ ps aux | grep dhcp
> > nobody 868 0.0 0.0 13784 3556 ? S May12 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.224.27 --dhcp-range=192.168.224.36,192.168.224.254,60m --dhcp-lease-max=50 --dhcp-leasefile=/var/lib/NetworkManager/dnsmasq-enp2s0.leases --pid-file=/run/nm-dnsmasq-enp2s0.pid --conf-dir=/etc/NetworkManager/dnsmasq-shared.d
> > nobody 934 0.0 0.1 13784 4100 ? S May12 0:01 /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
> >
>
> And connected computers now say that "IP configuration was unavailable".
>
> What happened? How do I get dnsmasq to start as it used to do above?
>
> Augustine
Tried to run one of the above commands:
$ sudo /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.224.27 --dhcp-range=192.168.224.36,192.168.224.254,60m --dhcp-lease-max=50 --dhcp-leasefile=/var/lib/NetworkManager/dnsmasq-enp2s0.leases --pid-file=/run/nm-dnsmasq-enp2s0.pid --conf-dir=/etc/NetworkManager/dnsmasq-shared.d
and after entering the password I get this:
dnsmasq: failed to create listening socket for 192.168.224.27: Address already in use
so this has to get started as part of the network setup, or be started
by network manager. Why is it not doing it any more? Did some config
get obliterated? What changed? Any hints on what to check?
Thanks.
Augustine
More information about the Freedombox-discuss
mailing list