holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Allow Shorewall6 to recognize TC, IP and IPSET

Browse Source
This commit is contained in:
Tom Eastep 2009-07-26 12:26:49 -07:00
parent 0ee15ec91e
commit 26cb2b1eeb
4 changed files with 18 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Shorewall/Perl/Shorewall/Config.pm
View File

@ -488,6 +488,9 @@ sub initialize( $ ) {
# Location of Files
#
IP6TABLES => undef,
IP => undef,
TC => undef,
IPSET => undef,
#
#PATH is inherited
#

4
Shorewall/changelog.txt
View File

@ -1,3 +1,7 @@
Changes in Shorewall 4.4.0-RC2
1) Fix capabilities file with Shorewall6.
Changes in Shorewall 4.4.0-RC1
1) Delete duplicate Git macro.

30
Shorewall/releasenotes.txt
View File

@ -1,4 +1,4 @@
Shorewall 4.4.0 RC1
Shorewall 4.4.0 RC2
----------------------------------------------------------------------------
R E L E A S E 4 . 4 H I G H L I G H T S
@ -110,25 +110,13 @@ Shorewall 4.4.0 RC1
released.
----------------------------------------------------------------------------
P R O B L E M S C O R R E C T E D I N 4 . 4 . 0 RC1
P R O B L E M S C O R R E C T E D I N 4 . 4 . 0 RC2
----------------------------------------------------------------------------
1) The duplicate macro GIT has been deleted.
1) In RC1, Shorewall6 reported that the capabilities file did not
contain the latest additions.
2) Previously, Shorewall might alter the routing when there were no
providers, even if the "-n" option was given.
3) Previously, NONAT rules on a sub-zone were not exempted from
DNAT/REDIRECT rules of a parent zone.
4) Previously if the 'status' command was run by someone other than
root, the response always show that the firewall was stopped and
the state was 'Unknown'. Now an error message is generated to
indicate that the command may only be run by root.
5) Previously, if 'rpm -U' was used to upgrade from a version of
Shorewall earlier than 4.3.5, then Shorewall would not start
automatically at boot time.
2) Shorewall6 did not recognize the TC, IP and IPSET options.
----------------------------------------------------------------------------
K N O W N P R O B L E M S R E M A I N I N G
@ -137,14 +125,10 @@ Shorewall 4.4.0 RC1
None.
----------------------------------------------------------------------------
N E W F E A T U R E S I N 4 . 4 . 0 RC1
N E W F E A T U R E S I N 4 . 4 . 0 RC2
----------------------------------------------------------------------------
1) A new keyword 'any' may be used in the SOURCE and DEST columns of
the rules file. In the absense of nested zones, 'any' works the
same as 'all'. When there are nested zones, 'any' only selects the
top-level zones. 'any' is intended to be used with
IMPLICIT_CONTINUE=Yes in shorewall.conf.
None.
----------------------------------------------------------------------------
N E W F E A T U R E S IN 4 . 4

8
web/shorewall_index.htm
View File

@ -47,7 +47,7 @@
</tr>
</tbody>
</table>
<hr style="width: 100%; height: 2px;"><span style="font-weight: bold;">2009-07-12</span><br>
<hr style="width: 100%; height: 2px;"><span style="font-weight: bold;">2009-07-26</span><br>
<h3><a href="Notices.html#Shell-EOL">Attention Shorewall-shell users</a><br>
</h3>
<h3><a name="Releases"></a>Current Shorewall Releases</h3>
@ -93,14 +93,14 @@ Release</span><br>
</div>
</td>
<td style="vertical-align: top;"><span style="font-weight: bold;">4.4.0
Beta 4</span><br>
RC 1</span><br>
</td>
<td style="vertical-align: top;"><a
href="http://www1.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta4/releasenotes.txt">Release
href="http://www1.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-RC1/releasenotes.txt">Release
Notes<br>
</a> </td>
<td style="vertical-align: top;"><a
href="http://www1.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta4/known_problems.txt">Known
href="http://www1.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-RC1/known_problems.txt">Known
Problems</a> </td>
</tr>
</tbody>