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

Update release notes and change log for 3.0.0 Final

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@2963 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2005-11-04 17:07:58 +00:00
parent c370293443
commit 57b1472275
2 changed files with 5 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Shorewall/changelog.txt
View File

@ -1,3 +1,7 @@
Changes in 3.0.0 Final
None.
Changes in 3.0.0 RC 3. Changes in 3.0.0 RC 3.
1) ROUTE target and Extended Mark removed from capabilities. 1) ROUTE target and Extended Mark removed from capabilities.

26
Shorewall/releasenotes.txt
View File

@ -1,28 +1,4 @@
Shorewall 3.0.0 RC 3. Shorewall 3.0.0
Problems Corrected in 3.0.0 RC 3:
1) Shorewall no longer has any functionality that is dependent on the
Netfilter ROUTE target and extended packet marking so detection and
reporting of those capabilities has been removed.
2) Previously, the following message could appear in the error output
from the 'check' command:
"/usr/share/shorewall/firewall:  line 128:  $RESTOREBASE:  ambiguous
redirect"
3) The test that Shorewall uses to detect the availability of the
owner match capability has been changed to avoid the generation
of ipt_owner messages under kernel 2.6.14. The affected configuration
files have been updated to warn that +<program name> is not supported
by kernel versions 2.6.14 and later.
4) When MACLIST_TABLE=mangle and an interface is enabled for DHCP (the
'dhcp' option is specified in /etc/shorewall/interfaces) then broadcasts
on UDP port 67 to address 255.255.255.255 from address 0.0.0.0 were being
dropped and logged. While this did not prevent the client from acquiring
an IP address, it could result in lots of log messages.
Migration Considerations: Migration Considerations: