All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: David Miller <davem@davemloft.net>, jengelh@medozas.de
Cc: pascal.mail@plouf.fr.eu.org, netfilter-devel@vger.kernel.org
Subject: Re: rules matching ipv6 prefix addrs
Date: Wed, 03 Nov 2010 18:36:12 -0400	[thread overview]
Message-ID: <5ca75042-e809-4439-856a-e3da43cb6c23@email.android.com> (raw)
In-Reply-To: <20101103.145503.104044664.davem@davemloft.net>

The prefix is set by the ISP and can change at any time.  In IPv4 this is generally masked by NAT, but in IPv6 it affects every host.

What changes (in the normal case) is the common prefix of the network, i.e. the fraction delegated by the ISP.  If your ISP gives you a /56, for example, those 56 bits can change at any time, and that will affect all the hosts on your network.


"David Miller" <davem@davemloft.net> wrote:

>From: Jan Engelhardt <jengelh@medozas.de>
>Date: Wed, 3 Nov 2010 13:32:42 +0100 (CET)
>
>> On Wednesday 2010-11-03 13:19, David Miller wrote:
>>>
>>>> What would be a use case ?
>>>
>>>I thought it was painfully obvious but...  the use case is setting up
>>>a rule that matches the prefix addresses and having such rules still
>>>work properly when the link flaps onto a link with a different prefix
>> 
>> A link moving to another link.. you lost me there.
>> Links usually don't move, packets do. Can you provide `ip addr`-style
>
>> output of Before and After, to better see what's being meant?
>
>This issue was expressed to me by H. Peter Anvin, let's CC: him
>to get some specific examples.
>
>HPA?

-- 
Sent from my mobile phone.  Please pardon any lack of formatting.

  reply	other threads:[~2010-11-03 22:38 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 [this message]
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
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=5ca75042-e809-4439-856a-e3da43cb6c23@email.android.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.