US IPv6 Usage Grows To 3 Million Users 155
darthcamaro writes "There is a myth that IPv6 is only for those in Asia, but that's not true. According to new data discussed this week at an IETF conference, there are more IPv6 users in the U.S. than anywhere else in the world — coming in at 3 million. From the article: 'George Michaelson, senior R&D scientist at APNIC (Asia Pacific Network Information Centre) has a reasonable idea of what the current levels are globally for IPv6 adoption, thanks to some statistical research he has been doing. In his view, IPv6 is now a reality in terms of adoption. "I think you're used to us standing up and saying 'woe is me, woe is me, v6 isn't happening,'" George Michaelson, senior R&D scientist at APNIC (Asia Pacific Network Information Centre) said. "But it is actually happening, these are not trivial numbers of people that are now using IPv6 on a routine basis."'"
Re:IPV6 on AT&T Residential DSL (Score:5, Informative)
Why do you need to remember it at all? I certainly don't have any of my IP addresses memorized. When I need it, I usually end up cutting and pasting.
The whole point of this DNS thing is that you're not supposed to need to IP address day-to-day. Anything else is sloppy administration.
Verizon 4G (Score:5, Informative)
We had to upgrade one of the software packages we use solely because it logs IP addresses of web site visitors and it was crashing every time someone visited from a Verizon 4G smartphone.
Re:IPV6 on AT&T Residential DSL (Score:2, Informative)
I suspect you're just seeing a link local address, like fe80::f6ce:46ff:fe30:12c5. This isn't routable. It's much like a 169.254.x.x link local address. You can talk to other nodes on your wireless, but nothing beyond a router.
Most likely you will have to replace your CPE device(s). Your DSL modem and/or your router (if they're two different devices) will have to be replaced as the manufacturer doesn't support it anymore and won't release an update to add IPv6 support.
This is the case for Comcast - you have to replace your cablemodem. If you have a router (and you should), you'll most likely have to replace it as well.
Hardware vendors should be massively promoting IPv6 as it means more sales.
Re:IPV6 on AT&T Residential DSL (Score:3, Informative)
Re:Yet Slashdot remains IPv6 Free (Score:2, Informative)
Nortel is bankrupt, Juniper is juniper.net (with IPv6 support), and ipv6.alcatel-lucent.com works, although not ipv6 for www.alcatel-lucent.com
Nearly every phone (Score:4, Informative)
Re:IPV6 on AT&T Residential DSL (Score:5, Informative)
Why don't you have the IP entered in your connection bookmark? Both puTTY and SecurCRT store connection profiles, where you can put the IP instead of hostname for critical servers.
Bash has aliases and shell scripts to call ssh. Even windows CLI has batch scripts.
If "ssh ns1" doesn't resolve, I can run "~/.ssh/ns1.sh" easily enough, which contains the "ssh <ip>" command.
Also if your DNS regularly goes down, I'd guess remembering addresses is the least of your network troubles.
You can already use the alias fe80::%eth0 for your gateway. Best part is you only need to remember that single address, unlike IPv4 which requires me remembering many different "x.x.x.1" addresses used as the gateways right now.
You can even organize it identically to your IPv4 layout. You still only need to really remember 1-2 numbers that will change depending if you use a /24 or /16, and a single prefix that never changes. /16 is already going to have the entire thing documented in a management system or at worse a wiki. Excel will not cut it at that size. /12 or larger network, you already have software that manages the addresses for you. Nothing will change there with IPv6.
Anyone managing larger than a
Basically put, if you have an IPv4
At home I have a /24. That means 3 octets are assigned and fixed already. Gives 253 usable addresses. Most of your IPv6 address will also be assigned.
Instead of x.x.x.1 you have yyyy::1
Instead of x.x.x.10 you have yyyy::10
Instead of x.x.x.100 you have yyyy::100
See the pattern here?
You can even avoid using the hex digits A-F and stick to 0-9 only.
Sure, per "group" you only get 9999 IPs instead of 65534 IPs, but either is better than 253 or less.
At work I manage a /16. That means 2 octets are fixed. I grouped that into 255 blocks of roughly 253 addresses each. Each block is a logical division.
x.x.0.y is routers/switches. x.x.1.y is servers. x.x.4.y are static IPs, and x.x.5.y are dynamic ones.
Instead, you can use yyyy::1:z and yyyy::2:z and so on. .
The best part, my IPv4 and IPv6 suffixes pretty much match for my "dot zero" infrastructure and "dot one" servers blocks. Learning the IPv6 prefix took no longer than remembering a brand new /28 allocated from an ISP.
Your fixed prefix will likely be 8 hex characters. Even a chimp can memorize 8 hex numbers they work with every day :P
The absolute worst situation is going to be having a post-it note in your wallet/purse with the prefixes on it... Pretty much what most of us network admins do anyway for any IPs assigned by upstream providers or other 3rd parties.
I have my entire internal /16 memorized fully. It's the 10ish tiny /29 and smaller blocks from my 4 ISPs that are the bitch to remember! Growing my internal IP blocks with IPv6 took literally less than one full day to memorize the prefix. Just because I waste most of my /64 allocation by padding it with zeros on the left doesn't matter now.
Once I get more than 20k network devices, they will be added slowly over time just like right now. You only have to learn new subnets individually as you add them in at the time they are created, and IPv6 will not change that.