DontAskJusTckle
Guest
- Joined
- Nov 2, 2010
- Messages
- 3,981
- Points
- 0
Seeing how the TMF is an Internet forum, I thought that perhaps some of you might be interested in this big change that has actually already begun as of June of last year. Of course I'm talking about the change from IPv4 to IPv6.
What the hell are you talking about, DAJT?
Every device that sits on the public Internet has a unique IP address. This is a 32-bit string that routers use to indentify the source and destination of Internet traffic. If you ever want to know your own IP address, open a "Command Prompt" (Start/All Programs/Accessories/Command Prompt). In the little black window type the word ipconfig and hit enter.
My IP address is 192.168.1.101. But this is not a public address. It's a private address, used only between my cable modem and the computers in my house. The cable modem has a public IP address with which it interfaces the Internet. (see attachment)
If you want to know the IP address of a web page, simply ping that website in your Command Prompt window.
So far these IP addresses we're seeing are all IPv4 addresses. They are represented here in "dotted decimal notation" for the benefit of us average humans who deal with base 10 quicker and easier than base 2. For example, the Fox News IP address 208.47.254.56 really looks like this:
So basically, this is what an IPv4 address looks like. Four bytes, or 32 bits. This is how virtually every packet has been sent over the internet since its inception. It's been a great system...
...But, we now have a problem, Houston. There are only so many IP addresses conceivable. Roughly 4.3 billion. That may sound like a lot, but believe it or not we are running out, and the pool of available IPv4 addresses is quickly running dry! This has been coming for years, and there have been many band-aids to temporarily hold off the inevitable, like subnetting, Network Address Translation, Private IP space, etc.
But finally, a more permanent solution has arrived.
Enter IPv6! It works pretty much the same as IPv4 except for a few key differences, the most significant of which is the address size. IPv6 addresses are 128 bits (16 bytes) which gives us a pool of about 3.4 x 10<sup>38</sup>. About one IP address for every 15 sq feet on the planet.
Now let's see what happens if we ping Google!
That is what an IPv6 address looks like. Notice the address is no longer displayed in dotted decimal, but rather hexidecimal. Eventually, IPv4 will be phased out, and all IP addresses will look more or less like what we see from Google.
There's a lot more we could talk about. I'm sure many are already aware of the change to IPv6, but I thought a simple presentation like this might be beneficial for some.
What the hell are you talking about, DAJT?
Every device that sits on the public Internet has a unique IP address. This is a 32-bit string that routers use to indentify the source and destination of Internet traffic. If you ever want to know your own IP address, open a "Command Prompt" (Start/All Programs/Accessories/Command Prompt). In the little black window type the word ipconfig and hit enter.
C:\Users\dajt>ipconfig
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : dajt.cox.com
IPv4 Address. . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : dajt.cox.com
IPv4 Address. . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
My IP address is 192.168.1.101. But this is not a public address. It's a private address, used only between my cable modem and the computers in my house. The cable modem has a public IP address with which it interfaces the Internet. (see attachment)
If you want to know the IP address of a web page, simply ping that website in your Command Prompt window.
C:\Users\dajt>ping www.foxnews.com
Pinging a20.gakamai.net [208.47.254.56] with 32 bytes of data
Reply from 208.47.254.56: bytes=32 time=13ms TTL=49
Reply from 208.47.254.56: bytes=32 time=13ms TTL=49
Reply from 208.47.254.56: bytes=32 time=14ms TTL=49
Reply from 208.47.254.56: bytes=32 time=12ms TTL=49
Ping statistics for 208.47.254.56:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip time in milli-seconds:
Minimum = 12ms, Maximum = 14ms, Average = 13ms
Pinging a20.gakamai.net [208.47.254.56] with 32 bytes of data
Reply from 208.47.254.56: bytes=32 time=13ms TTL=49
Reply from 208.47.254.56: bytes=32 time=13ms TTL=49
Reply from 208.47.254.56: bytes=32 time=14ms TTL=49
Reply from 208.47.254.56: bytes=32 time=12ms TTL=49
Ping statistics for 208.47.254.56:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip time in milli-seconds:
Minimum = 12ms, Maximum = 14ms, Average = 13ms
So far these IP addresses we're seeing are all IPv4 addresses. They are represented here in "dotted decimal notation" for the benefit of us average humans who deal with base 10 quicker and easier than base 2. For example, the Fox News IP address 208.47.254.56 really looks like this:
11010000.00101111.11111110.00111000
So basically, this is what an IPv4 address looks like. Four bytes, or 32 bits. This is how virtually every packet has been sent over the internet since its inception. It's been a great system...
...But, we now have a problem, Houston. There are only so many IP addresses conceivable. Roughly 4.3 billion. That may sound like a lot, but believe it or not we are running out, and the pool of available IPv4 addresses is quickly running dry! This has been coming for years, and there have been many band-aids to temporarily hold off the inevitable, like subnetting, Network Address Translation, Private IP space, etc.
But finally, a more permanent solution has arrived.
Enter IPv6! It works pretty much the same as IPv4 except for a few key differences, the most significant of which is the address size. IPv6 addresses are 128 bits (16 bytes) which gives us a pool of about 3.4 x 10<sup>38</sup>. About one IP address for every 15 sq feet on the planet.
Now let's see what happens if we ping Google!
C:\Users\dajt>ping www.google.com
Pinging www.google.com [2404:6800:4003:801::1014] with 32 bytes of data:
Reply from 2404:6800:4003:801::1014: time=268ms
Reply from 2404:6800:4003:801::1014: time=265ms
Reply from 2404:6800:4003:801::1014: time=264ms
Reply from 2404:6800:4003:801::1014: time=266ms
Ping statistics for 2404:6800:4003:801::1014:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 264ms, Maximum = 268ms, Average = 265ms
Pinging www.google.com [2404:6800:4003:801::1014] with 32 bytes of data:
Reply from 2404:6800:4003:801::1014: time=268ms
Reply from 2404:6800:4003:801::1014: time=265ms
Reply from 2404:6800:4003:801::1014: time=264ms
Reply from 2404:6800:4003:801::1014: time=266ms
Ping statistics for 2404:6800:4003:801::1014:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 264ms, Maximum = 268ms, Average = 265ms
That is what an IPv6 address looks like. Notice the address is no longer displayed in dotted decimal, but rather hexidecimal. Eventually, IPv4 will be phased out, and all IP addresses will look more or less like what we see from Google.
There's a lot more we could talk about. I'm sure many are already aware of the change to IPv6, but I thought a simple presentation like this might be beneficial for some.