Thanks for the response and glad you got it worked out. It reminds me
that I would like to document using fail2ban with ufw more.
** Changed in: ufw (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sorted out the issue. I've got systemd to also wait for ufw to load when
starting fail2ban.
Fail2ban issues a many iptables commands in rapid succession and then
it's database of banned IPs is large it takes a considerable amount of
time for the firewall to be initialised. In the meanwhile anythi
Right after reboot I tried to get the status.
Result is . . . .
root@loki:~# s ufw status
ERROR: problem running iptables: Another app is currently holding the xtables
lock. Perhaps you want to use the -w option?
. . . . while fail2ban is setting up its rules.
Anyway... After a reeboot, whate
By networking stops means that I can not establish a connection with the
Lemaker BananaPi Pro on any port so I can't get a SSHed shell, can't
access the VPN server, etc... It behaves like someone has plugged the
network cable.
Putting "ufw.service" was a guess, but I've not rebooted the OS yet wi
Thanks for the bug report. A few things:
1. I'm not sure what 'networking stops' means precisely in the context
of this bug report. Does 'ufw disable' restore the network? Is the
network torn down? Something else (you are using a lot of limit rules
instead of allow rules, I wonder if you are hitti
> How to I ensure that ufw is fully up and initialised BEFORE the
fail2ban service starts?
This line from your existing fail2ban.service should be sufficient:
After=network.target iptables.service firewalld.service
ip6tables.service ipset.service nftables.service ufw.service
See https://www.free
> 4. you didn't mention which distro you are using
This would be good to know since some distros are using iptables 1.8.x
which has two different backends that are in play. Which distro are you
using and what is the output of `iptables --version`
--
You received this bug notification because you
root@loki:/home/myron# journalctl -u ufw.service
-- Logs begin at Wed 2021-12-29 15:30:45 GMT, end at Thu 2021-12-30 13:10:27
GMT. --
-- No entries --
-
Current status of service. ufw was enabled manually so is actually
active. It won't be once I reboot.
root@loki:/home/myron# systemctl sta
** Description changed:
- I was advised to start a bug report:
- https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/comments/38
+ I was advised to start a bug report (Comment 38):
+ https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856
I "ufw enable" then several seconds later ne
** Summary changed:
- ufw does not activate at boot time
+ ufw remains inactive at boot time
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956029
Title:
ufw remains inactive at boot time
To manag
10 matches
Mail list logo
