netdev
[Top] [All Lists]

Re: IPv6 bugs introduced in 2.4.21

To: andre@xxxxxxxxxxx
Subject: Re: IPv6 bugs introduced in 2.4.21
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
Date: Wed, 18 Jun 2003 22:42:57 +0900 (JST)
Cc: netdev@xxxxxxxxxxx, usagi-users@xxxxxxxxxxxxxx
In-reply-to: <1055793048.24660.160.camel@slurv.ws.pasop.tomt.net>
Organization: USAGI Project
References: <1055793048.24660.160.camel@slurv.ws.pasop.tomt.net>
Sender: netdev-bounce@xxxxxxxxxxx
In article <1055793048.24660.160.camel@xxxxxxxxxxxxxxxxxxxxxxx> (at 16 Jun 2003 
21:50:48 +0200), Andre Tomt <andre@xxxxxxxxxxx> says:

> I mailed you guys a little while ago on the "unable to use
> SOMENETWORK::0000 as a nexthop gateway" bug in 2.4.21-pre/rc a while
> ago. It is still present in 2.4.21, rendering the "first" /128 of a
> arbitrary prefixlen unusable - :0000. This is especially bad with /127
> tunnels, rendering :0000 and :0001 unusable). But! There is one more
:

This is NOT the bug but by the spec.
prefix:: is an anycast address, not a unicast;
you cannot use it like an unicast address.

Well...

Do you really need to assign global address on the point-to-point device? 
If yes, you should not use /127 prefix; please use /64 instead.

Thank you.

-- 
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@xxxxxxxxxxxxxx>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF  80D8 4807 F894 E062 0EEA

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