From: Dunc <dunc@lemonia.org>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Marc Donner <webmaster@poweraudio.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: TCP_MD5 and Intel e1000
Date: Tue, 22 May 2007 10:04:39 +0100 [thread overview]
Message-ID: <4652B227.60404@lemonia.org> (raw)
In-Reply-To: <20070522105738.f03cb83b.dada1@cosmosbay.com>
Eric Dumazet wrote:
> On Tue, 22 May 2007 09:33:29 +0200
> Marc Donner <webmaster@poweraudio.de> wrote:
>
>> Hi,
>>
>> 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?
>>
>
> Hi Marc
>
> CCed netdev as more appropriate to discuss about network stuff.
>
> Would be nice if you sent some tcpdump samples to share with us, and tell us
> which exact linux version you tried.
>
> You could try "ethtool -K tx off", and/or other ethtool -K settings
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
I had this with e1000 NICs and it was just because I had TSO on.
It is disabled with ethtool as Eric suggests
Cheers,
Dunc
next prev parent reply other threads:[~2007-05-22 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 7:33 TCP_MD5 and Intel e1000 Marc Donner
2007-05-22 8:57 ` Eric Dumazet
2007-05-22 9:04 ` Dunc [this message]
2007-05-22 9:36 ` YOSHIFUJI Hideaki / 吉藤英明
2007-05-22 10:14 ` David Miller
2007-05-22 10:33 ` Marc Donner
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=4652B227.60404@lemonia.org \
--to=dunc@lemonia.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=webmaster@poweraudio.de \
/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.