4 ms·
And yet almost no server supports ipv6 and almost no consumer isp supports it either.
by tomjen3 11y ago
And yet almost no server supports ipv6 and almost no consumer isp supports it either.
- tzs 11y agoComcast, the largest consumer ISP in the US, supports IPv6 on its entire network, and all current modems they supply have it enabled. There are still customers on older modems, and customers who have brought their own modems that do not support it, so only about 50% of Comcast users are actually running IPv6. Consumer wireless ISPs in the US are also doing pretty good. Verizon has 70% deployment, and AT&T and T-mobile are around 50%.
- scurvy 11y agoThat's simply not true. Over 22% of US Internet consumers have IPv6 addresses. Your mobile phone probably has a (few) IPv6 addresses. From NANOG 64: https://www.youtube.com/watch?v=EfjdOc41g0s https://www.youtube.com/watch?v=EfjdOc41g0s
- ay 11y agoYou can go to http://testipv6.com/ http://testipv6.com/ and check for yourself. Indeed, 1 out of 5 users in USA today has IPv6.
- ersii 11y agoI got IPv6 connectivity on my LTE-services. (Sweden)
- azernik 11y agoMost servers do support IPv6 these days. It's all the networking infrastructure in the middle that's the problem.
- scurvy 11y agoThat's mostly not accurate. Every transit provider offers IPv6 transit. It's not any different or more expensive for them. Routes are routes and datagrams are datagrams to them. The stuff that doesn't support IPv6 is mostly older CPE gear (your old firewall, a bunk load balancer, an oddball console server, etc). You really just need a router that supports IPv6 to offer an IPv6 capable server. Maybe a firewall and loadbalancer if that's in your setup, but those should all support IPv6 already. Things like your access switches and console servers don't require IPv6 addresses yet. You can leave them on IPv4 for now. Your customers aren't going to be accessing them, only you.
- azernik 11y agoAnd yet for some reason most co-lo and VM providers I've seen are still incapable of giving their paying customers routable IPv6 addresses. If, like most people, your servers are sitting in a datacenter, there's going to be a lot of layer-3-aware stuff sitting between you and your users, and empirically it does not support IPv6 end to end.
- scurvy 11y agoThat's just FUD. Pure and simple. There isn't that much that matters. It's jut routers from edge to core to leaf. Your L2 switches don't care about L3 protocols. Some of the worse colo vendors aren't offering it because they're lazy or see increased income from higher v4 rental prices.
- azernik 11y ago> That's just FUD. Pure and simple. ... are you claiming that most co-los, and major VPS providers like AWS, actually do let you use IPv6? Because that's an easily falsifiable claim. Or are you claiming that this is irrelevant and only motivated by a desire to slow IPv6 adoption? Trust me. I've worked on IPv6, I love IPv6, I want it to get out there in the world. > There isn't that much that matters. It's jut routers from edge to core to leaf. Oh, you sweet summer child. The typical hosting setup involves a server behind a NAT on a network that internally looks nice and layered and normal, but that no outsider can get to. When you ask for a public IP address to be assigned to your box, a 1:1 mapping on the NAT box is installed, so that anything directed to "your" public address is mapped to your internal (private) IP. In the middle is a whole host of firewalls (typically IPv4-aware and either not IPv6-capable or not IPv6-configured, since the configuration is a substantial piece of code), VPNs to layer a more customer-friendly network topology on top of the physical one, and on VPS providers a network virtualization layer that is usually not IPv6-ready. > Some of the worse colo vendors aren't offering it because they're lazy or see increased income from higher v4 rental prices. I'm sure they would love to see such increased income. And yet, I've never yet seen a co-lo or VPS provider actually charge anything for IPv4 addresses. If you're going to impute malicious intent to these faceless corporations, you need to at least come up with a realistic motive. Otherwise, the "it's hard and they haven't spent the engineer-days" is a lot more convincing of an argument. Here's a good example that I think shows that this has to do with the inherent difficulty in maintaining two separate layer-3 infrastructures on the same layer-2: Amazon EC2 does not support IPv6. It is impossible to get a public IPv6 address assigned to one, or even to route IPv6 traffic internally between different EC2-internal subnets. However, they've gone to the trouble of making their load-balancer service (ELB) support IPv6 and IPv4, translating TCP, SSL, HTTP, or HTTPS to IPv4 internally. Why would they do such a thing? The rates they charge for an ELB are peanuts; this is not a profit center. This does have the benefit of keeping IPv6 packets out of the internal network, though; that they went through that effort seems to indicate that they consider that problematic.
- solotronics 11y agoTime Warner Cable has implemented IPv6 fully for all residential customers (excluding customer owned modems that do not support IPv6). All new internet circuits for commercial DOCSIS and fiber are built with IPv6 also.
- ay 11y agoIn addition to other answers, here is some food for thought: Some operators are already working on turning IPv4 off in their networks: https://www.youtube.com/watch?v=EfjdOc41g0s https://www.youtube.com/watch?v=EfjdOc41g0s