> Patch PARAM.patch attached.
With the PARAM1.patch applied...

action.circ1
~~~~~~~~~~~~
$1 $2 $3

rules
~~~~~
circ1(LOG:info,$FW,net)

I get "ERROR: Unknown Interface (fw)"

Also:

actions
~~~~~~~
circ2 inline
circ3 inline

action.circ2
~~~~~~~~~~~~
circ3($1)

action.circ3
~~~~~~~~~~~~
$1

rules
~~~~~
circ2(LOG:info) $FW net

I get "ERROR: Invalid Action (circ2(LOG:info)) in inline action".

> For number 2, have you tried simply placing an empty COMMENT line as the
> first line of C_ACTION?
Yep, that does the trick.

> The space is there to separate the tag from the following 'IN=' in the
> log message; without it, the log message reads
> ...Shorewall:my_log7890123456789IN=eth0....
I get the same issue with NFLOG (in the form of --nflog-prefix 
"Shorewall:log789012345678 ") where there is no such thing as "IN=", at least 
not in 99% of all cases anyway.

> Looks like there is no target named 'nonSyn' (note that the standard
> shorewall action is 'NotSyn').
Looks like I shouldn't be relying on your shorewall announcements (where you 
used "NonSyn") and should stick to reading the relevant man pages instead. 
"NotSyn" works as expected though.

> Obviously not. COMMA.patch attached.
Works as expected this time.

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel

Reply via email to