Every Reboot Disables 'ufw'

Hello Friends:

Here is an old thread from December 21. A solution was reached there, and it was working for these months. But the problem has returned. That old thread is:

Now again I am having a similar problem, but the solution from the thread does not apply. I have EOS installed on three computers that I maintain – one, a desktop where I work, two, a laptop that I take with me to my college, and three, a desktop that my daughter uses. After the grub-debacle I had to reinstall EOS on all three of them. Maybe that is from where the problem returned.

In all these three machines, I have installed ‘ufw’ and activated it. I have followed both the EOS and the arch-linux ufw-howto minutely in doing this. Still let me reiterate the steps here.

  1. Install ‘ufw’
  2. sudo systemctl disable iptables
  3. sudo systemctl enable and sudo systemctl start --now ufw.
  4. Create the rules under sudo – very simple ones, default deny incoming, default allow outgoing, allow from, allow Transmission and limit ssh after enabling ssh in all these three machines with IPs 192.168.0.x
    5.sudo Enable ufw, and at last
  5. sudo ufw status

Every time they are working fine. But it is getting disabled in every reboot. I have to issue ‘sudo enable ufw’ and then it works. My desktop reboots only with a kernel update, but my laptop and my daughter’s machine reboot a lot. What is the error on my part?

Thanking in advance


Before you “fix” it, what does systemctl status ufw show?

Let me paste the output:

sudo ufw status
[sudo] password for dd:
Status: inactive

And the output for systemctl status:

sudo systemctl status ufw
● ufw.service - CLI Netfilter Manager
Loaded: loaded (/usr/lib/systemd/system/ufw.service; enabled; preset: disa>
Active: active (exited) since Fri 2022-10-14 19:11:28 IST; 58s ago
Process: 286 ExecStart=/usr/lib/ufw/ufw-init start (code=exited, status=0/S>
Main PID: 286 (code=exited, status=0/SUCCESS)
CPU: 57ms

Hmm…is something disabling perhaps? Do you have any other firewalls installed? Has firewalld been removed?

Dear Dalto

No, firewalld is not removed. That output is:

sudo systemctl status firewalld
[sudo] password for dd:
● firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; preset>
Active: active (running) since Fri 2022-10-14 19:11:30 IST; 53min ago
Docs: man:firewalld(1)
Main PID: 511 (firewalld)
Tasks: 2 (limit: 19110)
Memory: 50.8M
CPU: 242ms
CGroup: /system.slice/firewalld.service
└─511 /usr/bin/python /usr/bin/firewalld --nofork --nopid

Oct 14 19:11:29 ru systemd[1]: Starting firewalld - dynamic firewall daemon…
Oct 14 19:11:30 ru systemd[1]: Started firewalld - dynamic firewall daemon.
lines 1-13/13 (END)

Shall I disable that too?

sudo systemctl disable firewalld?

I would just uninstall it. You don’t need two firewalls installed.

sudo pacman -R firewalld
1 Like

Did that. And also:

sudo systemctl disable firewalld
Removed “/etc/systemd/system/multi-user.target.wants/firewalld.service”.
Removed “/etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service”.

Does this message signal any problem? See, I do not understand anything of these technical details. Sorry to disturb you. And thank for the help.


Should I do the same thing on all the three machines?

Yes, firewalld and ufw are both firewalls. If you prefer ufw then remove firewalld.

Thank you dalto. Problem solved on all the three machines.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.