extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-06-20 17:58:07 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update release documents

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2010-01-11 14:49:45 -08:00
parent 1a74dbf93e
commit fc8bfdcbf9
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/changelog.txt
View File

@ -8,6 +8,8 @@ Changes in Shorewall 4.4.6
4) Allow both <...> and [...] for IPv6 Addresses. 4) Allow both <...> and [...] for IPv6 Addresses.
5) Port mark geometry change from 4.5.
Changes in Shorewall 4.4.5 Changes in Shorewall 4.4.5
1) Fix 15-port limit removal change. 1) Fix 15-port limit removal change.

10
Shorewall/releasenotes.txt
View File

@ -169,6 +169,11 @@ Shorewall 4.4.6
now, if the zone has <interface>:0.0.0.0/0 (even with exclusions), now, if the zone has <interface>:0.0.0.0/0 (even with exclusions),
then it may have no additional members in /etc/shorewall/hosts. then it may have no additional members in /etc/shorewall/hosts.
13) Prior versions of Shorewall applied PREROUTING marking rules to all
packets from 'tracked' provider interfaces when
TC_EXPERT=No. Beginning with Shorewall 4.4.6, packets from these
interfaces will only have those rules applied when TC_EXPERT=Yes.
---------------------------------------------------------------------------- ----------------------------------------------------------------------------
P R O B L E M S C O R R E C T E D I N 4 . 4 . 6 P R O B L E M S C O R R E C T E D I N 4 . 4 . 6
---------------------------------------------------------------------------- ----------------------------------------------------------------------------
@ -182,6 +187,11 @@ Shorewall 4.4.6
verifying the existence of the correct ipset utility before using verifying the existence of the correct ipset utility before using
it to save the contents of the sets. it to save the contents of the sets.
2) Prior versions of Shorewall incorrectly applied PREROUTING marking
rules to all packets from 'tracked' provider interfaces when
TC_EXPERT=No. Beginning with Shorewall 4.4.6, packets from these
interfaces will only have those rules applied when TC_EXPERT=Yes.
---------------------------------------------------------------------------- ----------------------------------------------------------------------------
K N O W N P R O B L E M S R E M A I N I N G K N O W N P R O B L E M S R E M A I N I N G
---------------------------------------------------------------------------- ----------------------------------------------------------------------------