From: Phil Oester <kernel@linuxace.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] ip6tables: don't print out /128
Date: Sun, 7 Jul 2013 21:19:08 -0700 [thread overview]
Message-ID: <20130708041908.GA5532@linuxace.com> (raw)
In-Reply-To: <20130708022641.GA14090@localhost>
On Mon, Jul 08, 2013 at 04:26:41AM +0200, Pablo Neira Ayuso wrote:
> I just look at the source of old iptables releases (1.4.11) and it
> displays the /32 with iptables -L. I prefer if we restore that
> behaviour, ie. we get it back to display /32, for historial reasons.
That does not appear to be correct.
# ./iptables-multi main -V
iptables v1.4.10
# ./iptables-multi main -L foo
Chain foo (0 references)
target prot opt source destination
all -- 1.2.3.4 anywhere
>From what I can tell, the comment
/* we don't want to see "/32" */
has existed in the tree since at least 3/2000.
Phil
next prev parent reply other threads:[~2013-07-08 4:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 20:11 [PATCH] ip6tables: don't print out /128 Phil Oester
2013-07-08 2:26 ` Pablo Neira Ayuso
2013-07-08 4:19 ` Phil Oester [this message]
2013-07-08 16:55 ` Pablo Neira Ayuso
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=20130708041908.GA5532@linuxace.com \
--to=kernel@linuxace.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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 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).