From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Mr Dash Four <mr.dash.four@googlemail.com>,
Netfilter user mailing list <netfilter@vger.kernel.org>
Subject: Re: kernel helper modules parameters
Date: Tue, 14 Feb 2012 01:24:11 +0100 [thread overview]
Message-ID: <20120214002411.GE24194@1984> (raw)
In-Reply-To: <alpine.LNX.2.01.1202131035220.30851@frira.zrqbmnf.qr>
On Mon, Feb 13, 2012 at 10:38:53AM +0100, Jan Engelhardt wrote:
> On Monday 2012-02-13 10:06, Pablo Neira Ayuso wrote:
>
> >On Wed, Feb 08, 2012 at 04:49:07PM +0100, Jan Engelhardt wrote:
> >> On Wednesday 2012-02-08 16:16, Mr Dash Four wrote:
> >>
> >> >
> >> >> "ENOENT has many meanings, and iptables prints just one of them,
> >> >> which is potentially misleading."
> >> >>
> >> > Thanks, this will be corrected I take it?
> >>
> >> Is this wording compatible enough with non-developers? :)
> >>
> >> diff --git a/libiptc/libiptc.c b/libiptc/libiptc.c
> >> index 42d9784..4106afe 100644
> >> --- a/libiptc/libiptc.c
> >> +++ b/libiptc/libiptc.c
> >> @@ -2730,7 +2730,10 @@ TC_STRERROR(int err)
> >> { NULL, ENOPROTOOPT, "iptables who? (do you need to insmod?)" },
> >> { NULL, ENOSYS, "Will be implemented real soon. I promise ;)" },
> >> { NULL, ENOMEM, "Memory allocation problem" },
> >> - { NULL, ENOENT, "No chain/target/match by that name" },
> >> + { NULL, ENOENT, "An object was not found. Check that the chain, "
> >> + "target/match extension, and/or per-extension "
> >> + "named object exists. Look at `dmesg` for "
> >> + "reports about the latter." },
> >
> >This makes sense to me.
> >
> >We still need better (more fine grain) error reporting though. That's
> >one limitation that would be great to solve.
> >
> >Probably the netlink interface will allow us to solve this.
>
> Yes. Did you see my most recent answer yet?:
> http://marc.info/?l=netfilter-devel&m=132705156805852&w=2
Yes, I read it.
Am I missing anything about it regarding this thread?
next prev parent reply other threads:[~2012-02-14 0:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 23:44 kernel helper modules parameters Mr Dash Four
2012-02-08 3:11 ` Mr Dash Four
2012-02-08 3:55 ` Jan Engelhardt
2012-02-08 3:59 ` Mr Dash Four
2012-02-08 5:39 ` Jan Engelhardt
2012-02-08 14:19 ` Mr Dash Four
2012-02-08 14:37 ` Jan Engelhardt
2012-02-08 15:16 ` Mr Dash Four
2012-02-08 15:49 ` Jan Engelhardt
2012-02-08 16:20 ` Mr Dash Four
2012-02-13 9:06 ` Pablo Neira Ayuso
2012-02-13 9:38 ` Jan Engelhardt
2012-02-14 0:24 ` Pablo Neira Ayuso [this message]
2012-02-14 1:07 ` Jan Engelhardt
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=20120214002411.GE24194@1984 \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--cc=mr.dash.four@googlemail.com \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.