Netdev List
 help / color / mirror / Atom feed
From: Krzysztof Oledzki <olel@ans.pl>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org
Subject: Re: incorrect cksum with tcp/udp on lo with 2.6.20/2.6.21/2.6.22
Date: Tue, 2 Oct 2007 16:15:15 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710021606550.3175@bizon.gios.gov.pl> (raw)
In-Reply-To: <20071002104033.GA30281@gondor.apana.org.au>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 897 bytes --]



On Tue, 2 Oct 2007, Herbert Xu wrote:

> On Mon, Sep 24, 2007 at 11:44:19AM +0200, Krzysztof Oledzki wrote:
>>
>> So, with DR mode, packet goes by the lo device (with bad checksum) and
>> then get redirected outside. Unfortunately, when it leaves host it has bad
>> checksum, too. :(
>
> Did you check this by taking a tcpdump on an external host?
Yes.

> Doing a local tcpdump doesn't work as tcpdump won't show the
> correct checksum if checksum offload is enabled.
Indeed, I'm aware about this.

> If it's really sending a bogus checksum then it's a bug in
> LVS.

I'm not sure if we should call it a bug. LVS does not support such 
configuration by default - it requires kernel patching. However, it worked 
with older kernels so that's why I asked if it is possible to force full 
TCP/UDP checksum calculation?

Thank you.

Best regards,

 				Krzysztof Olędzki

  reply	other threads:[~2007-10-02 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 17:55 incorrect cksum with tcp/udp on lo with 2.6.20/2.6.21/2.6.22 Krzysztof Oledzki
2007-09-23  4:39 ` Herbert Xu
2007-09-23 21:18   ` Krzysztof Oledzki
2007-09-24  1:30     ` Herbert Xu
2007-09-24  9:44       ` Krzysztof Oledzki
2007-10-02 10:40         ` Herbert Xu
2007-10-02 14:15           ` Krzysztof Oledzki [this message]
2007-10-02 14:17             ` Herbert Xu

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=Pine.LNX.4.64.0710021606550.3175@bizon.gios.gov.pl \
    --to=olel@ans.pl \
    --cc=herbert@gondor.apana.org.au \
    --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