Clarify UFW documentation

[ubombi]

SUMMARY

Clarification of potentially misleading documentation.

ISSUE TYPE

• Docs Pull Request

COMPONENT NAME

community.general.ufw

ADDITIONAL INFORMATION

It may be a weird use-case, but:

1. Enable firewall
2. Edit /etc/ufw/user.rules
3. Run playbook with state: enabled
4. Rules aren't reloaded.
5. Run playbook with state: reloaded
6. Rules are reloaded

ufw -h explains commands like:

enable enables the firewall
disable disables the firewall
reload reload firewall
reset reset firewall

state: enabled or ufw -f enable does not reload firewall. New rules are visible in ufw status, but the iptables aren't updated.

And the part about "enabled"/"disabled" working on boot is incorrect either because the change is immediate. Like systemctl enable --now

[ansibullbot]

cc @ahtik @ovcharenko @pyykkis
click here for bot help

[felixfontein]

Thanks for your contribution!

The current descriptions match what ufw's man page is saying about the commands, check for example https://manpages.org/ufw/8 (or in raw form, https://git.launchpad.net/ufw/tree/doc/ufw.8):

enable
reloads firewall and enables firewall on boot.

disable
unloads firewall and disables firewall on boot

reset
Disables and resets firewall to installation defaults. Can also give the --force option to perform the reset without confirmation.

If you think that ufw doesn't do what it documents, please file a bug against ufw so they fix their documentation. Once they do that, we can also update our descriptions.

[russoz]

hi @ubombi are you still going to pursue some change here? If not, could you please close the PR, or let us know and we'll be happy to do it.

[ubombi]

Sure.