From: anupam.kapoor@gmail.com (Anupam Kapoor)
To: kernelnewbies@lists.kernelnewbies.org
Subject: writting NIC driver for IPV6
Date: Wed, 29 Jun 2011 12:36:02 +0530 [thread overview]
Message-ID: <BANLkTi=_C_5X0WZ3R_g+JdjVvA4R0quAcQ@mail.gmail.com> (raw)
In-Reply-To: <FB770C3681D13B43AC74438DAC1AC3F7592EB96995@MTKMBS30.mediatek.inc>
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110629/3201e66b/attachment.html
prev parent reply other threads:[~2011-06-29 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 10:02 writting NIC driver for IPV6 Gang Lei (雷刚)
2011-06-28 16:38 ` Michael Blizek
2011-06-29 1:38 ` Gang Lei (雷刚)
2011-06-29 6:32 ` Mulyadi Santosa
2011-06-29 7:06 ` Anupam Kapoor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=_C_5X0WZ3R_g+JdjVvA4R0quAcQ@mail.gmail.com' \
--to=anupam.kapoor@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).