From: Brian Haley <brian.haley@hp.com>
To: Steve Chen <schen@mvista.com>
Cc: usagi-users-ctl@ml.linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: TAHI CN-6-4-1 failed on Linux 2.6.32 kernel
Date: Fri, 13 Aug 2010 13:55:27 -0400 [thread overview]
Message-ID: <4C65870F.4080307@hp.com> (raw)
In-Reply-To: <AANLkTi=01koVqt6YR0LQi53Nx0E=7UT1TFVNL44TwAR4@mail.gmail.com>
On 08/13/2010 01:34 PM, Steve Chen wrote:
>>>>> The TAHI correspondent node tests CN-6-4-1 (Processing in upper layer
>>>>> - Echo Checksum) failed for me in the 2.6.32 kernel. It appears that
>>>>> the Linux kernel is replying the ICMP echo request in
>>>>> icmpv6_echo_reply without much checking. Is this an intentional
>>>>> non-conformance to RFC3775 section 9.3.1?
[snip]
> It appears that skb->ip_summed is always 1 (CHECKSUM_UNNECESSARY).
> I'm using e1000e. Looking at the driver, there is a checksum offload
> hardware. I think the code is doing frame check on the entire
> Ethernet packet. Since no error was found, it assume everything
> inside is correct.
# ethtool -K ethX rx off
Does that help? Does using a different NIC help?
-Brian
next prev parent reply other threads:[~2010-08-13 17:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 3:20 TAHI CN-6-4-1 failed on Linux 2.6.32 kernel Steve Chen
2010-08-12 21:10 ` Brian Haley
2010-08-12 23:04 ` Steve Chen
2010-08-13 0:00 ` Steve Chen
2010-08-13 2:23 ` Brian Haley
2010-08-13 17:34 ` Steve Chen
2010-08-13 17:55 ` Brian Haley [this message]
2010-08-13 22:25 ` Steve Chen
2010-08-16 14:07 ` Steve Chen
2010-08-19 18:35 ` Steve Chen
2010-08-20 0:06 ` David Miller
2010-08-20 17:16 ` Steve Chen
2010-08-20 17:39 ` Jesse Gross
[not found] ` <AANLkTi=T_=Dy8EhOOyevLd4yj1cy2P8ytXUPS=Y-d6hK@mail.gmail.com>
2010-08-21 4:16 ` Steve Chen
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=4C65870F.4080307@hp.com \
--to=brian.haley@hp.com \
--cc=netdev@vger.kernel.org \
--cc=schen@mvista.com \
--cc=usagi-users-ctl@ml.linux-ipv6.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).