A lot of times when I see a post like this, there hasn't been an IPv6 address assigned to the local area connection interface. However, you mentioned that you're doing RA and the LAN connection does indeed grab an address.
Yes, it definitely is grabbing an address, and it's a valid autoconfigure address (the first 64 bits are indeed my routed HE subnet, and the last 64 bits are the MAC address derived address... the default gateway is the link-local address address of my Linux gateway... which seems weird to me that it uses the link-local address, I don't know why it doesn't show the gateway's global address, but my understanding is that this is nonetheless correct for Windows. And again, from the command line, ICMP based tools like ping6, tracert, all work fine. It's just higher level (TCP/UCP) connections that don't seem to work.)
For the heck of it, I just created an XP VM on another system, so I would be working with a clean, fresh install of XP SP3, with all updates applied. I got the exact same thing, although curiously, that machine is picking up a bunch of IPv6 addresses. Although I thought I had a fairly good understanding of IPv6, I must admit that I really don't understand the ins and outs of the Microsoft IPv6 stack and netsh. It seems unnecessarily complicated to me (by a factor of like 10.) :-) Every one of my Linux boxes (about 7 of them if you include VMs, including several CentOS 5.6, and Ubuntu Server and Desktop 10.10, and 11.04) are behaving exactly as expected, picking up exactly one valid autoconfigure IPv6 address on eth0, and inserting exactly one route to 0::/0, pointed at the gateway, while the Windows XP boxen are doing all kinds of crazy things. I do also have one Windows 7 box which I just brought up, and it is working fine as well, so it's only XP that is having problems. On the Windows 7 box I see two IPv6 addresses (not counting the link local one), one of which says "IPv6 Address", and the other "Temporary IPv6 Address", both of which are on my routed subnet. Not sure what that's about, but again, that box works, with zero configuration.
Here's the output from ipconfig on the non-working XP VM. Again, this is a clean XP SP3 install + all updates, nothing else installed or altered on it, no AV software, Windows firewall disabled in Control Panel:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : nullmodem.org
IP Address. . . . . . . . . . . . : 192.168.2.129
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 2001:470:1f0f:bb9:600e:3b27:9f5b:a35b
IP Address. . . . . . . . . . . . : 2001:470:1f0f:bb9:a00:27ff:fe0c:58b2
IP Address. . . . . . . . . . . . : fe80::a00:27ff:fe0c:58b2%6
IP Address. . . . . . . . . . . . : 2001:470:1f0f:bb9:18a9:f585:6b6c:af76
IP Address. . . . . . . . . . . . : 2001:470:1f0f:bb9:a00:27ff:fe0c:58b2
IP Address. . . . . . . . . . . . : fe80::a00:27ff:fe0c:58b2%4
Default Gateway . . . . . . . . . : 192.168.2.1
fe80::a00:27ff:fe70:cdc2%4
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
Default Gateway . . . . . . . . . :
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . : nullmodem.org
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.2.129%2
Default Gateway . . . . . . . . . :
Why all those addresses? I don't get that. And again, just like the XP box on physical hardware, the XP VM can ping6, tracert to IPv6 only hosts just fine, but any higher level tests, like from a web browser or telnet, not only fail, but I don't even see any packets coming from the box when I run a tcpdump on the segment.
Here's my radvd.conf for good measure... looks pretty straightforward, but maybe there's something missing that XP and only XP needs?
interface eth0
{
AdvSendAdvert on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
prefix 2001:470:1f0f:bb9::1/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
};
};
Should "AdvRouterAddr" be set to on? The above is what I've seen in most example radvd.conf files, so that's what I've used, but isn't the whole point of the router advertisement protocol supposed to be, well, to advertise the router? :-) Still, everything but my XP boxes seems to work fine with radvd configured as it is. Maybe I'll give that a try though.
Have you tried setting an IP address manually just to see what would happen?
No, but I'll give it a try. I need to figure out how to do so with netsh first though, as you've probably figured out, I'm a Linux guy. :-)