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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 15 Sep 2007 01:09:16 -0400 From: Bill Fink <billfink@...dspring.com> To: "L F" <lfabio.linux@...il.com> Cc: "Kok, Auke" <auke-jan.h.kok@...el.com>, netdev@...r.kernel.org Subject: Re: e1000 driver and samba On Fri, 14 Sep 2007, L F wrote: > > can you describe your setup a bit more in detail? you're writing from a linux > > client to a windows smb server? or even to a linux server? which end sees the > > connection drop? the samba server? the samba linux client? > Certainly. > I have a LAN, with two switches in a stack. There currently are 7 > WinXP clients and one linux machine. The linux machine acts as a samba > server and as a firewall/gateway. > The two ports of the PRO/1000 in the linux box are connected to the > LAN (eth4) and to a Comcast modem (eth3) respectively. Shorewall 3.4.5 > is running on the linux machine, with a strong firewall + NAT setup. > Further, the linux machine currently has a tap device bridged into the > LAN side, for virtualbox. > Therefore, eth3 is a plain ethernet interface. br0, on the lan side, > is tap0 + eth4. > If I get any client on the LAN side, I can read from the linux box > without a problem. However, if I attempt to write to the linux box > from a LANside client, it will fail. If traffic is low, the failures > are sporadic. If traffic is high (large file and/or multiple incoming > files) the failure is guaranteed, either in 'delayed write fail' mode > on the client or in silent corruption of the file (much worse). If > read/write activity is combined, for instance when I unzip a zip > archive to its own directory, failure is guaranteed and rapid, with a > 'delayed write fail' on the client after 50MB or so. > I can post .config and anything else you may want if you require it. I > tried changing cable as you suggested with little success. I'll try > changing switch port, just to cover all bases. Would it be worth a shot to try disabling the receiver hardware checksumming (ethtool -K ethX rx off)? -Bill - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists