无色无味(杨波) 的Web Log(博客)

   如果你对你的IPV6速度自信的话，可以看看这个 WebCam。  实时的。

     DNS Server是否拥有IPV6地址，NS name是否做了V6解析对域名的IPV6解析有着绝对性的影响。

    我拥有几个域名。   也通过Tunnel的方式接入了IPV6。同时也对域名进行了Ipv6和IPv4的解析设置。但是通过普通PC无法解析出来IPV6的地址。

Read entire article.

    经过一段时间的摸索。终于把基于Windows Server +DNs server 的 IPV6 Rdns搭建起来了。

C:\>tracert -6 vs1.ghitr.com

Tracing route to vs1.ghitr.com [2001:470:1f05:819::2]
over a maximum of 30 hops:

  1   311 ms   325 ms   301 ms  2001:5c0:1000:b::5786
  2   411 ms   403 ms   399 ms  ix-0-0.224.mcore4.MTT-Montreal.ipv6.as6453.net [2001:5a0:300::5]
  3   597 ms   479 ms   795 ms  if-12-3.mcore3.MTT-Montreal.ipv6.as6453.net [2001:5a0:300:100::21]
  4   421 ms   739 ms   377 ms  POS13-0.mcore4.NYY-NewYork.ipv6.as6453.net [2001:5a0:300:100::2]
  5   615 ms   643 ms   603 ms  POS5-0.mcore4.NJY-Newark.ipv6.as6453.net [2001:5a0:f00:100::1]
  6   604 ms   585 ms   331 ms  10gigabitethernet4-2.core1.nyc4.he.net [2001:504:0:6::6939:1]
  7   384 ms   399 ms   377 ms  10gigabitethernet5-3.core1.lax1.he.net [2001:470:0:10e::1]
  8   565 ms   763 ms   679 ms  10gigabitethernet1-3.core1.pao1.ipv6.he.net [2001:470:0:34::1]
  9   613 ms   553 ms   389 ms  10gigabitethernet1-4.core1.fmt2.ipv6.he.net [2001:470:0:30::1]
10   390 ms   392 ms   405 ms  gige-gbge0.tserv3.fmt2.ipv6.he.net [2001:470:0:45::2]
11   606 ms   783 ms   577 ms  yangybcy-1-pt.tunnel.tserv3.fmt2.ipv6.he.net [2001:470:1f04:819::2]
12   588 ms   609 ms   605 ms  ipv6.server.ghitr.com [2001:470:1f05:819::2]

Trace complete.

    IPv6 or IP version 6 is the next generation Internet protocol which will eventually replace the current protocol IPv4. IPv6 has a number of improvements and simplifications when compared to IPv4. The primary difference is that IPv6 uses 128 bit addresses as compared to the 32 bit addresses used with IPv4. This means that there are more available IP addresses using IPv6 than are available with IPv4 alone. For a very clear comparison, in IPv4 there is a total of 4,294,967,296 IP addresses. With IPv6, there is a total of 18,446,744,073,709,551,616 IP addresses in a single /64 allocation.

    To also help illustrate the sheer magnitude of available IP addresses using IPv6, you can get 65536 /64 allocations out of a single /48, and then 65536 /48 allocations out of a single /32. Many Service Providers are getting /32 allocations from their Regional Internet Registry (RIR) like ARIN, APNIC, RIPE, etc.

    A significant difference between IPv6 and IPv4 is the address notation. IPv4 uses a period (.) between each octet, compared to IPv6 which uses a colon (:). With IPv6, if you have a series of zeroes in a row, the address need not be written out completely. You can use a double colon (::) to represent that series of zeroes, however you can only use that once. For example, if you have an address like “2001:0DB8:0000:0003:0000:01FF:0000:002E”, it can be written like “2001:DB8::3:0:1FF:0:2E” or “2001:DB8:0:3:0:1FF::2E”, but would never be written like “2001:DB8::3::1ff::2E”. You also cannot have three colons in a row (:::).

    IPv6 availability depends on your Service Provider, either at home or for work. In a dual-stack environment, IPv4 and IPv6 co-exist along the same connection and don’t require any special kind of connection. If dual-stack is not available, you might find yourself using an IP tunneling product or service to bring IPv6 connectivity to you. IPv4 exhaustion, as of this writing, is estimated to happen sometime in early or mid 2011. When this happens, IPv4 won’t simply disappear off the face of the Internet, but continued explosive growth requiring more unique IP address assignments will mean using more and more of the abundant IPv6 address space.

    Many Operating System platforms have native IPv6 support these days. The UNIX based platforms like Linux, BSD (Free, Open, Net) & MacOSX have had IPv6 support enabled for years now. Microsoft Windows starting having native IPv6 support enabled by default with it’s Vista and Windows 2008 products. Earlier Windows versions like 2000/2003/XP had to have it installed optionally, and did not have as robust features that are available in the newer versions of Windows. Even common web browsing and email software will use IPv6 if it is enabled and available, without having to check off an option or special configuration. The transition from IPv4 to IPv6 is being worked on to be as seemless as possible, and many might not even notice the subtle changes in the coming years.

    昨晚一朋友询问怎样配置IPV6在Cisco的路由器上。   他的平台是Cisco 3640+Gns3+Windows7。后来讨论发现GNS3在Windows7上面好像不能对本机的网络链接进行操作。

    大家都知道IPV6的地址是a long a long的。如果让每个用户都去手工配置地址。那肯定是一件很大的灾难。那么肯定还是自动配置是最方便的。

    IPV6的自动配置又分成两种方式：1.DHCPv6             2.IPV6的无状态自动配置。

    当让IPV6的无状态自动配置是最简单的。所以先看一下无状态自动配置。

Read entire article.

为什么我们中国的网络发展总是那么的滞后呢？

为什么我们国家的CNNIC总在叫着要加快IPV6的步伐！ 可是却没有任何进展？？

我们也不去报怨了。   现在让我们的家庭也接入IPV6吧。（不是指某一台机器哟）

要想让你的家庭也接入IPV6网络。肯定得有一段地址吧！    这个简单   申请吧！ （是不是在想我去哪儿申请呢？ ）   

去国外申请。 为什么要去国外。  因为国外拥有大量的IPV6地址。人家的地址段可以约等于我们的地址位。

Read entire article.

最近在调试OpenVPN IPV6，发觉这个有用的资料。特收集到这里。

Copyright © 2004 by Christian Strauf

Acknowledgements go to people from the University of Erlangen for inspiring us with the idea to use OpenVPN for a tunnel broker service. Thank you, guys, it works like a charm!

Table of Contents:

1. Introduction
2. Definition of the term "tunnel broker"
3. Tunnel broker clients
4. Installation of tunnel broker components
   1. Installation of OpenSSL CA
      • Creating an openssl.cnf
      • Creating keys and certificates for your CA
   2. Installation of OpenVPN server
   3. Installation of user database
5. Functionality of tunnel broker and its components
   1. OpenSSL CA
   2. OpenVPN server
6. Routing configuration
7. Sample server configuration
8. Sample subnet client configuration
9. Management (and download of JOIN tunnel broker scripts)
10. Client user guide
11. Appendix

Read entire article.