From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Mart Frauenlob <mart.frauenlob@chello.at>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nfct parameters
Date: Thu, 7 Apr 2016 19:02:27 +0200 [thread overview]
Message-ID: <20160407170227.GA5825@salvia> (raw)
In-Reply-To: <5706290C.7080000@chello.at>
On Thu, Apr 07, 2016 at 11:31:56AM +0200, Mart Frauenlob wrote:
> Good day,
>
> while I'm writing bash completion code for conntrack-tools, I browsed
> through the source and found some things, that raised this questions for me
> (I'm no C developer, so limited here).
>
> 1: Are there three undocumented parameters?
> namely: disable, default-get, default-set
> At least there are functions that do something... not sure what exactly w/
> the default-* cmds.
They set the default timeouts. They provide a replacement for the
/proc/ interface to set default conntrack protocol timeouts.
'disable' is for userspace helpers. You can disable enqueueing packets
to userspace for helper inspection.
> 2: in src/nfct-extensions/timeout.c there is:
>
> static void
> nfct_cmd_timeout_usage(char *argv[])
> {
> fprintf(stderr, "nfct v%s: Missing command\n"
> "%s <list|add|delete|get|flush|set> timeout "
> "[<parameters>, ...]\n", VERSION, argv[0]);
> }
>
> Where a 'set' command is printed. Which is another discrepancy?
>
> If my reading is correct, please take this mail as a bug report.
Right, we seem not to have any 'set' there.
prev parent reply other threads:[~2016-04-07 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 9:31 nfct parameters Mart Frauenlob
2016-04-07 17:02 ` 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=20160407170227.GA5825@salvia \
--to=pablo@netfilter.org \
--cc=mart.frauenlob@chello.at \
--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;
as well as URLs for NNTP newsgroup(s).