@jdstran The fix of Debian doesn't help. I use fail2ban too. But if
fail2ban.service is disabled and masked then the issue still happens.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.ne
@jdstrand I've created a new bug report as you suggested:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1956029
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1726856
Title
@Stefan, I suggest you try the fix that is in Debian. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990834#27
@Myron, yours sounds like a different issue. I suggest you file a new
bug, downloading https://git.launchpad.net/ufw/tree/tests/check-
requirements and including the output of 'su
Same problem here. Also when I "ufw enable" then several seconds later
networking stops. I have get Ubuntu to gracefully power-down using the
power-button and then gracefully power-up.
ufw 0.36
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Running "/usr/bin/sleep 10 && /usr/sbin/ufw enable" via cron works for
me
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1726856
Title:
ufw does not start automatically at boo
Im using Ubuntu 20.04 by the way.
To make clear what I meant: I think the dependencies aren't defined
right such that some services are starting to early.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https:/
I have the same issue on an computer with NVME. Maybe the boot is too
fast? The fix and all workarounds (cron) haven't helped.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1726
This introduced an ordering cycle, and hence broke networking, see
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1950039
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/17268
This bug was fixed in the package ufw - 0.36.1-3
---
ufw (0.36.1-3) unstable; urgency=medium
* debian/ufw.service (LP: #1726856, Closes: 990834):
- use Before and Wants on network-pre.target. Per systemd documentation,
"network-pre.target is a target that may be used to or
I've looked at this issue again in reference to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990834 and while I
still cannot reproduce, I plan to change to the following (I won't ship
the commented out lines of course):
[Unit]
Description=Uncomplicated firewall
Documentation=man:ufw(8)
#Defau
@cajicas215 - your comment is not helpful. If you look at the other
comments in this bug, there has been nothing to fix in ufw. I suggest
looking at the comments in this bug and seeing if any of the issues
others have seen apply to you. If not, please report a new bug with
steps to reproduce.
--
@Fabian - your change both makes the firewall start after networking,
brings python into the boot process (which can slow down boot) and
changes the intent of 'systemctl stop ufw' from unloading the firewall
to disabling the firewall in the moment and forever in the future, which
is inappropriate (
This bug still exist since i was a kid. now in 2021 its still exist in
Ubuntu 20.04 (LTS) . Will reupdate the status 10 years from now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/
I also have this Bug on "Raspbian GNU/Linux 10 (buster)". I solved it
with the following changes:
-Before=network.target
+After=network.target
-ExecStart=/lib/ufw/ufw-init start quiet
+ExecStart=/usr/sbin/ufw --force enable
-ExecStop=/lib/ufw/ufw-init stop
+ExecStop=/usr/sbin/ufw --force disable
@Muhammad - can you run:
$ sudo /usr/share/ufw/check-requirements
and paste the results?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1726856
Title:
ufw does not start aut
This bug occurs in Ubuntu 20.04 too but I could bypass it by using the
suggested fix in comment #23
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1726856
Title:
ufw does not
I also had this problem still once in a while and had a look at it again. I
think in my case the problem is the package sshguard, which also adds firewall
rules on startup and in some cases might interfere with ufw startup.
I added /etc/systemd/system/sshguard.service.d/after_ufw.conf with conten
Hi,
I can confirm this bug still exists on Ubuntu 18.04 and in my case none
of the above solutions have been successful.
The following workaround has solved it for me:
Edit /etc/crontab and add the following line:
@reboot rootufw enable
It has worked every time on 5 reboots I have done to t
@Matt you have both ufw and firewalld installed and running. You should
disable/remove firewalld. Marking this as 'Invalid' for now, but please
feel free to report back if you still see a bug in ufw after addressing
firewalld.
** Changed in: ufw
Status: Incomplete => Invalid
** Changed in:
** Attachment added: "ufw.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222404/+files/ufw.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/b
** Attachment added: "dpkg.list"
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222403/+files/dpkg.list
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bug
** Attachment added: "ufw.raw"
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222405/+files/ufw.raw
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/17
I rebooted and confirmed that ufw still reports itself as inactive.
Attached are the requested files. Note: I only included the last 25000
lines from journal.full - otherwise I would have to upload 250Mb!
** Attachment added: "journal.full"
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/17
@Matt, there aren't any errors in your journalctl output that I can see.
Without removing the change to /lib/ufw/ufw-init yet, can you reboot
until you see the problem, and then before you correct the issue, can
you attach the output of all of the following:
1. journalctl --no-pager > /tmp/journa
I made the change to /lib/ufw/ufw-init as requested and confirmed that
after reboot I was still hitting the issue (Ubuntu 18.04.1 LTS):
$ sudo ufw status
Status: inactive
Attached is the requested journalctl output.
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+sou
For those experiencing this issue, can you adjust /lib/ufw/ufw-init to
use this:
#!/bin/sh -x
on its first line instead of:
#!/bin/sh
Then reboot and until you see the issue. When you do, please use
`journalctl --no-pager --unit=ufw` and attach the results.
Thanks!
** Changed in: ufw
S
I just tried:
After=network.target
After 5 reboot tests I got mixed results:
The first two reboots failed to start networking at all and ufw reported its
status as "inactive" immediately after boot.
The next two reboots networking started successfully, and ufw reported as
active.
The final reboo
Sorry after some more reboots the problem persists with:
After=network-pre.target
Wants=network-pre.target
So only working setup for me at the moment is:
After=network.target
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to uf
Also tested:
After=network-pre.target
Wants=network-pre.target
This works as well, so this seems to be the appropriate config ? Maybe
@marcosfrm has a typo in his recommendation ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
If I use in /lib/systemd/system/ufw.service:
-Before=network.target
+After=network.target
ufw starts without errors, so there seem to be dependencies in the
network.target, that are not allowing ufw-init-functions to complete
successfully.
--
You received this bug notification because you are a
I changed this:
-Before=network.target
+Before=network-pre.target
+Wants=network-pre.target
and get following:
Jul 23 09:40:53 us-proxy1 ufw-init[424]: ip6tables-restore: line 4 failed
Jul 23 09:40:53 us-proxy1 systemd[1]: ufw.service: Main process exited,
code=exited, status=1/FAILURE
Jul 23 09:
On latest Ubuntu 18.04 I have an inconsistent state of ufw on reboots
(sometimes even ssh doesn't work):
root@us-proxy1:~# uname -a
Linux us-proxy1 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
root@us-proxy1:~# dpkg -l |grep ufw
ii ufw
I just tried that:
$ diff -u ufw.service.orig ufw.service
--- ufw.service.orig2018-05-26 13:45:48.696356561 +0100
+++ ufw.service 2018-07-17 16:50:45.545596167 +0100
@@ -2,7 +2,8 @@
Description=Uncomplicated firewall
Documentation=man:ufw(8)
DefaultDependencies=no
-Before=network.target
+Be
You need
Before=network-pre.target
Wants=network-pre.target
(Wants is necessary because network-pre.target is a passive target)
(Before=network.target can be removed)
And then network management software needs to have After=network-
pre.target. systemd-networkd and NetworkManager are fine, but I
Unfortunately, after a few reboots using these settings it seems this is
not the answer. While it does seem to work intermittently, it also
sometimes fails. I've also had some issues with network not working at
all. I'm not 100% sure that this change is the culprit - but for now I
have reverted the
Wrt:
the network-pre.target has this purpose:
"It's primary purpose is for usage with firewall services that want to
establish a firewall before any network interface is up"
I'm not sure network-pre.target existed at the time ufw added a systemd
unit, but regardless, this sounds like exactly wha
This issue still seems to be a problem in 18.04.
If found a solution:
https://askubuntu.com/questions/1040539/how-do-i-get-ufw-to-start-on-boot/1040584
I edited /lib/systemd/system/ufw.service as follows:
$ diff -u ufw.service.orig ufw.service
--- ufw.service.orig2018-05-26 13:45:48.69635656
** Changed in: ufw (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1726856
Title:
ufw does not start automatically at boot
Status in
Hi Seth,
This is what I get:
matt@matt-laptop:~$ sudo ufw status
Status: inactive
matt@matt-laptop:~$ journalctl -u ufw.service
-- Logs begin at Tue 2017-10-24 22:48:54 BST, end at Wed 2017-10-25 00:03:54
BST. --
Oct 24 22:48:54 matt-laptop systemd[1]: Started Uncomplicated firewall.
matt@matt-l
Hi Matt, can you give the output of:
systemctl status ufw
and
journalctl -u ufw.service
Thanks
** Changed in: ufw (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
ht
40 matches
Mail list logo
