gmc2000

Btw, there is an option 'Stop low-level messages on console' under 'System' in armbian-config. I don't know what that does exactly, but worth a try?

The linux kernel has a command line option that sets the device to use as console. I believe it is possible to change the kernel command line by editing /boot/extlinux/extlinux.conf. Mine has 'console=ttyS02,1500000' in it, which is a serial console. Removing that should at least stop the kernel from printing messages to that serial port. There probably is a better way to configure this (I don't even know if editing extlinux.conf will do the trick). I see armbian-config documentation mentions a 'bootenv' option under 'system', but I don't see that when I run armbian-config on my board. Apart from the kernel, there is likely also a login session configured to run on the serial port. You need to disable that separately: When I `systemctl | grep getty` I can see there's a service running with the name 'serial-getty@ttyS2.service', disabling that should stop the serial logon console. systemctl disable serial-getty@ttyS2.service

To answer my own post: I had tailscale installed, which flushes the rules after they've been restored. Case closed.

Hi all, I'm quite puzzled by this. I installed iptables-persistent to be able to restore the iptables rules at start-up. Saved the rules to /etc/iptables/rules.v4 / /etc/iptables/rules.v6, then rebooted. But after boot, the iptables are empty. Looking at the status of service netfilter-persistent, it looks like it has ran the scripts to restore the rules: root@gateway:/etc# systemctl status netfilter-persistent.service ● netfilter-persistent.service - netfilter persistent configuration Loaded: loaded (/lib/systemd/system/netfilter-persistent.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/system/netfilter-persistent.service.d └─iptables.conf Active: active (exited) since Fri 2024-02-09 10:36:23 CET; 29min ago Docs: man:netfilter-persistent(8) Process: 334 ExecStart=/usr/sbin/netfilter-persistent start (code=exited, status=0/SUCCESS) Main PID: 334 (code=exited, status=0/SUCCESS) CPU: 130ms Feb 09 10:36:30 gateway.ow.sono netfilter-persistent[340]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables start Feb 09 10:36:30 gateway.ow.sono netfilter-persistent[340]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/25-ip6tables start Notice: journal has been rotated since unit was started, output may be incomplete. root@gateway:/etc# And when I manually run the scripts under /usr/share/netfilter-persistent/plugins.d, the rules are restored properly. It seems something is flushing the rules again after they have been restored, but I have no clue what that could be. Is this NetworkManager perhaps? Something else? Is iptables-persistent not the way to go on armbian to restore iptables rules on start-up? This is on Armbian 23.8.1 Bookworm with Linux 6.1.63-current-media (debian version 12.2).