Link: Test your IPv6.
http://gyazo.com/8c4129caf32f20607fc3763ed1c9bb6b.png
[My public IP address removed]
I have "No problems are anticipated for you with this browser, at this location" [Yippee!]
Printable View
Link: Test your IPv6.
http://gyazo.com/8c4129caf32f20607fc3763ed1c9bb6b.png
[My public IP address removed]
I have "No problems are anticipated for you with this browser, at this location" [Yippee!]
But doesn't it say "You appear to be able to browse the IPv4 internet only. You will not be able to reach IPv6-only site"?
ipv6 checker is a little software that you could find quite useful, it checks for ipv6 readiness, totally free
here's the link ipv6 checker
free
Yes but it is only checking for issues with IP6 day where a bunch of sites will be avalible over both IP4 and IP6. The only way that they would fail is if they are using a hack OS like OSX with a bad IP6 stack and have a badly configured router and non split DNS setup.Quote:
Originally Posted by sparkeh
Basiclly if you are running OSX and have a router like an Airport that sets up an internal IP6 network the OSX system will blindly decide that it has full IP6 connectivity and if the DNS from your ISP is not split to filter out IP6 (AAAA) records OSX will decide that this is the only address and because it has no real IP6 connectivity outside your local network it will fail at trying to get to the site.
This is why most of the ISPs filter out IP6 records so that IP4 clients that wrongly beleive that they have IP6 won't get hung up and fail by trying only the IP6 DNS result. Some of the eairly *nix systems also had this issue but it was cleaned up to a reasonable degree in most distributions.
Windows is actually the best overall at dealing with IP6 as it runs a few more intelligent tests on the network link and also falls back to the IP4 DNS results if required and even Windows XP has IP6 support if you choose to enable it.