[Top] [All Lists]

Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked

To: CaT <cat@xxxxxxxxxx>
Subject: Re: 2.4.21+ - IPv6 over IPv4 tunneling b0rked
From: Mika Liljeberg <mika.liljeberg@xxxxxxxxx>
Date: 11 Jul 2003 03:04:29 +0300
Cc: yoshfuji@xxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, pekkas@xxxxxxxxxx
In-reply-to: <20030710233931.GG1722@xxxxxxxxxx>
References: <20030710154302.GE1722@xxxxxxxxxx> <1057854432.3588.2.camel@hades> <20030710233931.GG1722@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Fri, 2003-07-11 at 02:39, CaT wrote:
> And having remembered /127 being mentioned as bad I changed the
> interface config to a netmask of /64. Dropped it and brought it
> up and it all works.
> There's something fundamental about ipv6 netmasks that I just don't
> understand...

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).

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. 


<Prev in Thread] Current Thread [Next in Thread>