More Lite tweaks -- will they ever end?

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@4081 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-06-13 00:04:15 +00:00
parent 97d281655d
commit 90ad8341ba
5 changed files with 17 additions and 14 deletions

View File

@ -62,7 +62,7 @@ debug)
If you include the keyword debug as the first argument to any
of these commands:
start|stop|restart|reset|clear|refresh|check|add|delete
start|stop|restart|reset|clear|add|delete
then a shell trace of the command is produced. For example:
@ -157,13 +157,6 @@ logreject)
See also \"help address\""
;;
refresh)
echo "refresh: refresh
The rules involving the broadcast addresses of firewall interfaces,
the black list, and ECN control rules are recreated to reflect any
changes made. Existing connections are untouched."
;;
reject)
echo "$1: $1 <address> ...
Causes packets from the specified <address> to be rejected
@ -275,7 +268,7 @@ trace)
If you include the keyword trace as the first argument to any
of these commands:
start|stop|restart|reset|clear|refresh|check|add|delete
start|stop|restart|reset|clear|check|add|delete
then a shell trace of the command is produced. For example:

View File

@ -62,3 +62,7 @@ e) On the administrative system, for each firewall system you:
It is possible to have both shorewall and Shorewall Lite
installed on the same system.
For more information, see:
http://www.shorewall.net/CompiledProgram.html#Lite

View File

@ -8335,7 +8335,7 @@ __EOF__
# [re]-Establish routing
#
setup_providers $(find_file providers)
[ -n "$ROUTEMARK_INTERFACES" ] && setup_routes
[ -n "$ROUTEMARK_INTERFACES" ] && setup_routes
progress_message2 "$DOING NAT..."; setup_nat
progress_message2 "$DOING NETMAP..."; setup_netmap
@ -8370,7 +8370,7 @@ __EOF__
save_progress_message "Setting up Actions..."
progress_message2 "$DOING Actions..."; process_actions2
process_actions3
process_actions3
save_progress_message "Applying Policies..."

View File

@ -110,7 +110,7 @@ debug)
If you include the keyword debug as the first argument to any
of these commands:
start|stop|restart|reset|clear|refresh|check|add|delete
start|stop|restart|reset|clear|refresh|check|add|delete|compile
then a shell trace of the command is produced. For example:
@ -362,7 +362,7 @@ trace)
If you include the keyword trace as the first argument to any
of these commands:
start|stop|restart|reset|clear|refresh|check|add|delete
start|stop|restart|reset|clear|refresh|check|add|delete|compile
then a shell trace of the command is produced. For example:

View File

@ -297,11 +297,17 @@
<member>delete</member>
<member>refresh</member>
<member>try</member>
<member>safe-start</member>
<member>safe-restart</member>
<member>show actions</member>
<member>show macros</member>
</simplelist>
</blockquote>