From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: netfilter-devel@vger.kernel.org, kaber@trash.net
Subject: Re: [RFC nft PATCH] src: add import operation
Date: Wed, 12 Nov 2014 14:17:33 +0100 [thread overview]
Message-ID: <20141112131733.GA1846@salvia> (raw)
In-Reply-To: <20141021112420.11406.7309.stgit@nfdev.cica.es>
On Tue, Oct 21, 2014 at 01:25:47PM +0200, Arturo Borrero Gonzalez wrote:
> The import operation reads a XML or JSON file, with syntax:
> % nft import {xml|json}
>
> A basic way to test this new functionality is:
> % nft export xml | nft import xml
>
> Signed-off-by: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
> ---
>
> NOTE: This patchs requires:
> * [nft] mnl: delete useless parameter nf_sock in batch functions
> * [libnftnl] ruleset: deconstify _get interface
>
> Please comment :-)
The existing approach doesn't support incremental updates. I think
it's important to provide a way to say: 'add this and delete that'
when importing something too, so this interface becomes equivalent to
nft -f.
I think we need a new _parse_file() function to takes a callback as
argument. This callback is invoked per object parsed from the file, so
we can reuse the existing "struct cmd" in nft. I think it's important
to consolidate code, the existing approach where we have different
code to do basically the same is not desirable.
> +int mnl_nft_ruleset_batch_add(const struct nft_ruleset *rs,
> + uint32_t table_flags, uint32_t chain_flags,
> + uint32_t set_flags, uint32_t rule_flags)
[...]
> + ret = mnl_nft_ruleset_batch_add(rs, 0, 0, 0, 0);
So we don't make any global assumption on the flags and so on.
Thanks.
prev parent reply other threads:[~2014-11-12 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 11:25 [RFC nft PATCH] src: add import operation Arturo Borrero Gonzalez
2014-11-12 13:17 ` 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=20141112131733.GA1846@salvia \
--to=pablo@netfilter.org \
--cc=arturo.borrero.glez@gmail.com \
--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 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.