From c7649f966c249a9296a7457b749d0f4d59bd6ed9 Mon Sep 17 00:00:00 2001 From: hygienic-books Date: Sat, 16 Jul 2022 02:24:46 +0200 Subject: [PATCH] docs(xml): Typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 15c6708..ef93330 100644 --- a/README.md +++ b/README.md @@ -291,7 +291,7 @@ A custom `[section]` has the following options. We're calling them locals most o ... multiport dports 143,993,110,995,25,465,587 recent: SET ... ACCEPT ... state NEW multiport dports 143,993,110,995,25,465,587 ... ``` - Where the first `DROP` target will drop packets that have exceeded their hit count; the second `recent: SET` simply marks all matching packets to be added into the hitcount bucket and the third on is the actual `ACCEPT` rule permitting access **_if_** a source's hitcount permits it. + Where the first `DROP` target will drop packets that have exceeded their hit count, the second `recent: SET` simply marks all matching packets to be added into the hitcount bucket and the third one is the actual `ACCEPT` rule permitting access **_if_** a source's hitcount permits it. * `do_ipv6`, __*optional*__, defaults to `false`: Decide if you want `firewalld` to generate `ip6tables` rules in addition to `iptables` rules. A default install of Docker Engine will have its IPv6 support disabled in `/etc/docker/daemon.json`. You may still want your machine to handle incoming IPv6 traffic. If your machine truly doesn't use IPv6 feel free to leave this at `false`. Otherwise `update-firewall-source.py` generates unused rules that clutter your rule set.