On Jun 23, 2013, at 4:49 PM, David Iannucci <[email protected]> wrote:
> On Sun, Jun 23, 2013, at 3:20, Tom Eastep wrote: >> On Jun 23, 2013, at 3:36 AM, David Iannucci wrote: >> >>> Hi, I've been receiving the following error for weeks or months now: >>> >>> iptables: No chain/target/match by that name. >>> >>> I know this is a common thing and that it usually means that >>> something is missing from your kernel config. [........] >> >> More importantly, it is appearing right before the capabilities are >> reported. That leads me to believe that it is being generated during >> capability detection. >> >> 'shorewall trace check' might give enough information to see what >> iptables command is generating the message. But given where it is >> being generated, I would not be concerned that it is causing any type >> of vulnerability. >> >> -Tom > > Thanks for the quick response. Here's a clipping from what shorewall > trace check said, starting from Loading Modules. I note there are quite > a few examples of the error in question here... no idea which one is the > lone one that is printed normally. > > The whole output of the command overran my terminal scroll buffer, > but rather than change that, I've attached the entire output to this > mail; apologies if that's a no-no on this list - or maybe Mailman'll > strip it :-} Before I wade through this, I would like to know if you can reproduce this on the current Shorewall version. -Tom Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
