Thanks a lot, Michi. 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? Rick From: kernelnewbies-bounces@kernelnewbies.org [mailto:kernelnewbies-bounces@kernelnewbies.org] On Behalf Of Michael Blizek Sent: 2011年6月29日 0:38 To: Gang Lei (雷刚) Cc: kernelnewbies@kernelnewbies.org Subject: Re: writting NIC driver for IPV6 Hi! On 18:02 Tue 28 Jun , Gang Lei (????) wrote:

HI all:

Thanks for your help in advance. Could anyone tell me how to revise NIC driver to support IPV6? Or it doesn??t need driver??s change to support IPV6? Can anyone throw some light on this question?

You do not need to change the nic driver to support IPv6 unless it's the driver is totally broken. Network cards and drivers operate on layer 2 and generally do not care what you do on layer 3 and above. However in some cases hardware accelerations like "TCP segmentation offloading" may be available which partly violates this layer separation. But this is "only" a performance issue. -Michi -- programing a layer 3+4 network protocol for mesh networks see http://michaelblizek.twilightparadox.com _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

2011/6/29 Gang Lei (雷刚) <gang.lei@mediatek.com>

Thanks a lot, Michi.****

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?

yes apart from ping6, you can use: 1. wireshark/ethereal for seeing ND messages on the wire 2. if possible, setup ISATAP in your lab-network. ubuntu does have a isatapd, so should other distributions. 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 kame.org for example, i have the following is0 Link encap:IPv6-in-IPv4 inet6 addr: 2001:420:5401:1:200:5efe:4067:9c63/64 Scope:Global inet6 addr: fe80::200:5efe:4067:9c63/64 Scope:Link UP RUNNING NOARP MTU:1280 Metric:1 RX packets:1352 errors:0 dropped:0 overruns:0 frame:0 TX packets:872 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1575341 (1.5 MB) TX bytes:72571 (72.5 KB) <aside> can you find out where i work from above ? ;) have fun... anupam -- In the beginning was the lambda, and the lambda was with Emacs, and Emacs was the lambda.