From: Chuck Ebbert <cebbert@redhat.com>
To: Siddharth Taneja <siddharth.taneja@gmail.com>
Cc: linux-kernel@vger.kernel.org, Netdev <netdev@vger.kernel.org>
Subject: Re: TCP MD5 and Scatter Gather offloading.
Date: Wed, 25 Jul 2007 15:32:30 -0400 [thread overview]
Message-ID: <46A7A54E.4000608@redhat.com> (raw)
In-Reply-To: <526ad3230707251012r25188175g5fa460fe90ca9d61@mail.gmail.com>
On 07/25/2007 01:12 PM, Siddharth Taneja wrote:
[cc: netdev]
> Hello,
>
> I am using a vanilla 2.6.22.1 kernel and I see the same kind of
> problem as had been mentioned some time back on this list
>
> http://lkml.org/lkml/2007/5/22/45
>
> The issue is essentially that with the MD5 option enabled for the
> specific TCP connection, the SYN and SYN-ACKS are passed fine and the
> connection establishes fine, but the other end (a cisco router)
> complains about incorrect MD5 signatures on any other message that is
> sent after this.
>
> Setting the scatter-gather offloading option on the NIC seems to
> correct this problem. Recently I had seen a checkin (as a response to
> the problem mentioned in the above link) where the TSO option was
> turned off to make MD5 work (my kernel has that fix). Is a similar
> solution needed here too?
>
> This is the information about my system:
>> uname -a
> Linux stdalone 2.6.22.1 #1 SMP Mon Jul 23 20:15:21 PDT 2007 i686 i686
> i386 GNU/Linux
>
>> ethtool -i eth0
> driver: e1000
> version: 7.3.20-k2
> firmware-version: N/A
> bus-info: 0000:01:0a.0
>
>> ethtool -k eth0
> Offload parameters for eth0:
> rx-checksumming: on
> tx-checksumming: on
> scatter-gather: off
> tcp segmentation offload: off
>
> Thanks for your help.
>
> Siddharth
>
> PS: I would like to be CC'ed on the reply to this email. Thanks.
prev parent reply other threads:[~2007-07-25 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 17:12 TCP MD5 and Scatter Gather offloading Siddharth Taneja
2007-07-25 19:32 ` Chuck Ebbert [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=46A7A54E.4000608@redhat.com \
--to=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=siddharth.taneja@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.