From: Patrick McHardy <kaber@trash.net>
To: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Cc: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>
Subject: Re: nftables add vs replace
Date: Tue, 21 Jan 2014 11:49:55 +0000 [thread overview]
Message-ID: <20140121114955.GA27718@macbook.localnet> (raw)
In-Reply-To: <52DE5E10.5000403@linux.intel.com>
On Tue, Jan 21, 2014 at 01:46:24PM +0200, Tomasz Bursztyka wrote:
> Hi Arturo,
>
> >Think about a 'ruleset.nft' file starting like this:
> >==== 8< ====
> >wipe ruleset
>
> That hits the current problem: you have to wipe-out all before
> creating stuff: it's greedy,
> instead of just letting untouched/replace what exists already and
> adding new ones.
I'm working on my proposed solution. So far just the add vs. create,
the replace command will be a bit more involved.
# src/nft create table filter
<cmdline>:1:1-19: Error: Could not add table: File exists
create table filter
^^^^^^^^^^^^^^^^^^^
# src/nft add table filter
#
next prev parent reply other threads:[~2014-01-21 11:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 11:06 nftables add vs replace Patrick McHardy
2014-01-21 11:27 ` Pablo Neira Ayuso
2014-01-21 11:32 ` Patrick McHardy
2014-01-21 11:37 ` Arturo Borrero Gonzalez
2014-01-21 11:45 ` Patrick McHardy
2014-01-21 15:15 ` Phil Oester
2014-01-21 17:37 ` Patrick McHardy
2014-01-22 8:38 ` Pablo Neira Ayuso
2014-01-22 8:54 ` Patrick McHardy
2014-01-22 9:17 ` Pablo Neira Ayuso
2014-01-22 9:30 ` Patrick McHardy
2014-01-21 11:46 ` Tomasz Bursztyka
2014-01-21 11:49 ` Patrick McHardy [this message]
2014-01-21 12:08 ` Tomasz Bursztyka
2014-01-21 12:11 ` Patrick McHardy
2014-01-21 12:17 ` Tomasz Bursztyka
2014-01-21 12:25 ` Patrick McHardy
2014-01-21 12:49 ` Tomasz Bursztyka
2014-01-21 14:05 ` Arturo Borrero Gonzalez
2014-01-21 15:10 ` Patrick McHardy
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=20140121114955.GA27718@macbook.localnet \
--to=kaber@trash.net \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tomasz.bursztyka@linux.intel.com \
/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.