> Not a defect -- Within the body of a non-inlined action, the SOURCE column > cannot include a zone name. Didn't know that. Should I assume (and test) for destination zones then?
>> 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. xt_LOG is not the only filter in ulogd2. In fact, it is one of about a dozen others. The likelihood that NFLOg's xt_LOG will be used instead of the LOG target is slim-to-none. Why is it so difficult for you to change this and account for the extra space then? ------------------------------------------------------------------------------ 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
