Here Comes IPv6... Guess Who is Not Ready
In about 100 days, the United States Federal Government will be required to be running large portions of their systems on IPv6. Now, for the few non-technical in the crowd, it means that the address your PC uses to connect to the Internet, in most cases, is IPv4. Version 4 has been around almost since most of you started networking your machines to the Internet (it was around in the early '90s when I started doing all of this). IP version 6, which debuted in 1995 was designed to "fix" some of the things that were broken in IPv4, such as the limited address space (it may surprise you but there are only so many addresses in IPv4 that can be allocated). IPv6 increases the address space to some ridiculous number like 1000 per cubic meter of the Earth - in other words A LOT!.
So, as part of my testing, I figured I would call my ISP and request a block. Might as well get while the getting is good right?
So, here is some of my chat with my ISP (try not to laugh):
Me: I want a block of IPv6 addresses. How do I request them?
ISP: As I understand, you wish to block the IP Address of any Domain name. Am I correct?
Me: Negative. I want to request a block (say a /48) of IPv6 addresses.
As you can see, we are off to a roaring start.
But it gets better:
ISP: I apologize for the inconvenience caused to you. I am not getting your concern correctly, could you please elaborate your concern once again for me?
Me: I would like to request a block of IPv6 addresses for use on my home network. How do I do that?
ISP: Alright. As I understand, you wish to block of General Unicast IPv6 addresses for your Home Network. Am I correct?
ISP: I would love to assist you however we have a different department...
So, I call the department and they do not even know what I am talking about until they find a supervisor who tells them that the "service" is not supported.
Tell me again why the Fed is pushing to convert?
Now, how do I apply for an IPv6 address block?
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Three More Lessons
- Django Models and Migrations
- August 2015 Issue of Linux Journal: Programming
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- Huge Package Overhaul for Debian and Ubuntu
- Hacking a Safe with Bash
- Purism Librem 13 Review
- diff -u: What's New in Kernel Development