forked from extern/shorewall_code
Document the restoration of SAVE_IPSETS=Yes
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
parent
91b65125aa
commit
e3c75dcfcc
@ -4,6 +4,8 @@ Changes in Shorewall 4.4.6
|
||||
|
||||
2) Add a hack to work around a bug in Lenny + xtables-addons
|
||||
|
||||
3) Re-enable SAVE_IPSETS
|
||||
|
||||
Changes in Shorewall 4.4.5
|
||||
|
||||
1) Fix 15-port limit removal change.
|
||||
|
@ -235,7 +235,15 @@ None.
|
||||
|
||||
e) The 'routefilter' interface option can have values 0,1 or 2. If
|
||||
'routefilter' is specified without a value, the value 1 is
|
||||
assumed.
|
||||
assumed.
|
||||
|
||||
2) SAVE_IPSETS=Yes has been resurrected but in a different form. With
|
||||
this setting, the contents of your ipsets are saved during 'shorewall
|
||||
stop' and they are restored during 'shorewall start' and 'shorewall
|
||||
restore'.
|
||||
|
||||
When SAVE_IPSETS=Yes, you may not include ipsets in your
|
||||
/etc/shorewall/routestopped configuration.
|
||||
|
||||
----------------------------------------------------------------------------
|
||||
N E W F E A T U R E S I N 4 . 4 . 0
|
||||
|
Loading…
Reference in New Issue
Block a user