-1

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?

Improve this question
14
  • Probably because using 6to4 is being deprecated
    – Sander Steffann
    Oct 31, 2014 at 15:40
  • @SanderSteffann How? Native IPv6 users are a minority still. And 6to4 actually works where i live.
    – kinokijuf
    Oct 31, 2014 at 15:55
  • @SanderSteffann This is definitely not the expected behavior. I noticed by repeatedly running 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
    – kinokijuf
    Oct 31, 2014 at 16:03
  • 1
    Besides, the low reliability of 6to4 depends on the 6to4 relay closest to you and also on the 6to4 relay closest to the native IPv6 system you are talking to. Even if the relay you use is good the other relay might still be bad. It is therefore usually better to use a managed tunnel (SixXS, HE/tunnelbroker.net) then you can't get native IPv6 so you know who is managing the devices for your IPv6 connectivity.
    – Sander Steffann
    Oct 31, 2014 at 17:32
  • 1
    You are still well advised to dump 6to4 and use a tunnel. Even if 6to4 works today, it will not do in the very near future.
    – Michael Hampton
    Nov 1, 2014 at 20:13

1 Answer 1

Reset to default
0

NOTE: As of December 2014, UPC now directs 192.88.99.1 to Hurricane Electric, so the problem no longer appears for UPC users.

The 6to4 anycast relay i get (port80.se) unfortunately has a misconfigured or overzealous firewall.

Windows 8.1 tests 6to4 relay availability by trying to ping [2002:c058:6301::c058:6301] with TTL set to 1 and expecting to get either a response or a TTL exceeded error, only then enabling a default route to 6to4.

I have emailed the server admins at port80 and will update if i get any response back.

The workarounds include setting a default route manually, or choosing a non-anycast relay.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .