Clean up release notes

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1985 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2005-03-07 16:51:37 +00:00
parent 48ba931536
commit cefa44418d

View File

@ -9,8 +9,8 @@ Problems corrected in version 2.2.2
2) If A is a user-defined action and you have file /etc/shorewall/A 2) If A is a user-defined action and you have file /etc/shorewall/A
then when that file is invoked, the $TAG value may be incorrect. then when that file is invoked, the $TAG value may be incorrect.
3) If an iptables command that generates a logging rule failed 3) Previously, if an iptables command generating a logging rule
previously, the Shorewall [re]start was still successful. This error failed, the Shorewall [re]start was still successful. This error
is now considered fatal and Shorewall will be either restored from is now considered fatal and Shorewall will be either restored from
the last save (if any) or it will be stopped. the last save (if any) or it will be stopped.
@ -29,10 +29,15 @@ New Features in version 2.2.2
display. display.
4) The 2.6.11 Linux kernel and iptables 1.3.0 now allow port ranges 4) The 2.6.11 Linux kernel and iptables 1.3.0 now allow port ranges
to appear in port lists. If Shorewall detects this capability, it to appear in port lists handled by "multiport match". If Shorewall
will allow port ranges to appear in port lists. Be cautioned that detects this capability, it will use "multiport match" for port
each port range counts for TWO ports and a port list can still lists containing port ranges. Be cautioned that each port range
specify a maximum of 15 ports. counts for TWO ports and a port list handled with "multiport match"
can still specify a maximum of 15 ports.
As always, if a port list in /etc/shorewall/rules is incompatible
with "multiport match", a separate iptables rule will be generated
for each element in the list.
----------------------------------------------------------------------- -----------------------------------------------------------------------
Problems corrected in version 2.2.1 Problems corrected in version 2.2.1