netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: linux-kernel@vger.kernel.org
Cc: Mika Liljeberg <mika.liljeberg@welho.com>, netdev@oss.sgi.com
Subject: Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked
Date: 11 Jul 2003 03:49:14 +0200	[thread overview]
Message-ID: <1057888154.26854.324.camel@localhost> (raw)
In-Reply-To: <1057881869.3588.10.camel@hades>

On fre, 2003-07-11 at 02:04, Mika Liljeberg wrote:
> Well, the thing is that prefix:: is a special anycast address that
> identifies a router on the link prefix::/n, where n is the prefix
> length. You had configured a 127-bit link prefix, meaning that you had
> only one valid unicast address (last bit == 1) in addition to the router
> anycast address (last bit == 0).

Thanks for the explanation, I've been struggling to understand what
Yoshfuji tried to explain to me earlier on this topic (see "IPv6 bugs
introduced in 2.4.21" - ie. my bogus bugreport), now it all makes
perfect sense :-)

> Normally, IPv6 networks are supposed to use 64-bit on-link prefixes but
> the implementation can be written in such a way that other prefix
> lengths can be configured.
> 
> Setting your tunnel prefix to /64 is certainly the right thing to do. 

If you don't have anything but one /64 for example.. I guess /126's
would be ok as you could rule out the the anycast address? It will
probably work with Linux - but is it wrong in any sense, other than
"breaking" with EUI-64/autoconfiguration?

-- 
Cheers,
André Tomt
andre@tomt.net

  reply	other threads:[~2003-07-11  1:49 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10 15:43 2.4.21+ - IPv6 over IPv4 tunneling b0rked CaT
2003-07-10 15:55 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-10 15:58   ` CaT
2003-07-10 16:08   ` Pekka Savola
2003-07-10 16:18     ` 2.4.21+ - IPv6 over IPv4 tunneling broken YOSHIFUJI Hideaki / 吉藤英明
2003-07-10 16:19       ` Pekka Savola
2003-07-13 14:49     ` 2.4.21+ - IPv6 over IPv4 tunneling b0rked Anand Kumria
2003-07-13 16:23       ` Pekka Savola
2003-07-10 19:57   ` Mika Penttilä
2003-07-10 16:27 ` Mika Liljeberg
2003-07-10 23:39   ` CaT
2003-07-11  0:04     ` Mika Liljeberg
2003-07-11  1:49       ` Andre Tomt [this message]
2003-07-11  2:03         ` Mika Liljeberg
2003-07-11  2:03         ` 2.4.21+ - IPv6 over IPv4 tunneling broken YOSHIFUJI Hideaki / 吉藤英明
2003-07-11  4:51         ` 2.4.21+ - IPv6 over IPv4 tunneling b0rked Pekka Savola
2003-07-11  5:20           ` Mika Liljeberg
2003-07-11  5:22             ` Pekka Savola
2003-07-11  5:39               ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11  8:46                 ` Pekka Savola
2003-07-11  9:04                   ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11  9:39                     ` Mika Penttilä
2003-07-11 10:03                     ` Pekka Savola
2003-07-11 10:47                       ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 10:47                         ` Pekka Savola
2003-07-11 10:59                           ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 10:59                             ` Pekka Savola
2003-07-11 11:03                               ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-11 11:04                                 ` Pekka Savola
2003-07-11 11:36               ` Mika Liljeberg
2003-07-11 11:48                 ` Pekka Savola
2003-07-11 12:09                   ` Mika Liljeberg
2003-07-11 12:48                     ` Mika Penttilä
2003-07-11 13:38                       ` Mika Liljeberg
2003-07-11 14:27                         ` Mika Penttilä
2003-07-11 14:32                           ` Mika Liljeberg
2003-07-11 15:16                             ` Mika Penttilä
     [not found] <20030710.214551.08349572.davem@redhat.com>
2003-07-14 23:49 ` kuznet
2003-07-15  6:14   ` Pekka Savola
2003-07-15 14:46     ` kuznet
2003-07-15 17:29       ` Pekka Savola
2003-07-15 23:19         ` kuznet
2003-07-16  6:03           ` Pekka Savola
2003-07-17  0:03             ` kuznet
2003-07-17  6:50               ` Pekka Savola

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=1057888154.26854.324.camel@localhost \
    --to=andre@tomt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.liljeberg@welho.com \
    --cc=netdev@oss.sgi.com \
    /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).