From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Shorewall: iptables: No chain/target/match by that name.
Date: Sun, 10 Feb 2013 08:49:10 -0800 [thread overview]
Message-ID: <CAN0CFw22Db5bocyr62rPk52=WYycq0e8gXr3GjLQ1r4RdX7mWQ@mail.gmail.com> (raw)
In-Reply-To: <5117459C.60708@dmj.nu>
>> I'm getting the following when restarting shorewall:
>>
>> # /etc/init.d/shorewall restart
>> * Stopping firewall ...
>> * Starting firewall ...
>> iptables: No chain/target/match by that name.
>>
>> How can I find out which chain/target/match I need to compile into the
>> kernel? shorewall-init.log does not indicate any problems and I have
>> LOG_VERBOSITY=2 in shorewall.conf which is the maximum.
>
> I hade the same problem. Using "shorewall trace restart" I could figure
> out which chain/target/match that was missing.
Thanks, that got them. A couple oddities:
'shorewall trace restart' produced output the same as
shorewall-init.log which contained no info useful for this purpose.
However, 'shorewall trace restart > file.txt' sent completely
different output to file.txt which did contain all of the needed info.
How can that be?
I got a lot of "No such file or directory" lines in file.txt for stuff
like -j LOGMARK, -m condition, -m geoip, -m ipp2p, nfacct which I
can't find in the kernel. Numerous other miscellaneous errors there
too. Ignore them if they aren't outputted by the initscript?
- Grant
next prev parent reply other threads:[~2013-02-10 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 5:19 [gentoo-user] Shorewall: iptables: No chain/target/match by that name Grant
2013-02-10 7:00 ` Dan Johansson
2013-02-10 12:07 ` covici
2013-02-10 16:49 ` Grant [this message]
2013-02-10 17:07 ` Grant
2013-02-11 3:56 ` Adam Carter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN0CFw22Db5bocyr62rPk52=WYycq0e8gXr3GjLQ1r4RdX7mWQ@mail.gmail.com' \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox