From: Bart De Schuymer <bdschuym@pandora.be>
To: Ankit <ankit.s.shah@elitecore.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Query: No-flush support for ebtables-restore in v2.0.10-4
Date: Sun, 19 May 2013 21:33:51 +0200 [thread overview]
Message-ID: <5199291F.9020009@pandora.be> (raw)
In-Reply-To: <51925792.3050505@elitecore.com>
Op 14/05/2013 17:26, Ankit schreef:
> Hello,
> I am working on ebtables-v2.0.10-4 and I noticed that there is
> no support for "no-flush" switch in ebtables-restore unlike
> iptables-restore. Before I start digging for a roundabout solution, I
> wanted to confirm if there is any particular reason for not
> incorporating no-flush support in ebtables-restore? Does the netfilter
> team have any plans to develop it further?
There's no particular reason for not supporting that. In the sunny-day
scenario it probably suffices to call ebt_get_kernel_table() with second
argument equal to 0 instead of 1.
Bart
prev parent reply other threads:[~2013-05-19 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 15:26 Query: No-flush support for ebtables-restore in v2.0.10-4 Ankit
2013-05-19 19:33 ` Bart De Schuymer [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=5199291F.9020009@pandora.be \
--to=bdschuym@pandora.be \
--cc=ankit.s.shah@elitecore.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).