|
Vista IPv6 autoconfiguration broke down. any ideas?
![[fi]](/s/countries/fi.gif) Shadow Hawkins on Saturday, 14 November 2009 17:30:29
I have been happily using Vista SP2 with stateless IPv6 autoconfiguration for half a year. Now I suddenly noticed that for the past week or two the PC has not been able to get IPv6 address by autoconfiguration, and IPv6 has been limited to local connectivity.
AICCU tunnel works, if I try to use it.
And I am writing this through IPv6 after entering manually the IPv6 address into Vista network interface settings. So, the IPv6 connectivity seems to work otherwise except the autoconfiguration part.
My DIR-615C provides hardware support for a 6in4 tunnel, so from Vista's perspective the router provides a full IPv6 environment. To my knowledge, there has been no change regarding the router.
When looking to SIXXS logs, I notice that for certainty the autoconfig has worked on October 30, at which point I have updated Sun VirtualBox, updated Java and of course there have been some Windows updates after that.
One symptom is that the IPCONFIG /RENEW6 command takes a long time to run (some timeout period?) and seems to complain about "semaphore timeout" in connection to LAN interface and about some file related to "Loopback Pseudo Interface 1"...
I have tried with antivirus/firewall disabled, but that didn't help.
I have also deinstalled network card and let Vista to recognize it again.
Browsing the net did not provide much help regarding the issue.
Has anybody ran into similar problem?
C:\Users>ipconfig /renew6
Windows IP Configuration
No operation can be performed on aiccu while it has its media disconnected.
An error occurred while renewing interface Local Area Connection : The semaphore
timeout period has expired.
An error occurred while renewing interface Loopback Pseudo-Interface 1 : The sys
tem cannot find the file specified.
No operation can be performed on Local Area Connection* 10 while it has its medi
a disconnected.
Ethernet adapter aiccu:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : pp.htv.fi
IPv6 Address. . . . . . . . . . . : 2001:14b8:xxxxxxxx
Link-local IPv6 Address . . . . . : fe80::a:9c0a:9919:a992%14
IPv4 Address. . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 2001:14b8:xxxxxxxx
192.168.0.1
Vista IPv6 autoconfiguration broke down. any ideas?
Shadow Hawkins on Saturday, 14 November 2009 19:34:05
I seem to have finally fixed it by hard-resetting the router to factory defaults and then re-entering all settings to the router. Now Vista picks up again IPv6 address through stateless autoconfiguration. Looks like it was a "hardware issue" after all.
Vista IPv6 autoconfiguration broke down. any ideas?
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 17 November 2009 17:36:57
Autoconfiguration is enabled by a Router Advertisement daemon which probably runs on your router. I would guess it's in your router as "RA" or "radvd" or perhaps it's nicely hidden behind the configuration settings. It's the part that needs to know what your subnet's /64 prefix is. From a technical point of view it isn't related to aiccu or Vista.
Also, "ipconfig /renew6" is actually for when you have a dhcpv6 server, not for autoconfiguration. Specifically IPv6 autocconfiguration is stateless autoconfiguration and using a dhcpv6 server is stateful autoconfiguration. (OK, so it also is called "autoconfiguration", but usually "autoconfiguration" is synonymous with "stateless autoconfiguration" with RA.)
|
Posting is only allowed when you are