From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH] iptables: fix error reporting for missing/wrong arguments
Date: Mon, 13 Oct 2008 13:01:51 +0200 [thread overview]
Message-ID: <48F32A9F.1080402@netfilter.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0810121644530.27764@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Sunday 2008-10-12 15:39, Pablo Neira Ayuso wrote:
>> Some work to improve iptables error reporting would be nice, I'll see if
>> I can have a look into this issue.
>
> Improve - in what way?
There are a couple of nitpicking issues that I have observed during some
training sessions, dummy users have the ability to trigger very
confusing error messages from iptables, just one example:
% iptables -I INPUT -m state --state NEW, ESTABLISHED
^
mind the small space
triggers:
iptables v1.4.2-rc1: Bad state `'
Try `iptables -h' or 'iptables --help' for more information.
Another example: if iptables returns EINVAL, it would be nice to add a
string to say "Check your kernel log messages". Even if we don't have
better error handling, at least we can be more informative.
So, when I said *improve* I meant about hunting this sort of issues.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
prev parent reply other threads:[~2008-10-13 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 19:39 [PATCH] iptables: fix error reporting for missing/wrong arguments Pablo Neira Ayuso
2008-10-12 20:45 ` Jan Engelhardt
2008-10-13 11:01 ` Pablo Neira Ayuso [this message]
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=48F32A9F.1080402@netfilter.org \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.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