Eliminate warning about policy as rule

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1190 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-03-15 18:40:17 +00:00
parent cd1048bf02
commit 2e929e1083
3 changed files with 16 additions and 5 deletions

View File

@ -66,3 +66,5 @@ Changes since 1.4.10
32) Make 'CONTINUE' rules work again.
33) Correct a comment in the rules file. Update for 2.0.0 final release.
34) Eliminate Warning about Policy as rule when using actions.

View File

@ -2878,10 +2878,14 @@ add_a_rule()
# Complain if the rule is really a policy
if [ -z "$proto" -a -z "$cli" -a -z "$serv" -a -z "$servport" -a -z "$userspec" -a "$logtarget" != LOG ]; then
error_message "Warning -- Rule \"$rule\" is a POLICY"
error_message " -- and should be moved to the policy file"
fi
case $logtarget in
ACCEPT|DROP|REJECT)
if [ -z "$proto" -a -z "$cli" -a -z "$serv" -a -z "$servport" -a -z "$userspec" ] ; then
error_message "Warning -- Rule \"$rule\" is a POLICY"
error_message " -- and should be moved to the policy file"
fi
;;
esac
if [ -n "${serv}${servport}" ]; then
if [ $COMMAND != check ]; then

View File

@ -1,4 +1,4 @@
Shorewall 2.0.0
Shorewall 2.0.0a
----------------------------------------------------------------------
Problems Corrected since 1.4.10
@ -25,6 +25,11 @@ Problems Corrected since RC2
2) A comment in the rules file has been corrected.
Problems Corrected since 2.0.0
1) Using actions in the manner recommended in the documentation
results in a Warning that the rule is a policy.
-----------------------------------------------------------------------
Issues when migrating from Shorewall 1.4.x to Shorewall 2.0.0: