extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-12-15 10:51:02 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update comments in the Rules module

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2010-12-28 16:02:10 -08:00
parent 2805d16246
commit 17ed14a895
1 changed files with 7 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
Shorewall/Perl/Shorewall/Rules.pm
View File

@ -65,11 +65,7 @@ our @actionstack;
# Action Table
#
# %actions{ <action1> => { requires => { <requisite1> = 1,
# <requisite2> = 1,
# ...
# } ,
# actchain => <action chain number> # Used for generating unique chain names for each <level>:<tag> pair.
# %actions{ actchain => used to eliminate collisions, active => 0|1 - 1 means that the action is in the action stack }
#
our %actions;
#
@ -92,8 +88,8 @@ sub initialize( $ ) {
%macros = ();
@actionstack = ();
$macro_nest_level = 0;
%actions = ();
%usedactions = ();
%actions = ();
%usedactions = ();
if ( $family == F_IPV4 ) {
@builtins = qw/dropBcast allowBcast dropNotSyn rejNotSyn dropInvalid allowInvalid allowinUPnP forwardUPnP Limit/;
@ -268,7 +264,7 @@ sub createactionchain( $ ) {
}
#
# Mark an action as used and create its chain. Returns one if the chain was
# Mark an action as used and create its chain. Returns a reference to the chain if the chain was
# created on this call or 0 otherwise.
#
sub use_action( $ ) {
@ -439,9 +435,9 @@ sub map_old_actions( $ ) {
# a) The related action definition file is located.
# a) The action is added to the target table
#
# The second phase (process_actions2) occurs after the policy file is scanned. Each default action's file
# is processed by process_action2(). That function recursively processes action files up the action
# invocation tree, adding to the %usedactions hash as each new action is discovered.
# The second phase (process_actions2) occurs after the policy file is scanned. Each policy action's chain is
# created and its action's file is processed by process_action2(). That function recursively processes action
# files up the action invocation tree, adding to the %usedactions hash as each new action is discovered.
#
# During rules file processing, process_action2() is called when a new action:level:tag:params is encountered.
# Again, each new such tupple is entered into the %usedactions hash.