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

Update release documents

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8425 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2008-04-16 16:44:49 +00:00
parent 4b5273c6bb
commit ba0b8056ff
2 changed files with 14 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Shorewall-common/changelog.txt
View File

@ -24,6 +24,10 @@ Changes in 4.1.7
12) Merge Tuomo's SANE support patch.
13) Fix silly duplicate-rule error.
14) Fix IPSEC host entry with DYNAMIC_ZONES=Yes
Changes in 4.1.6
1) Deprecate IMPLICIT_CONTINUE=Yes

12
Shorewall-common/releasenotes.txt
View File

@ -83,8 +83,8 @@ Problems corrected in Shorewall 4.1.7.
between the time that forwarding was enabled and when the nat table
rules were instantiated.
Beginning with Shorewall 4.0.11, enabling of forwarding is deferred
until after the rules are in place.
Beginning with Shorewall 4.0.11 and 4.1.7, enabling of forwarding
is deferred until after the rules are in place.
Problems corrected in Shorewall-perl 4.1.7.
@ -113,6 +113,14 @@ Problems corrected in Shorewall-perl 4.1.7.
6) A MARK of ":" in /etc/shorewall/tcrules would produce Perl
run-time errors.
7) If both the ESTABLISHED and RELATED sections were present then
each connection through chains controlled by a RATE/LIMIT in
/etc/shorewall/policies was counted twice toward the limit.
8) If DYNAMIC_ZONES=Yes and an entry in /etc/shorewall/hosts for an
IPv4 zone specified 'ipsec', dynamic IPSEC zone members were
mis-handled by the generated ruleset.
New Features in 4.1.7.
1) If an interface fails when using balanced multi-ISP routing, the