Tom Eastep wrote: > On 06/01/2013 07:22 AM, Dash Four wrote: > > >> IFLOG is the "inline" equivalent of FLOG, which I have posted before: >> >> action.FLOG >> ~~~~~~~~~~~ >> ?IF $1 >> NFLOG($1,0,1) >> ?ENDIF >> ?IF $2 >> ?SET @chain $3 ? $3 : " " >> ?SET @disposition $4 ? $4 : " " >> LOG:info(tcp_options,ip_options,macdecode,tcp_sequence,uid) >> ?END IF >> ?IF $5 >> $5 >> ?END IF >> >> > > The above doesn't compile -- ?END IF should be ?ENDIF at the very least. > Yeah, I did a quick cut-and-paste from one of my previous posts to save myself the hassle.
> I have taken the standard two-interface example and modified it as follows: > > [...] > > What am I missing? > Define a loopback zone on 'lo' and see what happens, which is what these warnings were all about. I am assuming the "all all" catch-all statement does something to that 'loopback' zone, which shorewall doesn't like, hence the warnings. I did not have these warnings before I explicitly defined the loopback zone (I had it as ipv4 before that). ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
