IPv6 products, community and services
Vista and autoconfig
Anyone out there using Vista with IPv6?
I have a native Vista box and a Vista VM on a Linux box, and neither of them is autoconfiguring an address. The Linux machines in the same network do autoconfigure, as does a Brother printer. If I snoop the network I see what look like perfectly acceptable RA packets.
radvdump sees this on the interface the VM is bridged on:
interface wlan0
{
AdvSendAdvert on;
# Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump
AdvManagedFlag off;
AdvOtherConfigFlag off;
AdvReachableTime 0;
AdvRetransTimer 0;
AdvCurHopLimit 64;
AdvDefaultLifetime 180;
AdvHomeAgentFlag off;
AdvDefaultPreference medium;
AdvSourceLLAddress on;
prefix 2406:a000:0:100::/64
{
AdvValidLifetime 345600;
AdvPreferredLifetime 172800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
}; # End of interface definition
The Vista on the VM was set up with next to no non-standard config; it's basically "out of the box".
The Vista machines are both showing "Autoconfiguration Enabled - Yes". I've looked at the Vista firewall, including the advanced settings, and it appears to be allowing ICMPv6 through OK. To make sure, I also tried turning the firewall OFF - no change. Both hosts are getting IPv4 addresses via DHCP from the same device that is doing the RAs. Both hosts can communicate via IPv4. There is no difference in behaviour between wireless and wired. If I manually give an interface on the VM an IPv6 address in 2406:a000:0:100::/64 and a default IPv6 route, I can see the local network and the IPv6 Internet. Other machines on the same link are autoconfiguring themselves.
I.e., everything works. Just not autoconfiguration.
Puzzled I am. The RAs are there, the subnet is a /64, RAs are not being filtered, Vista is apparently set to autoconfigure, other nodes in the same subnet autoconfigure just fine, all seems right with the world... but autoconfiguration on Vista is not happening. What am I missing?
Regards, K.
I have a native Vista box and a Vista VM on a Linux box, and neither of them is autoconfiguring an address. The Linux machines in the same network do autoconfigure, as does a Brother printer. If I snoop the network I see what look like perfectly acceptable RA packets.
radvdump sees this on the interface the VM is bridged on:
interface wlan0
{
AdvSendAdvert on;
# Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump
AdvManagedFlag off;
AdvOtherConfigFlag off;
AdvReachableTime 0;
AdvRetransTimer 0;
AdvCurHopLimit 64;
AdvDefaultLifetime 180;
AdvHomeAgentFlag off;
AdvDefaultPreference medium;
AdvSourceLLAddress on;
prefix 2406:a000:0:100::/64
{
AdvValidLifetime 345600;
AdvPreferredLifetime 172800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
}; # End of interface definition
The Vista on the VM was set up with next to no non-standard config; it's basically "out of the box".
The Vista machines are both showing "Autoconfiguration Enabled - Yes". I've looked at the Vista firewall, including the advanced settings, and it appears to be allowing ICMPv6 through OK. To make sure, I also tried turning the firewall OFF - no change. Both hosts are getting IPv4 addresses via DHCP from the same device that is doing the RAs. Both hosts can communicate via IPv4. There is no difference in behaviour between wireless and wired. If I manually give an interface on the VM an IPv6 address in 2406:a000:0:100::/64 and a default IPv6 route, I can see the local network and the IPv6 Internet. Other machines on the same link are autoconfiguring themselves.
I.e., everything works. Just not autoconfiguration.
Puzzled I am. The RAs are there, the subnet is a /64, RAs are not being filtered, Vista is apparently set to autoconfigure, other nodes in the same subnet autoconfigure just fine, all seems right with the world... but autoconfiguration on Vista is not happening. What am I missing?
Regards, K.
Views: 48
Replies to This Discussion
-
Permalink Reply by Mikael Lind on -
Is there an old IPv6 address on the Vista machine? I have run into issues in Win7 where it won't pick up the RA if it has a deprecated address on the interface. Perhaps there is a similar issue on Vista.
-
-
Permalink Reply by Karl Auer on -
Doesn't seem to be the issue here (though that's a good thing to know about). The interfaces have link-local addresses, and that's it. Teredo and ISATAp are not active ("disconnected").
-
-
Permalink Reply by Mikael Lind on
-
So you are seeing the RA packets on the Vista machine but it isn't picking it up. If it isn't the depricated address bug then I would try simplifying the radvd setup in case there would be something that Vista doesn't like. AdvRouterAddr on perhaps.
-
-
Permalink Reply by Karl Auer on
-
Tried setting AdvRouterAddr to on instead of the default off - sadly no change.
-
-
Permalink Reply by Jeremy Duncan on -
anyway you can post the .pcap file of the RA? There might be something off in there I'd like to see...
-
-
Permalink Reply by Karl Auer on
-
Here ya go. There are a few packets surrounding it that you can ignore. Note that this is with AdvRouterAddr *on*, but it also doesn't work with it off.
- Attachments:
-
-
ra.pcap, 1 KB
-
-
-
Permalink Reply by Jeremy Duncan on
-
Ok first thing I see is the router lifetime needs to be 1800 not 180..
So set this on the interface:
AdvDefaultLifetime 1800; -
-
Permalink Reply by Karl Auer on
-
Why can't the route lifetime be 180 seconds?
The radvd man page says it defaults to 3 times the maximum router advertisement interval, and I am not setting it explicitly. I did set the maximum router advertisementinterval to 60 seconds, hence the the route lifetime of 180 seconds. I'll try it, but don't see an issue here unless Vista is somehow sensitive to legal but lowish values... -
-
Permalink Reply by Karl Auer on
-
Oops, wrong lifetime. But same question - and the same maths. The default for AdvDefaultLifetime is 3 times the maximum router advertisement interval, and I am not setting it explicitly. I did set the maximum router advertisement interval to 60 seconds, hence the the default router lifetime of 180 seconds.
The only limitation according to the man page is that it must be zero OR greater than the maximum router advertisement interval and less than 9000 seconds.
BTW, the radvd I am using doesn't understand AdvRouteLifetime, in spite of it being in the man page :-) -
-
Permalink Reply by Karl Auer on
-
Huh. radvd doesn't like AdvdefaultLifetime either... hm, maybe something else going on.
-
Sponsors
Coming soon...
IPv6 Product Information
IPv6 Resource Center
gogoNET LIVE! 3 Event
Nov. 12-14, 2012, Silicon Valley, USA
© 2012 Created by gogo6.
