I am sorry. I thought I was clear. I guess I did not state explicitly
the discrepancy.
The comments (#) I put in the original post (below) describe a
difference between the example and the definition.
The definition says
"copy the template to /etc/shorewall/action.<whatever>"
The example says
"copy the template to /etc/shorewall/<whatever>"
In the definition, there is an "action." appended to
"<whatever>"
I would think that if not only confusing this might cause trouble code wise.
-Alex
[Original post at the end of this mail]
Tom Eastep wrote:
> On Tue, 9 Dec 2003, Alex Martin wrote:
>
>
>>Something is a little off...
>>
>
>
> Alex and the list.
>
> Let''s make things very explicit -- I live with an
Alzheimer''s patient 24
> hours a day; I''m near the end of my rope.
>
> If you have something to say, then say it. If you want to post riddles,
> then post them on some other list.
>
> -Tom
[original post]
From the shorewall 1.4.9 Beta 1 News:
#Start section 4
4.
Support for user defined rule ACTIONS has been implemented through two
new files:
/etc/shorewall/actions - used to list the user-defined ACTIONS.
/etc/shorewall/action.template - For each user defined <action>, copy
this file to /etc/shorewall/action.<action> and add the appropriate
# here it says to copy the template
# to "/etc/shorewall/action.<whatever>"
rules for that <action>. Once an <action> has been defined, it may
be
used like any of the builtin ACTIONS (ACCEPT, DROP, etc.) in
/etc/shorewall/rules.
Example: You want an action that logs a packet at the ''info''
level and
accepts the connection.
In /etc/shorewall/actions, you would add:
LogAndAccept
You would then copy /etc/shorewall/action.template to
/etc/shorewall/LogAndAccept and in that file, you would add the two rules:
# here it says to copy the template
# to "/etc/shorewall/<whatever>"
LOG:info
ACCEPT
#End Section 4
[end original post]