forked from extern/shorewall_code
Update release notes
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8101 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
65df4d9f73
commit
000af58365
@ -18,6 +18,8 @@ Changes in 4.1.4
|
|||||||
|
|
||||||
8) Implement 'sourceonly' host entry option.
|
8) Implement 'sourceonly' host entry option.
|
||||||
|
|
||||||
|
9) Make all non-firewall zones "complex".
|
||||||
|
|
||||||
Changes in 4.1.3
|
Changes in 4.1.3
|
||||||
|
|
||||||
1) Fix NFLOG/ULOG upcasing problem.
|
1) Fix NFLOG/ULOG upcasing problem.
|
||||||
|
@ -154,6 +154,29 @@ Other changes in Shorewall 4.1.4.
|
|||||||
|
|
||||||
tun1 192.168.4.0/24
|
tun1 192.168.4.0/24
|
||||||
|
|
||||||
|
5) Previously, Shorewall classified non-firewall zones as either
|
||||||
|
'simple' or 'complex'. Attributes of a zone which made it 'complex'
|
||||||
|
included:
|
||||||
|
|
||||||
|
- The zone was of type 'ipsec' or 'ipsec4' or it had a hosts
|
||||||
|
entry with the 'ipsec' options.
|
||||||
|
- The zone had OPTIONS, IN OPTIONS or OUT OPTIONS
|
||||||
|
- The zone had more than one network on a given interface
|
||||||
|
- The zone had a hosts file entry with an exclusion.
|
||||||
|
- The zone had a hosts file entry specifying an ipset.
|
||||||
|
|
||||||
|
The handling of 'simple' and 'complex' zones was different.
|
||||||
|
|
||||||
|
- complex zones had their own 'forward' chain (named
|
||||||
|
'<zone>_frwd').
|
||||||
|
- complex zones with exclusions had their own 'input' and
|
||||||
|
'output' chains.
|
||||||
|
|
||||||
|
Beginning with Shorewall-perl 4.1.4, all non-firewall zones will be
|
||||||
|
treated as 'complex'. This will have the effect of one additional
|
||||||
|
filter chain per zone but in most cases, the average number of
|
||||||
|
filter rules traversed by a connection request will be reduced.
|
||||||
|
|
||||||
Migration Issues.
|
Migration Issues.
|
||||||
|
|
||||||
1) Previously, when HIGH_ROUTE_MARKS=Yes, Shorewall allowed non-zero
|
1) Previously, when HIGH_ROUTE_MARKS=Yes, Shorewall allowed non-zero
|
||||||
|
Loading…
Reference in New Issue
Block a user