[Freedombox-discuss] UPDATE: part of problem automagically got fixed. Re BIND not working,
A. F. Cano
afc54 at comcast.net
Fri May 21 21:08:58 BST 2021
I'm not sure what happened, but BIND is now working. There are still a
couple of issues: see below.
On Sun, May 09, 2021 at 03:41:45PM -0400, A. F. Cano wrote:
>
> ...
> 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
Which makes sense, and in combination with the /etc/hosts file I added to
the FreedomBox with entries like this:
192.168.224.10 <computer-name>.local <computer-name>
now this computer on the 224 sub-net gets allocated that address.
Great! That's what I wanted all along.
Still I get this: (on the above named computer)
$ sudo aptitude
sudo: unable to resolve host <computer-name>: Name or service not known
[sudo] password for <user>:
Why the "unable to resolve" message?
Also
$ ping <computer-name>
ping <computer-name>: Name or service now known
These old problems still persist.
>
> ...
>
> ping by internal IP works, even from one subnet to the other.
>
> ssh to the FreedomBox works (by IP number).
>
> ssh to a machine on the other subnet (by IP number) doesn't work
> (no route to host). Does this mean that the firewall needs to be opened
> between the 2 internal networks?
>
> ping by machine name doesn't work
> (ping: <internal hostname> Name or service not known)
>
> ssh by machine name doesn't work
> (ssh could not resolve hostname <internal hostname>: Name or service not known)
>
> ...
Do I need to add some manual configuration?
Any hints gratefully appreciated.
Augustine
More information about the Freedombox-discuss
mailing list