mirror of
https://gitlab.com/shorewall/code.git
synced 2025-01-03 03:59:16 +01:00
Amplify the 4.6.4 SAVE_IPSETS changes in the ipset article
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
parent
3bae6e61cf
commit
80c024c4aa
@ -159,6 +159,17 @@ ACCEPT net:+sshok $FW tcp 22</programlisting></para>
|
||||
setting SAVE_IPSETS to a comma-separated list of ipset names. You can also
|
||||
restrict the group of sets saved to ipv4 sets by setting
|
||||
SAVE_IPSETS=ipv4.</para>
|
||||
|
||||
<para>With Shorewall 4.6.4, the SAVE_IPSETS option may specify a list of
|
||||
ipsets to be saved. When such a list is specified, only those ipsets
|
||||
together with the ipsets supporting dynamic zones are saved. Shorewall6
|
||||
support for the SAVE_IPSETS option was also added in 4.6.4. When
|
||||
SAVE_IPSETS=Yes in <ulink
|
||||
url="manpages6/shorewall6.conf.html">shorewall6.conf(5)</ulink>, only ipv6
|
||||
ipsets are saved. For Shorewall, if SAVE_IPSETS=ipv4 in <ulink
|
||||
url="manpages/shorewall.conf.html">shorewall.conf(5)</ulink>, then only
|
||||
ipv4 ipsets are saved. Both features require ipset version 5 or
|
||||
later.</para>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
|
Loading…
Reference in New Issue
Block a user