Firewall/Network issues with Armbian based install

Support
1

I am trying get FreedomBox working on a Armbian system, but it doesn’t work.
I don’t know for sure why, but I think it is because the firewall isn’t being setup properly and it is blocking web access from any device on the local network.

I think that there is slight differences in the way networking functions on Armbian so the Debian install doesn’t work properly after successfully downloading everything.

There is a lot of devices that armbian can be installed on, so it would be nice to figure what needs to be done on an armbian box to get it working properly.

2

We want to support installation of FreedomBox on Armbian.

FreedomBox uses firewalld as a firewall. This in turn uses nftables. I see no reason why it should not work on Ambian. Please post the output of systemctl status firewalld.service and journalctl -u firewalld.service.

If networking is configured in /etc/network/interfaces (likely on Ambian) then FreedomBox (through NetworkManager) does not interfere with that configuration. So, it should play well with Armbian like it does with Debian.

Please post more debugging information so that we can isolate and fix the issue.

3

I came across this as I was looking for documentation on how to manually install other apps on Armbian and it is all I needed to do to get Freedombox working on a Armbian device.

Armbian 25 replace Netplan with NetworkManager

sudo apt install network-manager -y

sudo nano /etc/NetworkManager/NetworkManager.conf
[keyfile]
unmanaged-devices=none

sudo systemctl restart NetworkManager
sudo systemctl enable NetworkManager
sudo systemctl status NetworkManager

sudo systemctl enable --now NetworkManager-wait-online.service
sudo systemctl restart NetworkManager-wait-online.service
sudo systemctl status NetworkManager-wait-online

sudo mv /etc/systemd/system/systemd-networkd-wait-online.service /etc/systemd/system/systemd-networkd-wait-online.service.bak
sudo ln -s /lib/systemd/system/NetworkManager-wait-online.service /etc/systemd/system/systemd-networkd-wait-online.service
sudo systemctl restart systemd-networkd-wait-online.service
sudo systemctl status systemd-networkd-wait-online.service

sudo systemctl disable --now netplan-ovs-cleanup.service
sudo systemctl disable --now netplan-wpa-wlan0.service
sudo systemctl disable --now netplan-ovs-cleanup.service

sudo systemctl stop netplan-ovs-cleanup.service
sudo systemctl stop netplan-wpa-wlan0.service
sudo systemctl stop netplan-ovs-cleanup.service

sudo systemctl daemon-reload
sudo mv /etc/netplan /etc/netplan.bak

sudo apt remove --purge netplan.io -y

sudo nmcli device set wlan0 managed yes
sudo nmcli device set end0 managed yes
sudo nmcli device set eth0 managed yes

sudo reboot

sudo systemctl list-unit-files | grep -E ‘NetworkManager|netplan’

1 Like
4

Thanks for the detailed steps. Perhaps purging the netplan.io package and rebooting the machine might also work since NetworkManager’s default behavior is to manage all devices that are not part of ifupdown configuration. Or could be missing something.