Slashdot Mirror
Google Over IPv6 Coming Soon
fuzzel writes "Today Google announced Google over IPv6 where ISPs can sign up their DNS nameservers so that their users will get access to an almost fully IPv6-enabled Google, including http://www.google.com, images and maps, etc., just like in IPv4. Without this only http://ipv6.google.com is available, but then you go to IPv4 for most services.
So, start kicking your ISPs to support IPv6 too, and let them sign up.
Check this list of ISPs that already do native IPv6 to your doorstep.
The question that now remains is: when will Slashdot follow?"
One BIG carrot for Universities and Labs that use google (gmail, docs, etc) is that this means that all that google traffic can be routed over their Internet2 connections which are MUCH faster and of lower latency than their commercial internet connections.
As an IPv6 user, I would LOVE to use google over IPv6.
I smell the hand of Vint Cerf at google...
.. that for quick and dirty use the numeric address are just too complicated. Sure it has benefits wrt security, routing and a load of other behind the scenes stuff. But for people who are used to using numeric ip4 addresses when DNS is slow or for testing purpose or setting up various IP tables or 101 miscellanious things , ip6 is a royal PITA.
Ok , thats hardly a reason for not using it but I suspect its perhaps one reason why people are relunctant to try it. Half a line of hex is not user friendly.
Maybe you should read the summary again.
I hoped that Linksys, et.al., would intro consumer routers at CES2009 with IPv6/IPv4 dual stacks.
As I wrote elsewhere, you can get IPv6 on Linksys (et al.) routers at present as well, but you have to use custom firmware, meaning OpenWRT or DD-WRT.
Unfortunately this means that it can be quite difficult to configure. OpenWRT is not really suitable for non-technical users anyway, so for their userbase it won't be much of a problem. For DD-WRT, IPv6 was supported quite well in v23, but has been having problems for some years in v24 out of the box. If you want IPv6 in recent DD-WRT versions (v24 or higher), you need some manual configuration as well as a custom build, but then it's possible.
This arguably doesn't really qualify as a consumer solution, though.
As a state gets corrupt, its laws multiply; the most corrupt states have the most numerous laws. (Tacitus, Annales 3:27)
It is tiny and that sucks.
You can, unless you're using an ISP that specifically blocks it, use IPv6 now however. Either use 6to4 (if you've rolled your own router, then check the web for implementation specifics - start here if you can't find a better page. Another possibility are the Apple Airport routers, that generally have this built in. But before spending time on 6to4, ensure your ISP doesn't block it by ensuring you can ping 192.88.99.1. If you can, go right ahead), or use a Tunnel Broker. Hurricane Electric is a good example.
If you can't ping 192.88.99.1, please let your ISP know.
You are not alone. This is not normal. None of this is normal.
The Internet Stream Protocol (RFC 1819) used 5 in the protocol version field.
upon the advice of my lawyer, i have no sig at this time
I'm not sure that I even want all my machines to have globally routable IPs.
NAT != security
NAT doesn't provide security, it happens to disallow uninitiated inbound connections since it doesn't know where to send them, but so does any good firewall.
From Google:
To qualify for Google over IPv6, your network must have good IPv6 connectivity to Google. Multiple direct interconnections are preferred, but a direct peering with multiple backup routes through transit or multiple reliable transit connections may be acceptable. Your network must provide and support production-quality IPv6 networking and provide access to a substantial number of IPv6 users. Additionally, because IPv6 problems with users' connections can cause users to become unable to access Google if Google over IPv6 is enabled, we expect you to troubleshoot any IPv6 connection problems that arise in your or your users' networks.
Simply said, some networks may have borked IPv6 which would mean that users will be unable to access Google. I can understand that they're doing this before rolling it out to everyone. Maybe there could be something like OpenDNS for IPv6 so that more advanced users have a choice?
If this is too full of 'technical jargon' for you, here are some definition:
A subnet is a part of a larger network (borrowing some conventions from set theory, the whole network is also sometimes called a subnet, just to be confusing). IP addresses are a string of bits, 32 with v4 and 128 with v6. For routing purposes, each subnet is identified by a subnet mask. The first n bits of an IP address identify the subnet and the last 32-n or 128-n identify the machine on that subnet. When you see something like 10/8, this means the subnet that starts 10.x.y.z, where the first 8 bits identify the subnet. Sometimes the subnet doesn't fit on a byte boundary. The medium-sized private address range is 172.16.0.0/12. In hex, this is AC100000 - the AC1 is the subnet, and all of the zeros ignored until the packet is on the subnet.
Subnets can be hierarchical. For example the 10/8 subnet might be used by a big site with the 10.1/16 subnet used by one building, 10.2/16 by another, and so on. The first building might use 10.1.1/24 for one floor, 10.1.2/24 for the next floor, and so on. When you send a packet from the second building to 10.1.1.12 it will be routed to the 10.1/16 subnet, then to the 10.1.1/24 subnet, and then delivered within this subnet by ethernet (the router will use ARP to look up the MAC address that corresponds to that IP address and the ethernet switches will handle delivery on the last segment).
Bak to your question, you can use a publicly-routable address on a LAN, using v4 or v6. This doesn't mean that data will go over the Internet. If both machines are on the same subnet then packets will never make it to the router, they will be delivered by the local ethernet (or whatever) directly. IP routing is only needed when packets go outside the local subnet.
In summary, yes it's a ridiculously simple question, it's only the answer which is complicated...
I am TheRaven on Soylent News
Comcast isn't able to support IPv6 at the CPE until DOCSIS 3.X is rolled out, which is currently in progress. Once people have IPv6-capable CPE/DOCSIS, they could use either stack (or Comcast could just give them IPv6 and tunnel the IPv4 back).
Why only respond to an AAAA DNS request if it comes from a DNS resolver whose IPv4 address is on a whitelist? Surely it would make sense to allow any connection capable to IPv6 to make use of it.
Some clients may erroneously think they have working IPv6, get an AAAA address and timeout trying to use it before falling back to IPv4. This really annoys users. It wouldn't be Google's fault that this happens, but their sites would be perceived as very slow and they'd lose users.
I am lucky in that my ISP is on the list of those providing IPv6, but I use my own DNS resolver which will not be on the Google whitelist.
It is not clear to me exactly what they're doing. They might be whitelisting networks and not individual resolvers. If so then your home resolver may work when your ISP signs up with them.