All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Charlie Brady <charlieb-netfilter-devel@budge.apana.org.au>
Cc: Harald Welte <laforge@netfilter.org>,
	netfilter-devel@lists.netfilter.org
Subject: Re: [Patch] ip{, 6}tables-restore -n with existing user defined chain
Date: Sat, 11 Jun 2005 18:12:49 +0200	[thread overview]
Message-ID: <42AB0D81.2080804@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0505181157190.3744@e-smith.charlieb.ott.istop.com>

Charlie Brady wrote:
> 
> I want to redefine an existing chain atomically. I can't do that with
> the iptables command, but can almost do it with iptables-restore -n.
> When I try, iptables barfs because the chain already exists. Duh! Yeah,
> I know it exists, but I want to redefine it.
> 
> I don't see the semantics of this case defined anywhere, and I can't
> find discussion of it in the archives. So I suggest that the semantics
> be redefined, so that iptables-restore -n can redefine an existing chain
> (iptables-restore without -n already does that). I really can't think
> why anyone would depend on the current semantics.

I have no objections, but since I'm not too familiar with that code
I would like to hear Harald's opinion before applying it.

Regards
Patrick

  parent reply	other threads:[~2005-06-11 16:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18 16:07 [Patch] ip{,6}tables-restore -n with existing user defined chain Charlie Brady
2005-05-19 14:14 ` [Patch] ip{, 6}tables-restore " Charlie Brady
2005-05-19 15:43 ` Jonas Berlin
2005-05-19 15:57   ` Charlie Brady
2005-05-19 16:04     ` Charlie Brady
2005-05-19 16:37   ` Carl-Daniel Hailfinger
2005-05-19 16:46     ` Charlie Brady
2005-06-11 16:12 ` Patrick McHardy [this message]
2005-06-12  9:56   ` Harald Welte
2005-06-12 13:38     ` Patrick McHardy
2005-06-12 15:20       ` Charlie Brady
2005-06-12 15:43         ` Patrick McHardy
2005-06-13  2:24           ` Charlie Brady

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=42AB0D81.2080804@trash.net \
    --to=kaber@trash.net \
    --cc=charlieb-netfilter-devel@budge.apana.org.au \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.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 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.