extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-22 07:33:43 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update ipsets document

Browse Source 
- Clarify use of ipsets in stoppedrules.

Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2020-03-21 14:37:59 -07:00
parent e855d03332
commit 82d2863b29
No known key found for this signature in database
GPG Key ID: 96E6B3F2423A4D10
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/ipsets.xml
View File

@ -30,6 +30,8 @@
<year>2019</year>
<year>2020</year>
<holder>Thomas M. Eastep</holder>
</copyright>
@ -160,11 +162,11 @@ ACCEPT net:+sshok $FW tcp 22</programlisting></para>
</listitem>
<listitem>
<para>You cannot use an ipset in <ulink
<para>You can use an ipset in <ulink
url="manpages/shorewall-stoppedulres.html">shorewall-stoppedrules</ulink>
(5) (<ulink
url="manpages/shorewall-routestopped.html">shorewall-routestopped</ulink>
(5)).</para>
(5), but SAVE_IPSET={Yes|ipv4} will not save such a set during 'stop'
processing. Use Shorewall-init to save/restore your ipsets in this
case (see below).</para>
</listitem>
<listitem>