<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IPCPU——网络之路 &#187; IPv4</title>
	<atom:link href="http://www.ipcpu.com/tag/ipv4/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ipcpu.com</link>
	<description></description>
	<lastBuildDate>Sat, 03 Dec 2011 17:16:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>IPv4和IPv6同时存在时，那个协议会优先呢？</title>
		<link>http://www.ipcpu.com/2010/11/ipv6-ipv6-who/</link>
		<comments>http://www.ipcpu.com/2010/11/ipv6-ipv6-who/#comments</comments>
		<pubDate>Sat, 20 Nov 2010 15:45:50 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[网络技术]]></category>
		<category><![CDATA[IPv4]]></category>
		<category><![CDATA[ipv6]]></category>
		<category><![CDATA[协议]]></category>
		<category><![CDATA[实验]]></category>
		<category><![CDATA[网络]]></category>

		<guid isPermaLink="false">http://www.ipcpu.com/?p=853</guid>
		<description><![CDATA[今天爆发了，写第三篇文章了，(*^__^*) 嘻嘻 案例场景： www.kame.net网站域名同时拥有IPv4 DNS解析和IPv6 DNS解析。 如下 所示： C:\Documents and Settings\Administrator&#62;ping www.kame.net Pinging orange.kame.net [203.178.141.194] with 32 bytes of data: =========================================================== C:\Documents and Settings\Administrator&#62;ping www.kame.net Pinging orange.kame.net [2001:200:dff:fff1:216:3eff:feb1:44d7] with 32 bytes of data: 那么如果IPv4和IPv6同时存在，哪一个会优先被使用呢？ 自然是IPv6，因为这是新的协议，新协议都通了，旧的自然不必说。 但问题是，系统是如何判断IPv6网络时可用的呢？如果不可用却把地址解析成IPv6地址，那岂不是惨了？ 我们来做个试验，试验环境WinxP，IPv4可以连接外网，安装ipv6协议，但无ipv6网络。 我们用ipconfig可以看到接口状态 Ethernet adapter 本地连接 2: Connection-specific DNS Suffix  . : IP Address. . . . . . . [...]]]></description>
			<content:encoded><![CDATA[<p>今天爆发了，写第三篇文章了，(*^__^*) 嘻嘻</p>
<p><strong>案例场景：</strong></p>
<p><a href="http://www.kame.net/">www.kame.net</a>网站域名同时拥有IPv4 DNS解析和IPv6 DNS解析。<br />
如下 所示：<br />
C:\Documents and Settings\Administrator&gt;<strong>ping </strong><a href="http://www.kame.net/"><strong>www.kame.net</strong></a></p>
<p>Pinging orange.kame.net [<span style="color: #ff0000;"><strong>203.178.141.194</strong></span>] with 32 bytes of data:</p>
<p>===========================================================<br />
C:\Documents and Settings\Administrator&gt;<strong>ping </strong><a href="http://www.kame.net/"><strong>www.kame.net</strong></a></p>
<p>Pinging orange.kame.net [<span style="color: #ff0000;"><strong>2001:200:dff:fff1:216:3eff:feb1:44d7</strong></span>] with 32 bytes of<br />
data:</p>
<p><strong>那么如果IPv4和IPv6同时存在，哪一个会优先被使用呢？</strong></p>
<p>自然是IPv6，因为这是新的协议，新协议都通了，旧的自然不必说。</p>
<p><strong>但问题是，系统是如何判断IPv6网络时可用的呢？如果不可用却把地址解析成IPv6地址，那岂不是惨了？</strong></p>
<p>我们来做个试验，试验环境WinxP，IPv4可以连接外网，安装ipv6协议，但无ipv6网络。<span id="more-853"></span></p>
<p>我们用ipconfig可以看到接口状态</p>
<p>Ethernet adapter 本地连接 2:</p>
<p>Connection-specific DNS Suffix  . :<br />
IP Address. . . . . . . . . . . . : 192.168.0.6<br />
Subnet Mask . . . . . . . . . . . : 255.255.255.0<br />
IP Address. . . . . . . . . . . . : fec0::a:2e0:4cff:fe46:f24f%2<br />
IP Address. . . . . . . . . . . . : 2002:404:401:a:9123:a5b3:bed4:df11<br />
IP Address. . . . . . . . . . . . : 2002:404:401:a:2e0:4cff:fe46:f24f<br />
IP Address. . . . . . . . . . . . : fe80::2e0:4cff:fe46:f24f%7<br />
Default Gateway . . . . . . . . . : 192.168.0.1<br />
fe80::f898:2bda:2f5d:e06d%7</p>
<p>此时接口拥有link local本地链路地址，和6to4地址，（为什么有6to4？我也不清楚耶~反正我机器有5张网卡，其中一个是4.4.4.1，不管他，这个与本话题无关）</p>
<p><strong>此时ping </strong><a href="http://www.kame.net/"><strong>www.kame.net</strong></a><strong>解析出IPv4地址。</strong></p>
<p>接下来我们用ipv6 -p adu <span style="color: #ff0000;">7</span>/2001:470:19:13c::dead:beef  给接口增加一个global unicast地址</p>
<p><strong>此时ping </strong><a href="http://www.kame.net"><strong>www.kame.net</strong></a><strong>解析出IPv6地址！！！</strong>但是ping不通，因为我没有ipv6网络。</p>
<p>这是使用浏览器打开<a href="http://www.kame.net/">www.kame.net</a>需要花很长时间。</p>
<p><strong>实验结论：<br />
<span style="color: #ff0000;">当主接口存在global unicast地址时，系统会认为IPv6网路联通，进行IPv6解析，<br />
但当使用IPv6无法访问时，会重新采用IPV4。<br />
</span></strong></p>
<p><span style="color: #ff00ff;"><strong>本文仅为实验结论，如果您有更权威的说法，请告诉我，谢谢！^_^</strong></span></p>
<p><span style="color: #ff00ff;"><strong><span style="color: #000000;">&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</span></strong></span></p>
<p><strong>关于第一条命令的ipv6 if 7，这里面的7是哪里来的，我不想再重复了<br />
</strong>C:\Documents and Settings\Administrator&gt;netsh int ipv6 sh int<br />
正在查询活动状态&#8230;</p>
<p>索引 Met   MTU    状态          名称<br />
&#8212;- &#8212;-  &#8212;&#8211;  &#8212;&#8212;&#8212;&#8212;  &#8212;&#8211;<br />
6     0   1500  已连接           VMware Network Adapter VMnet8<br />
5     0   1500  已连接           本地连接<br />
4     2   1280  已断开           Teredo Tunneling Pseudo-Interface<br />
3     1   1280  已连接           6to4 Tunneling Pseudo-Interface<br />
2     1   1280  已连接           Automatic Tunneling Pseudo-Interface<br />
1     0   1500  已连接           Loopback Pseudo-Interface<br />
<strong> </strong></p>
<p><strong>这里的索引就是接口ID.也就是上面说的7<br />
此命令可以查看接口的ID、状态和名称。</strong></p>
<p><span style="color: #000000;">&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</span></p>
<p>如何调整ipv4和ipv6的优先级呢，根据孤舟蓑翁的提示，查找了相关的资料。</p>
<p>大家可以参考一下：</p>
<p><a href="http://www.ipv6day.org/action.php?n=En.Configuration-Windows2003" target="_blank">http://www.ipv6day.org/action.php?n=En.Configuration-Windows2003</a><br />
<a href="http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/b4d504c8-2ae9-41f3-bf21-e2e5d7d9704f" target="_blank">http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/b4d504c8-2ae9-41f3-bf21-e2e5d7d9704f</a></p>
<p><span style="color: #000000;">&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />
</span></p>
<p><span style="color: #000000;">end</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ipcpu.com/2010/11/ipv6-ipv6-who/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>IPv4私有地址、保留地址</title>
		<link>http://www.ipcpu.com/2009/12/ipv4-address-reserved/</link>
		<comments>http://www.ipcpu.com/2009/12/ipv4-address-reserved/#comments</comments>
		<pubDate>Thu, 17 Dec 2009 13:13:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[网络技术]]></category>
		<category><![CDATA[IPv4]]></category>
		<category><![CDATA[RFC]]></category>
		<category><![CDATA[私有地址]]></category>

		<guid isPermaLink="false">http://www.ipcpu.com/?p=338</guid>
		<description><![CDATA[Summary Table    Address Block             Present Use                       Reference    &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;    0.0.0.0/8            &#8220;This&#8221; Network                    [RFC1700, page 4]    10.0.0.0/8           Private-Use Networks                   [RFC1918]    14.0.0.0/8           Public-Data Networks         [RFC1700, page 181]    24.0.0.0/8           Cable Television Networks                    &#8211;    39.0.0.0/8           Reserved but subject                                          to allocation                       [RFC1797]    127.0.0.0/8          Loopback                       [RFC1700, page 5]    128.0.0.0/16         Reserved but subject [...]]]></description>
			<content:encoded><![CDATA[<p>Summary Table</p>
<p>   Address Block             Present Use                       Reference<br />
   &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
   0.0.0.0/8            &#8220;This&#8221; Network                    [RFC1700, page 4]<br />
   10.0.0.0/8           Private-Use Networks                   [RFC1918]<br />
   14.0.0.0/8           Public-Data Networks         [RFC1700, page 181]<br />
   24.0.0.0/8           Cable Television Networks                    &#8211;<br />
   39.0.0.0/8           Reserved but subject<br />
                                         to allocation                       [RFC1797]<br />
   127.0.0.0/8          Loopback                       [RFC1700, page 5]<br />
   128.0.0.0/16         Reserved but subject<br />
                                          to allocation                             &#8211;<br />
   169.254.0.0/16       Link Local                                   &#8211;<br />
   172.16.0.0/12        Private-Use Networks                   [RFC1918]<br />
   191.255.0.0/16       Reserved but subject<br />
                                            to allocation                             &#8211;<br />
   192.0.0.0/24         Reserved but subject<br />
                                           to allocation                             &#8211;<br />
   192.0.2.0/24         Test-Net<br />
   192.88.99.0/24       6to4 Relay Anycast                     [RFC3068]<br />
   192.168.0.0/16       Private-Use Networks                   [RFC1918]<br />
   198.18.0.0/15        Network Interconnect<br />
                                         Device Benchmark Testing            [RFC2544]<br />
   223.255.255.0/24     Reserved but subject<br />
                                               to allocation                             &#8211;<br />
   224.0.0.0/4          Multicast                              [RFC3171]<br />
   240.0.0.0/4          Reserved for Future Use        [RFC1700, page 4]</p>
<p><strong>From RFC3330</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ipcpu.com/2009/12/ipv4-address-reserved/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

