<br><div>2011/6/29 Gang Lei (À׸Õ) <span dir="ltr"><<a href="mailto:gang.lei@mediatek.com">gang.lei@mediatek.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="ZH-CN" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:#1F497D">Thanks a lot, Michi.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:#1F497D">Then how can I verify that IPV6 can be really running on our
NIC? Of course I have to build a kernel which can support IPV6 firstly, but how
to verify it’s really working? Use ping6?</span></p></div></div></blockquote><div> yes apart from ping6, you can use:</div><div> 1. wireshark/ethereal for seeing ND messages on the wire</div><div> 2. if possible, setup ISATAP in your lab-network. ubuntu does have a isatapd, so should other distributions.</div>
<div> 3. once you have (2) setup, update your resolver to do quad-A queries by default i.e. 'option inet6'. if you use google's DNS, you should be able to see dancing turtle at <a href="http://kame.org">kame.org</a></div>
<div><br></div><div>for example, i have the following</div><div><br></div><div><div>is0 Link encap:IPv6-in-IPv4 </div><div> inet6 addr: 2001:420:5401:1:200:5efe:4067:9c63/64 Scope:Global</div><div> inet6 addr: fe80::200:5efe:4067:9c63/64 Scope:Link</div>
<div> UP RUNNING NOARP MTU:1280 Metric:1</div><div> RX packets:1352 errors:0 dropped:0 overruns:0 frame:0</div><div> TX packets:872 errors:0 dropped:0 overruns:0 carrier:0</div><div> collisions:0 txqueuelen:0 </div>
<div> RX bytes:1575341 (1.5 MB) TX bytes:72571 (72.5 KB)</div></div><div><br></div><div><aside> can you find out where i work from above ? ;)</div><div><br></div><div>have fun...</div><div><br></div><div>anupam</div>
</div>-- <br>In the beginning was the lambda, and the lambda was with Emacs, and Emacs was the lambda. <br>
</div>