From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: David Miller <davem@davemloft.net>,
pascal.mail@plouf.fr.eu.org, netfilter-devel@vger.kernel.org
Subject: Re: rules matching ipv6 prefix addrs
Date: Thu, 04 Nov 2010 10:41:46 -0400 [thread overview]
Message-ID: <4CD2C62A.50805@zytor.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1011041252410.17937@obet.zrqbmnf.qr>
On 11/04/2010 07:53 AM, Jan Engelhardt wrote:
> On Thursday 2010-11-04 12:36, H. Peter Anvin wrote:
>
>> Guess what... other services like DNS needs to deal with this too, and
>> so far has not; this is part of what needs to happen before nontrivial
>> scale IPv6 deployment happens...
>
> Despite what the RFCs say, IPv6 has big enough an address space that
> static addresses (prefixes) are much more likely to be handed out.
>
Uhm... no. The reason we'll see dynamic prefixes isn't because of lack
of address space but because of mandatory route aggregation (which *is*
being implemented from the start) -- to keep BGP6 and the core routing
tables from melting down.
> Nevertheless, did you consider
>
>>> ip6tables -A FORWARD -d 0:0:0:1000::/0:0:0:ffff::
>>>
>>> to ignore the changing prefix part.
I did, but it means reducing the level of protection given; I'd consider
it an emergency hack.
-hpa
next prev parent reply other threads:[~2010-11-04 14:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 20:52 rules matching ipv6 prefix addrs David Miller
2010-11-02 21:24 ` Maciej Żenczykowski
2010-11-03 7:37 ` Patrick McHardy
2010-11-03 9:29 ` Pascal Hambourg
2010-11-03 10:51 ` Jan Engelhardt
2010-11-03 12:19 ` David Miller
2010-11-03 12:32 ` Jan Engelhardt
2010-11-03 21:55 ` David Miller
2010-11-03 22:36 ` H. Peter Anvin
2010-11-03 22:52 ` Jan Engelhardt
2010-11-04 2:12 ` H. Peter Anvin
2010-11-04 4:14 ` Patrick McHardy
2010-11-04 8:58 ` Jan Engelhardt
2010-11-04 11:36 ` H. Peter Anvin
2010-11-04 11:53 ` Jan Engelhardt
2010-11-04 14:41 ` H. Peter Anvin [this message]
2010-11-04 20:02 ` Pascal Hambourg
2010-11-04 12:07 ` Pascal Hambourg
2010-11-04 11:08 ` Stephen Clark
2010-11-04 11:29 ` Pascal Hambourg
2010-11-04 12:07 ` Stephen Clark
2010-11-04 12:19 ` Pascal Hambourg
2010-11-04 13:34 ` Jozsef Kadlecsik
2010-11-04 14:41 ` H. Peter Anvin
2010-11-04 17:35 ` Jeff Haran
2010-11-04 18:45 ` H. Peter Anvin
2010-11-04 19:24 ` Jan Engelhardt
2010-11-04 19:26 ` H. Peter Anvin
2010-11-04 11:55 ` Pascal Hambourg
2010-11-04 14:42 ` H. Peter Anvin
2010-11-04 20:00 ` Pascal Hambourg
2010-11-03 12:56 ` Pascal Hambourg
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=4CD2C62A.50805@zytor.com \
--to=hpa@zytor.com \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pascal.mail@plouf.fr.eu.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.