From: Mart Frauenlob <mart.frauenlob@chello.at>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Mart Frauenlob <mart.frauenlob@chello.at>,
netfilter-devel@vger.kernel.org,
Giuseppe Longo <giuseppelng@gmail.com>,
Eric Leblond <eric@regit.org>
Subject: Re: [PATCH 1/2] iptables: utils: Add bash completion
Date: Thu, 3 Mar 2016 15:18:45 +0100 [thread overview]
Message-ID: <56D847C5.2030707@chello.at> (raw)
In-Reply-To: <20160302125445.GA5129@salvia>
On 02.03.2016 13:54, Pablo Neira Ayuso wrote:
> On Wed, Mar 02, 2016 at 01:24:01PM +0100, Mart Frauenlob wrote:
>> On 02.03.2016 12:34, Pablo Neira Ayuso wrote:
>>> On Thu, Feb 25, 2016 at 04:06:53PM +0100, Mart Frauenlob wrote:
[...]
>
> One idea is to push into iptables some infrastructure so the script
> can inquire iptables on available options. This would be simple C code
> to be places on every extension to print the options. Then, add a tool
> like iptables-completion that you can use to inquire what is possible
> to get as options. Thus, we get a generic script that inquires
> iptables, instead of having them all hardcoded into the script.
One more thing coming into my mind:
A new tool would not be backwards compatible.
While the shell completion could be used with old versions up to when
the -S parameter was introduced. When commenting out some unsupported
extensions in their definition array, it'll be suitable for vast parts.
next prev parent reply other threads:[~2016-03-03 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 15:06 [PATCH 0/2] iptables: utils: Add bash completion Mart Frauenlob
2016-02-25 15:06 ` [PATCH 1/2] " Mart Frauenlob
2016-03-02 11:34 ` Pablo Neira Ayuso
2016-03-02 11:57 ` Jan Engelhardt
2016-03-02 12:24 ` Mart Frauenlob
2016-03-02 12:54 ` Pablo Neira Ayuso
2016-03-02 19:26 ` Mart Frauenlob
2016-03-03 14:18 ` Mart Frauenlob [this message]
2016-02-25 15:06 ` [PATCH 2/2] iptables: Add bash completion to build routine Mart Frauenlob
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=56D847C5.2030707@chello.at \
--to=mart.frauenlob@chello.at \
--cc=eric@regit.org \
--cc=giuseppelng@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).