Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#77709 - [ufw] uwf is not enabled after startup
Attached to Project:
Community Packages
Opened by arno (arenevier) - Friday, 03 March 2023, 06:24 GMT
Last edited by Toolybird (Toolybird) - Sunday, 05 March 2023, 07:06 GMT
Opened by arno (arenevier) - Friday, 03 March 2023, 06:24 GMT
Last edited by Toolybird (Toolybird) - Sunday, 05 March 2023, 07:06 GMT
|
DetailsSteps to reproduce:
I have followed the wiki, https://wiki.archlinux.org/title/Uncomplicated_Firewall - enabled ufw.service - call ufw enable But after a restart, "uwf enable" indicates that uwf is inactive. I put some quick log, and I can see that /usr/lib/ufw/ufw-init start is called by systemd during the startup process. But iptable rules are not created. I suspect this is problem similar to the one described here https://devtidbits.com/2019/07/31/ufw-service-not-loading-after-a-reboot/ I only discovered the problem because I decided to test ufw status after a reboot. I assume that many people are running into the same issue unknowingly, and think they have a working firewall when they actually don't. |
This task depends upon
Comment by Toolybird (Toolybird) -
Sunday, 05 March 2023, 07:06 GMT
Works fine here in a fresh VM. There are no other reports about this. You'll need to debug where it's going wrong on your system. For support, please use the proper support channels (forum/IRC/etc) to see if anyone can help spot the issue.