netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baruch Even <baruch@ev-en.org>
To: Netdev <netdev@vger.kernel.org>
Subject: Multicast and hardware checksum
Date: Fri, 08 Jun 2007 01:33:14 +0300	[thread overview]
Message-ID: <466887AA.800@ev-en.org> (raw)

Hello,

I have a machine on which I have an applications that sends multicast 
through eth interface with hardware tx checksum enabled. On the same 
machine I have mrouted running that routes the multicast traffic to a 
set of ppp interfaces. The packets that are received by the client have 
their checksum fixed on some number which is incorrect. If I disable tx 
checksum on the eth device the packets arrive with the proper checksum.

I still haven't followed the code paths to see how to fix this, maybe 
someone knows the relevant code and can find it faster.

Baruch

             reply	other threads:[~2007-06-07 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 22:33 Baruch Even [this message]
2007-06-08  6:20 ` Multicast and hardware checksum Herbert Xu
2007-06-08 11:02   ` Baruch Even
2007-06-08 11:06     ` Herbert Xu
2007-06-08 11:15       ` Baruch Even
2007-06-08 11:33         ` Baruch Even

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=466887AA.800@ev-en.org \
    --to=baruch@ev-en.org \
    --cc=netdev@vger.kernel.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).