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

   因为最近服务器调整。换了一个联网的虚拟空间。而服务器还没有iPV6地址。所以博客就暂时不支持IPV6了。

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

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

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

Read entire article.

现在很多大学校都已经实现了IPV6的覆盖。

今天在西南大学调试一批设备的时候。顺便看了一下IPV6的覆盖情况。

XP下安装IPV6：

在命令提示符状态下面输入：

netsh int ipv6 install

IPV6的安装就完成了。

如果校园实现了IPV6的覆盖。那么系统会自动获得一下IPV6地址。

C:\>ipconfig

Windows IP Configuration
Ethernet adapter 本地连接:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 172.18.2.152
        Subnet Mask . . . . . . . . . . . : 255.255.255.128
        IP Address. . . . . . . . . . . . : 2001:da8:c803:1406:8107:345c:1267:d0f
        IP Address. . . . . . . . . . . . : 2001:da8:c803:1406:92fb:a6ff:fe16:d14d
        IP Address. . . . . . . . . . . . : fe80::92fb:a6ff:fe16:d14d%5
        Default Gateway . . . . . . . . . : 172.18.2.129
                                            fe80::219:6ff:fe56:1e4a%5

一般IPV6地址都是自动获得，手工配置太麻烦。

通过netsh int ipv6 show route

netsh interface ipv6>show route
正在查询活动状态…

发行     类型      Met   前缀                     索引  网关/接口名
——-  ——–  —-  ————————  —  ———————
no       Autoconf     8  2001:da8:c803:1406::/64     5  本地连接
no       Autoconf   256  ::/0                        5  fe80::219:6ff:fe56:1e4a

可以查看该机现在的IPV6路由表。下面的tracert情况是为了验证路由。

C:\>tracert blog.ghitr.com

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

  1    <1 ms     2 ms    <1 ms  cernet2.net [2001:da8:c803:1406::1]
  2    <1 ms    <1 ms    <1 ms  cernet2.net [2001:da8:c803:ffff:ffff:ffff:ffff:1
069]
  3    <1 ms    <1 ms    <1 ms  cernet2.net [2001:da8:c803:ffff:ffff:ffff:ffff:1
002]
  4     1 ms     1 ms     1 ms  cernet2.net [2001:da8:c803:84::1]
  5     4 ms     5 ms    10 ms  cernet2.net [2001:da8:b1:1000::1]
  6     2 ms     2 ms     2 ms  cernet2.net [2001:da8:b1:f::2]
  7     1 ms     1 ms     1 ms  2001:da8:1:212::1
  8    15 ms     *       14 ms  wh-chq-v6.cernet2.net [2001:da8:1:c::1]
  9    51 ms     *        *     bj-wh-v6.cernet2.net [2001:da8:1:1::1]
 10    58 ms    55 ms    56 ms  2001:252:0:1::101
 11    87 ms     *       83 ms  2001:252:0:101::2
 12    88 ms    89 ms    89 ms  hurricaneelectric-RGE.hkix.net [2001:7fa:0:1::ca
28:a19e]
 13   315 ms   319 ms     *     v1026.core1.sjc1.he.net [2001:470:0:c3::1]
 14   330 ms   322 ms   322 ms  10gigabitethernet2-1.core1.sjc2.ipv6.he.net [200
1:470:0:55::2]
 15     *      319 ms   326 ms  10gigabitethernet1-2.core1.fmt2.ipv6.he.net [200
1:470:0:31::1]
 16   324 ms   322 ms   322 ms  gige-gbge0.tserv3.fmt2.ipv6.he.net [2001:470:0:4
5::2]
 17   609 ms   611 ms   609 ms  yangybcy-1-pt.tunnel.tserv3.fmt2.ipv6.he.net [20
01:470:1f04:819::2]
 18   610 ms   612 ms   613 ms  ipv6.server.ghitr.com [2001:470:1f05:819::2]

Trace complete.

C:\>
C:\>

以上的全是些废话。写得耍的。

    经过一段时间的摸索。终于把基于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.

    鉴于近段时间我的个人时间越来越混乱。以后工作的重心也在不停的调整中……，所以特调整个人生活学习时间。

1.个人博客(http://blog.ghitr.com)还是照常写。

2.个人网站(http://www.ghitr.com)准备跳转到我的个人博客。

3.女性生活网(http://www.5hml.com) 准备放缓更新进度。这个不在做为个人学习工作的重点。

4.下一代互联网（Http://www.usengi.com)这个网站暂停更新或者跳转到个人博客。  准备压缩这个网站的方向。目前仅作为个人在工作、学习中有关IPV6的相关资料的更新。  如果有哪位朋友愿意更新、维护IPV6、拓展IPV6应用、加固IPV6在中国的应用等相关意愿可以与我一起学习IPV6.

个人学习调整：

    个人学习方向调整至系统方面，不再注重网络的简单应用。

系统方面：主要以Linux为主。windows仅限于客户端。将不再重点学习Microsoft Windows Server的应用。

简单的综述就是 更多的关注 Linux 系统和网络应用、     关注IPv6的普及。

最近在调试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.

今天突然发现我家里的IPV6不能用了。   平时都是通过Teredo上的IPV6.     当发现不能使用后，使用netsh interface ipv6 show teredo.系统提示不能访问此地址。

Read entire article.