As most of you probably know, Google and several other websites are switching to IPv6 today and are never returning to IPv4.
Linux and Kubuntu are IPv6 capable using 6to4 tunneling. Teredo automatic tunneling can be had by installing Miredo, a Teredo clone running as a daemon.
Anyway, I decided to test the relative speed of IPv4 vs IPv6 using ping and ping6. Yesterday ping6 would only return results if I pinged the localhost using "ping6 ::1". "ping6 google.com" returned nothing.
Here are the results today.
An IP lookup for Google.com gives:
IP: 74.125.228.9
IP Country: Canada
This IP address resolves to iad23s05-in-f9.1e100.net
which is what is given when I use ping6.
I find it odd that ping6 is resolving to an IPv4 address instead of eight quad digits. aaaa:bbbb:cccc:dddd:eeee:ffff:gggg:hhhh or an abbreviated version of an 8 quad. Tracing doesn't give a hint of IPv6 routing.
Also, it is odd that for 10 pings both returned essential the same time, 9000ms, but the IPv6 packets averaged 2 times longer than IPv4 packets and the deviation was 75 times wider. Somethings wrong with the way IPv6 is collecting, computing or recording its data. When adding up the returns I compute:
ping6 1,055.9
ping 527.7
which shows that IPv4 is twice as fast as IPv6. Yet, by my watch they both took about the same amount of time, ten seconds. IF IPv4 were twice as fast as IPv6 it should have taken only about 5 seconds, or IPv6 should have taken 20 seconds.
Tunneling takes its toll on speed it appears.
My TP-Link 1043DN wireless doesn't support IPv6. I am not sure my TimeWarner modem does either. Looks like I will be looking into buying a wireless router that does and replacing my modem with one that does.
Linux and Kubuntu are IPv6 capable using 6to4 tunneling. Teredo automatic tunneling can be had by installing Miredo, a Teredo clone running as a daemon.
Anyway, I decided to test the relative speed of IPv4 vs IPv6 using ping and ping6. Yesterday ping6 would only return results if I pinged the localhost using "ping6 ::1". "ping6 google.com" returned nothing.
Here are the results today.
Code:
:~$ [B][COLOR=#ff0000]ping6[/COLOR][/B] google.com PING google.com(iad23s08-in-x09.1e100.net) 56 data bytes 64 bytes from iad23s08-in-x09.1e100.net: icmp_seq=1 ttl=59 time=395 ms 64 bytes from iad23s08-in-x09.1e100.net: icmp_seq=2 ttl=59 time=72.6 ms 64 bytes from iad23s08-in-x09.1e100.net: icmp_seq=3 ttl=59 time=73.7 ms 64 bytes from iad23s08-in-x09.1e100.net: icmp_seq=4 ttl=59 time=76.4 ms 64 bytes from iad23s08-in-x09.1e100.net: icmp_seq=5 ttl=59 time=71.0 ms 64 bytes from iad23s08-in-x09.1e100.net: icmp_seq=6 ttl=59 time=74.9 ms 64 bytes from iad23s08-in-x09.1e100.net: icmp_seq=7 ttl=59 time=75.1 ms 64 bytes from iad23s08-in-x09.1e100.net: icmp_seq=8 ttl=59 time=73.5 ms 64 bytes from iad23s08-in-x09.1e100.net: icmp_seq=9 ttl=59 time=73.4 ms ^C64 bytes from iad23s08-in-x09.1e100.net: icmp_seq=10 ttl=59 time=70.3 ms --- google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9002ms rtt min/avg/max/mdev = 70.335/105.650/395.130/96.509 ms :~$ [B]ping[/B] google.com PING google.com (74.125.228.5) 56(84) bytes of data. 64 bytes from iad23s05-in-f5.1e100.net (74.125.228.5): icmp_req=1 ttl=47 time=52.9 ms 64 bytes from iad23s05-in-f5.1e100.net (74.125.228.5): icmp_req=2 ttl=47 time=54.9 ms 64 bytes from iad23s05-in-f5.1e100.net (74.125.228.5): icmp_req=3 ttl=47 time=54.9 ms 64 bytes from iad23s05-in-f5.1e100.net (74.125.228.5): icmp_req=4 ttl=47 time=51.6 ms 64 bytes from iad23s05-in-f5.1e100.net (74.125.228.5): icmp_req=5 ttl=47 time=53.1 ms 64 bytes from iad23s05-in-f5.1e100.net (74.125.228.5): icmp_req=6 ttl=47 time=52.0 ms 64 bytes from iad23s05-in-f5.1e100.net (74.125.228.5): icmp_req=7 ttl=47 time=52.1 ms 64 bytes from iad23s05-in-f5.1e100.net (74.125.228.5): icmp_req=8 ttl=47 time=51.7 ms 64 bytes from iad23s05-in-f5.1e100.net (74.125.228.5): icmp_req=9 ttl=47 time=53.3 ms 64 bytes from iad23s05-in-f5.1e100.net (74.125.228.5): icmp_req=10 ttl=47 time=51.2 ms ^C --- google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9011ms rtt min/avg/max/mdev = 51.250/52.823/54.996/1.269 ms :~$
IP: 74.125.228.9
IP Country: Canada
This IP address resolves to iad23s05-in-f9.1e100.net
which is what is given when I use ping6.
I find it odd that ping6 is resolving to an IPv4 address instead of eight quad digits. aaaa:bbbb:cccc:dddd:eeee:ffff:gggg:hhhh or an abbreviated version of an 8 quad. Tracing doesn't give a hint of IPv6 routing.
Also, it is odd that for 10 pings both returned essential the same time, 9000ms, but the IPv6 packets averaged 2 times longer than IPv4 packets and the deviation was 75 times wider. Somethings wrong with the way IPv6 is collecting, computing or recording its data. When adding up the returns I compute:
ping6 1,055.9
ping 527.7
which shows that IPv4 is twice as fast as IPv6. Yet, by my watch they both took about the same amount of time, ten seconds. IF IPv4 were twice as fast as IPv6 it should have taken only about 5 seconds, or IPv6 should have taken 20 seconds.
Tunneling takes its toll on speed it appears.
My TP-Link 1043DN wireless doesn't support IPv6. I am not sure my TimeWarner modem does either. Looks like I will be looking into buying a wireless router that does and replacing my modem with one that does.
Comment