extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-01-03 03:59:16 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fix release docs for transition to Beta 8

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3914 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-05-15 21:08:02 +00:00
parent e133878c98
commit 82413defc5
2 changed files with 12 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Shorewall/changelog.txt
View File

@ -1,3 +1,7 @@
Changes in 3.2.0 Beta 8
1) Issue more helpful BRIDGING=No error messages.
Changes in 3.2.0 Beta 7
1) Fix mark/mask validation.
@ -8,8 +12,6 @@ Changes in 3.2.0 Beta 7
4) Avoid fatal error after missing forwardUPnP rule warning.
5) Issue more helpful BRIDGING=No error messages.
Changes in 3.2.0 Beta 6
1) Fix tc "notfound" errors when 'restart' is run out of ip-up.local.

35
Shorewall/releasenotes.txt
View File

@ -1,4 +1,4 @@
Shorewall 3.2.0 Beta 7
Shorewall 3.2.0 Beta 8
Note to users upgrading from Shorewall 2.x or 3.0
@ -27,27 +27,9 @@ Note to users upgrading from Shorewall 2.x or 3.0
Please see the "Migration Considerations" below for additional upgrade
information.
Problems Corrected in 3.2.0 Beta 7
Problems Corrected in 3.2.0 Beta 8
1) Previously, if 'ash' was used as the SHOREWALL_SHELL then any use of
packet marks would fail.
2) Previously, "shorewall restart" used SHOREWALL_SHELL for
compilation but used the default shell for executing the compiled
script. "shorewall restore" also used the default shell.
3) If the 'upnp' interface option was specified on one or more
interfaces but no forwardUPnP rule was included, the following
diagnostic messages were issued:
WARNING:Missing forwardUPnP rule (required by 'upnp' interface option on eth0)
ERROR: Fatal error in find_logactionchain
Given that the fatal error message is obscure if the first WARNING
isn't noticed, the ERROR message has been eliminated with the
result that Shorewall now starts but won't handle UPnP properly.
4) If BRIDGING=No in shorewall.conf, then an entry in
1) If BRIDGING=No in shorewall.conf, then an entry in
/etc/shorewall/hosts such as the following would result in an
obscure failure of an iptables command:
@ -60,12 +42,6 @@ Problems Corrected in 3.2.0 Beta 7
Other changes in 3.2.0 Beta 7
1) 'shorewall refresh' once again refreshes the tcrules and traffic shaping.
2) Shorewall will now attempt to detect the MTU of devices listed in
/etc/shorewall/tcdevices and will use the detected MTU in setting
up traffic shaping.
Migration Considerations:
1) If you are upgrading from Shorewall 2.x, it is essential that you read
@ -577,3 +553,8 @@ New Features:
b) When HIGH_ROUTE_MARKS=Yes, you can still clear the mark on packets
in the PREROUTING chain (i.e., you can specify a mark value of zero).
14) Shorewall will now attempt to detect the MTU of devices listed in
/etc/shorewall/tcdevices and will use the detected MTU in setting
up traffic shaping.