| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200705221233.25858.donner@dbd-breitband.de> Date: Tue, 22 May 2007 12:33:25 +0200 From: Marc Donner <donner@...-breitband.de> To: David Miller <davem@...emloft.net> Cc: yoshfuji@...ux-ipv6.org, dada1@...mosbay.com, webmaster@...eraudio.de, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: TCP_MD5 and Intel e1000 On Tuesday 22 May 2007, David Miller wrote: > From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@...ux-ipv6.org> > Date: Tue, 22 May 2007 18:36:47 +0900 (JST) > > > In article <20070522105738.f03cb83b.dada1@...mosbay.com> (at Tue, 22 May 2007 10:57:38 +0200), Eric Dumazet <dada1@...mosbay.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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists