* Floris Bruynooghe | 2008-05-20 23:13:28 [+0100]: >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?
It is already late here and my perceptive faculty could be limited but I didn't spot any problems. Did you double check the setup (e.g. routes) and did you test connectivity it with e.g. teredo (for testing purpose)? >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. No - the turtle is still (Tue May 20 23:02:14 UTC 2008) dancing ... ;) HGN -- Hagen Paul Pfeifer <[EMAIL PROTECTED]> || http://jauu.net/ Key Id: 0x98350C22 Key Fingerprint: 490F 557B 6C48 6D7E 5706 2EA2 4A22 8D45 9835 0C22 Always in motion, the future is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
