From: Marc Donner <donner@dbd-breitband.de>
To: David Miller <davem@davemloft.net>
Cc: yoshfuji@linux-ipv6.org, dada1@cosmosbay.com,
webmaster@poweraudio.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: TCP_MD5 and Intel e1000
Date: Tue, 22 May 2007 12:33:25 +0200 [thread overview]
Message-ID: <200705221233.25858.donner@dbd-breitband.de> (raw)
In-Reply-To: <20070522.031432.08079709.davem@davemloft.net>
On Tuesday 22 May 2007, David Miller wrote:
> From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
> Date: Tue, 22 May 2007 18:36:47 +0900 (JST)
>
> > In article <20070522105738.f03cb83b.dada1@cosmosbay.com> (at Tue, 22 May
2007 10:57:38 +0200), Eric Dumazet <dada1@cosmosbay.com> says:
> > > > I have tried to set up quagga with tcp-md5 support from kernel. All
> > > > seems ok with a intel e100 NIC, but as i testetd with a intel e1000
> > > > NIC the tcp packets have an invalid md5 digest.
> > > > If i run tcpdump on the mashine the packets are generated, it shows
> > > > on the outgoing interface invalid md5 digests.
> > > > Are there known issues about tcp-md5 and e1000 NICs?
> > >
> > > You could try "ethtool -K tx off", and/or other ethtool -K settings
> >
> > Disabling offloading should help; currently tcp-md5 stack
> > blindly copy md5-signature from the first segment
> > which is not appropriate for rest of segments.
>
> It is clear we should disable TSO for sockets making use of TCP-MD5.
disabling tso works. thanks
next prev parent reply other threads:[~2007-05-22 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C2786969.24B46%webmaster@poweraudio.de>
2007-05-22 8:57 ` TCP_MD5 and Intel e1000 Eric Dumazet
2007-05-22 9:04 ` Dunc
2007-05-22 9:36 ` YOSHIFUJI Hideaki / 吉藤英明
2007-05-22 10:14 ` David Miller
2007-05-22 10:33 ` Marc Donner [this message]
2007-06-12 21:39 ` David Miller
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=200705221233.25858.donner@dbd-breitband.de \
--to=donner@dbd-breitband.de \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=webmaster@poweraudio.de \
--cc=yoshfuji@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).