Neighbour discovery problem

[Floris Bruynooghe <floris.bruynooghe@gmail.com>]

Hello

My 6to4 prefix is 2002:5044:52b7::/48, so I've configured the sit0 of
my router to use 2002:5044:52b7::1/16 and that seemes to work.

The eth0 interface I wanted to configure to 2002:5044:52b7:1::1/64,
but that didn't work out.  Although "ip -6 maddr show" would show it
as listening on ff02::1:ff0:1 it ignored neighbour solicitation
messages.  When initiating communication from the router to the other
host it would work fine, and while the router was in the neighbour
cache everything would work.  But having a regular ping from the
router seems a little odd... ;-)

Once I changed the eth0 address to use the autogenerated host ID
(2002:5044:52b7:1:230:18ff:fea3:18c4/64) it would respond to neighbour
solicitation on the corresponding multicast address
(ff02::1:ffa3:18c4).

Is there any reason that ::1 should not work?  Or is there something
else wrong?


Unrelated to this.  Is www.kame.net down on IPv6?  I only seem to be
able to reach it on IPv4, but communication with ipv6.google.com works
flawlessly.


Thanks
Floris


-- 
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org