On 12/6/12 4:37 PM, "Mr Dash Four" <[email protected]> wrote:
> >> 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)" Not a defect -- Within the body of a non-inlined action, the SOURCE column cannot include a zone name. > >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". I'll look into that one. > >> 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. The syslog emulator in ulogd2 places IN= in every message and faithfully reproduces this awkward xt_LOG behavior; thus I'm not changing it. -Tom You do not need a parachute to skydive. You only need a parachute to skydive twice. ------------------------------------------------------------------------------ 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
