extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-14 19:54:06 +01:00
Code Issues Packages Projects Releases Wiki Activity

Make CONTINUE work again

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1186 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-03-12 22:58:41 +00:00
parent 2df740db75
commit 699a4cf567
3 changed files with 5 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall2/changelog.txt
View File

@ -62,3 +62,5 @@ Changes since 1.4.10
30) Remove fw->fw policy.
31) Issue clearer message if ip6tables not installed.
32) Make 'CONTINUE' rules work again.

1
Shorewall2/firewall
View File

@ -3061,6 +3061,7 @@ process_rule() # $1 = target
target=reject
;;
CONTINUE)
target=RETURN
;;
DNAT*)
target=ACCEPT

12
Shorewall2/releasenotes.txt
View File

@ -19,18 +19,10 @@ Problems Corrected since 1.4.10
DNAT z1!z2,z3 z4...
Problems Corrected since RC1
Problems Corrected since RC2
1) After a "shorewall stop", traffic routed back to networks in
the /etc/shorewall/routestopped file is accepted. This is required
to allow traffic through a bridge while shorewall is stopped.
1) CONTINUE rules now work again.
2) The /usr/share/shorewall/help file has been corrected.
3) fw->fw policy removed from /etc/shorewall/policy.
4) If IPV6_DISABLE=Yes, a clearer diagnostic message is issued if
ip6tables is not installed.
-----------------------------------------------------------------------
Issues when migrating from Shorewall 1.4.x to Shorewall 2.0.0: