Tom Eastep wrote: > On 4/17/13 5:26 PM, "Dash Four" <[email protected]> wrote: > > >>> Patch TARGETOPTIONS.patch attached. >>> >>> >> It catches most, but not all "known" targets. "INLINE $FW net ; -j NFLOG >> --name test" for example passes without warning or error being issued. >> > > NFLOG accepts options; I'm not going to parse and validate them. > Fair enough.
>> Another question and I know I asked this earlier, but can't find any >> references to this: How do I get rid of my "xt_CT: No such helper XXX" >> messages appearing in my shorewall startup/restart/reload logs? These >> are very annoying and I don't see a way to shut shorewall up! >> > > Use a capabilities file and set WARNOLDCAPSVERSION=No in shorewall.conf. > Hmm, I am not sure I like this, simply because every time I do an update, I have to manually sync this file and I don't need this extra headache. I just looked at your Config.pm, which seems to be the source of these messages - "have_helper", in particular. Am I right in thinking that if "helpers_enabled($helper)" isn't set, then no check takes place and no annoying messages are issued (and shorewall assumes that such capability does not exist)? If that is so, why not add a couple of shorewall.conf variables (you can call then HELPER_*_ENABLE for example) to set/reset these checks, instead of assuming that they all exists (your %helpers_enable" array members are all enabled by default)? ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
