mirror of
https://gitlab.com/shorewall/code.git
synced 2024-11-15 04:04:10 +01:00
Fix obscure bug in rule activation when zone exclusion is present
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5452 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
8568bc34ea
commit
f6178d50de
@ -4,6 +4,8 @@ Changes in 3.4.0 Final
|
||||
|
||||
2) Restore missing function merge_macro_source_dest.
|
||||
|
||||
3) Fix obscure bug in rule activation logic.
|
||||
|
||||
Changes in 3.4.0 RC 3
|
||||
|
||||
1) Add warning about 'loose' and 'balance'
|
||||
|
@ -4350,7 +4350,7 @@ activate_rules()
|
||||
#
|
||||
chain1=excl_${EXCLUSION_SEQ}
|
||||
EXCLUSION_SEQ=$(( $EXCLUSION_SEQ + 1 ))
|
||||
eval ${chain}_${zone}_ex=$chain1
|
||||
eval ${chain}_${zone1}_ex=$chain1
|
||||
createchain $chain1 no
|
||||
add_exclusions filter $chain1 $exclusions1
|
||||
run_iptables -A $chain1 -j $chain
|
||||
|
@ -39,6 +39,9 @@ Problems Corrected in 3.4.0 Final.
|
||||
|
||||
merge_macro_source_dest: command not found
|
||||
|
||||
3) An obscure bug in rule activation having to do with the new
|
||||
exclusion feature in /etc/shorewall/hosts has been corrected.
|
||||
|
||||
Migration Considerations:
|
||||
|
||||
If you are migrating from a Shorewall version earlier than 3.2.0 then
|
||||
@ -673,7 +676,12 @@ New Features in Shorewall 3.4:
|
||||
/etc/shorewall/params and those required at run-time may be set in
|
||||
/etc/shorewall/init.
|
||||
|
||||
Note: EXPORTPARAMS was actually introduced in Shorewall version
|
||||
Note 1: If you need shell variables values in your
|
||||
/etc/shorewall/stop or /etc/shorewall/stopped script, then you need
|
||||
to set their values in /etc/shorewall/stop. /etc/shorewall/init is
|
||||
not invoked during processing of the 'stop' and 'clear' commands.
|
||||
|
||||
Note 2: EXPORTPARAMS was actually introduced in Shorewall version
|
||||
3.2.9. It is described here for the benefit of those who did not
|
||||
install that version.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user