Recommended Tests

Cox Cable Las Vegas 5/768

C:\Documents and Settings\Owner>tracert -6 www.ipv6.bt.com

Tracing route to www.ipv6.bt.com [2001:618:1:8000::5]
over a maximum of 30 hops:

  1   162 ms   158 ms   159 ms  2001:2b8:2:fffd:0:5efe:203.254.38.129
  2   161 ms   159 ms   161 ms  2001:2b8:2:fff2::1
  3   164 ms   161 ms   164 ms  2001:2b8::1
  4   161 ms   162 ms   171 ms  2001:2b8:0:81::82
  5   470 ms   472 ms   497 ms  kesey.uk6x.com [2001:618:1:8000::5]

Trace complete.

C:\Documents and Settings\Owner>tracert -6 www.deepspace6.net

Tracing route to www.deepspace6.net [2001:1418:13:3::1]
over a maximum of 30 hops:

  1   159 ms   159 ms   159 ms  2001:2b8:2:fffd:0:5efe:203.254.38.129
  2   159 ms   168 ms   163 ms  2001:2b8:2:fff2::1
  3   163 ms   165 ms   163 ms  2001:2b8::1
  4   160 ms   164 ms   174 ms  2001:2b8:5:10::2
  5   160 ms   162 ms   159 ms  2001:220:1000:42e::2
  6   166 ms   172 ms   163 ms  2001:220:1000:400::1
  7   166 ms   168 ms   167 ms  2001:220:c00:200::1
  8   173 ms   169 ms   168 ms  2001:220:1800:200::1
  9   303 ms   304 ms   303 ms  apii-juniper-ge0-1-0-1.jp.apan.net [3ffe:8140:101:1a::162]
 10   675 ms   324 ms   326 ms  tpr4-10gi0-1-0.jp.apan.net [3ffe:8140:101:1e::4]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   317 ms   318 ms   315 ms  2001:200:0:1800::4725:1
 15   319 ms     *      318 ms  2001:278:0:2081::1
 16   317 ms   326 ms   316 ms  2001:278:0:2181::2
 17   654 ms   655 ms   792 ms  2001:1900:5:3::2d
 18   697 ms   689 ms   689 ms  2001:1900:5:2::2e
 19   720 ms   719 ms   715 ms  ils-gw.customer.ipv6.ITgate.net [2001:1418:1:400::6]
 20   734 ms   733 ms   718 ms  cadalboia.ferrara.linux.it [2001:1418:13:3::b01a]
 21   783 ms   743 ms   743 ms  deepspace6.net [2001:1418:13:3::1]

Trace complete.

C:\Documents and Settings\Owner>tracert -6 ipv6gate.sixxs.net

Tracing route to noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c]
over a maximum of 30 hops:

  1   158 ms   159 ms   160 ms  2001:2b8:2:fffd:0:5efe:203.254.38.129
  2   160 ms   163 ms   158 ms  2001:2b8:2:fff2::1
  3   163 ms   163 ms   167 ms  2001:2b8::1
  4   162 ms   162 ms   161 ms  2001:2b8:5:10::2
  5   164 ms   163 ms   162 ms  2001:220:1000:42e::2
  6   164 ms   163 ms   164 ms  2001:220:1000:400::1
  7   171 ms   167 ms   168 ms  2001:220:400:200::1
  8   164 ms   166 ms   165 ms  2001:220:1800:200::1
  9   304 ms   304 ms   337 ms  apii-juniper-ge0-1-0-1.jp.apan.net [3ffe:8140:101:1a::162]
 10   314 ms   334 ms   316 ms  tpr4-10gi0-1-0.jp.apan.net [3ffe:8140:101:1e::4]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   483 ms   507 ms   481 ms  2001:504:1::a500:1273:1
 18   502 ms   491 ms   482 ms  2001:5000:0:2d::1
 19   484 ms   487 ms   484 ms  2001:5000:0:1e::1
 20   485 ms   482 ms   484 ms  2001:5000:0:1d::1
 21   494 ms   507 ms   483 ms  2001:5000:0:20::1
 22   486 ms   487 ms   482 ms  2001:5000:0:21::2
 23   480 ms   484 ms   483 ms  2001:5000:0:12::2
 24   481 ms   481 ms   508 ms  ams-ix.ipv6.concepts.nl [2001:7f8:1::a501:2871:1]
 25   525 ms   485 ms   499 ms  2001:838:0:10::2
 26   484 ms   488 ms   485 ms  2001:838:1:1:210:dcff:fe20:7c7c

Trace complete.

C:\Documents and Settings\Owner>tracert -6 www.vsix.net

Tracing route to www.vsix.net [2001:2b8:1::100]
over a maximum of 30 hops:

  1   163 ms   160 ms   159 ms  2001:2b8:2:fffd:0:5efe:203.254.38.129
  2   163 ms   161 ms   160 ms  2001:2b8:2:fff2::1
  3   165 ms   164 ms   166 ms  2001:2b8::1
  4   163 ms   160 ms   165 ms  2001:2b8:0:160::161
  5   159 ms   158 ms   162 ms  2001:2b8:1::100

Trace complete.

C:\Documents and Settings\Owner>

---

::::::::::.. Download Stats ..::::::::::
Connection is:: 4001 Kbps about 4 Mbps (tested with 2992 kB)
Download Speed is:: 488 kB/s
Tested From:: http://testmy.net/ (server2)
Test Time:: Tue Jan 3 08:50:52 PST 2006
Bottom Line:: 71X faster than 56K 1MB download in 2.1 sec
Diagnosis: 90% + Okay : running at 97.4 % of your hosts average (Cox.net)
Validation Link:: http://testmy.net/stats/id-1DZB8WF56

::::::::::.. Upload Stats ..::::::::::
Connection is:: 737 Kbps about 0.7 Mbps (tested with 579 kB)
Upload Speed is:: 90 kB/s
Tested From:: http://testmy.net/ (server1)
Test Time:: Tue Jan 3 08:52:15 PST 2006
Bottom Line:: 13X faster than 56K 1MB upload in 11.38 sec
Diagnosis: Awesome! 20% + : 33.27 % faster than the average for host (Cox.net)
Validation Link:: http://testmy.net/stats/id-QXEKWDYGN

---

Downstream  Value
Frequency 675000000 Hz   
Signal to Noise Ratio 36 dB 
QAM 256
Network Access Control Object ON
Power Level -3 dBmV 

Upstream  Value
Channel ID 1
Frequency 36400000 Hz 
Ranging Service ID 3682
Symbol Rate 2.560 Msym/s
Power Level 41 dBmV 

Is their a point in using IPv6? Will it make anything any faster? And will Verizon support it? AND the install is all in Japanise or somthing not english.

Yes the site is in Japanise but also a Mix of English
 
As to your post -
Yes IPV6 has features that make it better than Ipv4
It boasts it's technology of long address length by enlarging the existing 32-bit based IPv4 address to almost four times longer(128-bit) and a new suite of standard protocols for the network layer of the Internet and more- to start!


A new protocol :::::::::::::::::::::::::::::::::::::::
As everyone of you knows, TCP/IP is the communication protocol of the Internet. To be precise, TCP/IP is a suite of protocols. The TCP (Transmission Control Protocol) provides a reliable bidirectional connection between two hosts, using the communication facilities provided by the IP (Internet Protocol). In fact, IP is a network layer protocol and its task is to deliver packets of data from a source host to a destination host.

IPv6 is the new version of the Internet Protocol, that is meant to replace IPv4 (which is the version currently in use) in a few years. IPv4 has been used since the Internet was born and has worked very well until now, but it has many serious limits that IPv6 has been designed to overcome. As you may guess, there have been many changes from the definition of the IPv4 protocol to the one of the IPv6 protocol.

First of all, IPv6 provides a larger address space than IPv4. As many of you know, IPv4 supports about 2.000.000.000 addresses. You may think that such a large number of addresses should be more than enough for the actual size of the Internet. This is partly true. In fact, until recent times, IPv4 addresses have only been allocated in blocks of 254, 65534 or 16777214. This has lead to an enormous waste of usable addresses, since many organizations have been forced to ask many more addresses than the ones they really needed. The waste of IPv4 addresses has been of such an order of magnitude that the whole address space will be soon completely exhausted. Now the IETF has developed a wiser address allocation policy: CIDR (Classless Inter-Domain Routing). However, while CIDR has been designed to achieve the minimum waste of the remained IPv4 addresses and to minimize the growth of the routing tables (due to the non-hierarchical organization of the IPv4 address space), it does not solve the problem of the upcoming exhaustion of the IPv4 address space. Here comes IPv6: it provides more than a billion of billions addresses per square meter on the Earth! Besides, IPv6 uses a CIDR-style architecture for address allocation that prevents a big waste of addresses and an uncontrolled growth of the routing tables. So, while CIDR partly addresses the problem, IPv6 represents the long-term solution.

Furthermore, IPv6 has been designed to satisfy the growing need of security experienced by the Internet community. The authentication header mechanism allows the receiver to be reasonably sure about the origin of the data, and the IPSEC privacy facilities provide end-to-end encryption of data at the network layer. IP spoofing attacks and eavesdropping of data will be much more difficult in the Internet of the next millennium. However, as Wietse Venema points out, network-level encryption poses new security problems. In fact decryption puts a considerable overhead on the CPU and this may eventually leave the host more vulnerable to flooding-type DoS attacks. To reduce these risk, a careful implementation of the networking protocols is required.

Moreover, IPv6 has many improvements for mobile networking and real-time communication. In particular, unlike IPv4, IPv6 has robust autoconfiguration capabilities that simplify the system administration of mobile hosts and LANs.

Although IPv6 is superior to IPv4 in everything, it is a common opinion that the transition from IPv4 to IPv6 will be long (perhaps more than a decade) and difficult. In fact, many organizations have made an enourmous investment in IPv4 technology and are not ready nor willing to speed up the transition yet. IPv4 is a well-known, and thoroughly-tested technology; its reliability and its widespread use represent a major slowing-factor in the development of IPv6.

Today, there are only a few working IPv6 implementations.


I see that you are not familiar with it. Hope this helps some......
JW