From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: sclark46@earthlink.net, 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 15:26:14 -0400 [thread overview]
Message-ID: <4CD308D6.8050203@zytor.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1011042021040.16729@obet.zrqbmnf.qr>
On 11/04/2010 03:24 PM, Jan Engelhardt wrote:
>
> On Thursday 2010-11-04 15:41, H. Peter Anvin wrote:
>> On 11/04/2010 07:08 AM, Stephen Clark wrote:
>>>>
>>>> Now, the upstream (ISP-assigned) prefix changes to
>>>> 2001:6b2f:1705::/48. RA will handle reassigning addresses to actual
>>>> downstream hosts, but things that explicitly encode IPv6 addresses
>>>> need to be changed, and that includes ip6tables, in this case these
>>>> rules now need to refer to 2001:6b2f:1705:0000::/52,
>>>> 2001:62bf:1705:1000::/52 and so on.
>>>>
>>> Won't this break existing tcp connections if all of a sudden you get a
>>> new address?
>>
>> Yes. Welcome to the brave new world of IPv6. One of many reasons why IPv6 IMO
>> is seriously misdesigned, but it's what we have and we no longer have the time
>> to do anything else.
>
> Well we know academia is evil as they never talk to us on linux-netdev
> when designing protocols behind closed doors.
>
> One could also argue that IPv6 just does what it does, and that any
> extra feature is layered... what you want sounds like Shim6.
Or Mobile IPv6 or whatever... however, it's unlikely that whatever
solution is going to be universal.
-hpa
next prev parent reply other threads:[~2010-11-04 19:27 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
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 [this message]
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=4CD308D6.8050203@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 \
--cc=sclark46@earthlink.net \
/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).