From: Phil Oester <kernel@linuxace.com>
To: netfilter-devel@vger.kernel.org
Subject: [RFC][PATCH] nftables: add slash to chain syntax
Date: Sat, 30 Nov 2013 15:20:23 -0800 [thread overview]
Message-ID: <20131130232022.GA23206@home> (raw)
The current syntax when handling chains seems counterintuitive to me. I would
expect that "add chain" would have the name of the chain directly after the
keyword "chain". But instead, the name of the table is there, with the chain
after. I think a better syntax might be this:
add chain <table>/<chain>
which seems clearer to me. And it has the added benefit of following the
"everything is a file" paradigm. Who knows - maybe someday we can add a sysfs
interface for nftables, and this will fit nicely within a tree:
nftables
tables
chains
rules
Thoughts? Attached patch is a general proof of concept.
Phil
next reply other threads:[~2013-11-30 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 23:20 Phil Oester [this message]
2013-11-30 23:22 ` [RFC][PATCH] nftables: add slash to chain syntax Phil Oester
2013-12-04 14:05 ` Pablo Neira Ayuso
2013-12-04 15:16 ` Arturo Borrero Gonzalez
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=20131130232022.GA23206@home \
--to=kernel@linuxace.com \
--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).