On my Windows 8.1 laptop, i can’t connect to native IPv6 hosts over 6to4. route print -6
shows that no default route is set:
=========================================================================== Interface List 21...02 25 xx xx xx xx ......Karta Microsoft Wi-Fi Direct Virtual Adapter 20...00 25 xx xx xx xx ......Karta Broadcom 802.11n Network Adapter 18...00 25 xx xx xx xx ......Urządzenie Bluetooth (sieć osobista) 17...00 25 xx xx xx xx ......Kontroler sieci NVIDIA nForce 1...........................Software Loopback Interface 1 22...00 00 00 00 00 00 00 e0 Karta tunelowania Teredo firmy Microsoft 23...00 00 00 00 00 00 00 e0 Karta Microsoft ISATAP 24...00 00 00 00 00 00 00 e0 Karta Microsoft 6to4 =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 22 306 2001::/32 On-link 22 306 2001:0:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/128 On-link 24 1010 2002::/16 On-link 24 266 2002:xxxx:xxxx::xxxx:xxxx/128 On-link 17 266 fe80::/64 On-link 22 306 fe80::/64 On-link 22 306 fe80::xxxx:xxxx:xxxx:xxxx/128 On-link 17 266 fe80::xxxx:xxxx:xxxx:xxxx/128 On-link 1 306 ff00::/8 On-link 17 266 ff00::/8 On-link 22 306 ff00::/8 On-link =========================================================================== Persistent Routes: None
I'm aware that i can set the default route manually, but this only works around the problem, which reappears if, for example, the IPv6 stack is reset, which deletes custom routes. On another PC with Vista on it, the 6to4 default route gets set automatically and survives a reset of the IPv6 stack.
What could be causing such behavior?
route print /6
that at first Teredo gets set as the default route, and then as 6to4 gets initialised, it removes the Teredo route but somehow fails to set its own