In article [EMAIL PROTECTED] (at Tue, 04 Apr 2006 02:54:12 +0200), Fredrik
Tolf [EMAIL PROTECTED] says:
radvd. This makes that subnet completely disconnected from IPv6. It
seems that the kernel simply refuses link-local packets on any interface
but the one serving 2002:52b6:8514:100:: (there doesn't appear to be a
hardware error or anything), but I have no idea why.
:
pc17 ~ # ip -6 addr
:
3: wan: BROADCAST,MULTICAST,UP mtu 1500 qlen 1000
inet6 fe80::2c0:26ff:fec0:3305/64 scope link tentative
valid_lft forever preferred_lft forever
:
5: int: BROADCAST,MULTICAST,UP mtu 1500 qlen 1000
inet6 2002:52b6:8514:200::1/64 scope global tentative
valid_lft forever preferred_lft forever
inet6 fe80::202:44ff:fe15:f98b/64 scope link tentative
valid_lft forever preferred_lft forever
Please make sure you have same address on the same link.
From 2.6.15, until the link becomes ready, we do not start autoconf
(and thus, tentative). What does the dmesg say? e.g.
% dmesg | grep ADDRCONF
Regards,
--
YOSHIFUJI Hideaki @ USAGI Project [EMAIL PROTECTED]
GPG-FP : 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]