From owner-freebsd-net@FreeBSD.ORG Wed Dec 14 21:33:45 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D558106564A for ; Wed, 14 Dec 2011 21:33:45 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5A6C38FC0C for ; Wed, 14 Dec 2011 21:33:45 +0000 (UTC) Received: by ggnp1 with SMTP id p1so1798108ggn.13 for ; Wed, 14 Dec 2011 13:33:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=mwYKJKKJ9ufzytZmRF9/JNwoQ4pzbgQAXgoKJsjLDtA=; b=Q5fLR+rzMrCML4HJnmwyQF3BdzskGD4mPZF1uL4Qq6yPQJuXi5bT6BHIvFoL4pdsqI oXeT7r4V41T2QOn6QzpzNOMYz5K5mct0sBlOIjhuQ0PmPtyN13FqdKYKwMoKD4SXZb4s 6K/JOhV40AfDwkBBopo/LOH1Ggdj3k4hPT4fA= Received: by 10.50.236.5 with SMTP id uq5mr254996igc.47.1323898424523; Wed, 14 Dec 2011 13:33:44 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id b20sm12736801ibj.7.2011.12.14.13.33.42 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 14 Dec 2011 13:33:43 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 14 Dec 2011 13:32:42 -0800 From: YongHyeon PYUN Date: Wed, 14 Dec 2011 13:32:42 -0800 To: Andrea Venturoli Message-ID: <20111214213242.GD11426@michelle.cdnetworks.com> References: <4EE8FA10.8090502@netfence.it> <20111214195918.GC11426@michelle.cdnetworks.com> <4EE91275.3060808@netfence.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EE91275.3060808@netfence.it> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: Intel 82550 Pro/100 Ethernet and TSO troubles X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2011 21:33:45 -0000 On Wed, Dec 14, 2011 at 10:17:41PM +0100, Andrea Venturoli wrote: > On 12/14/11 20:59, YongHyeon PYUN wrote: > > >AFAIK the firmware of controller has no known TSO issue so it > >indicates a bug in driver. > >What makes me wonder is ICMP ECHO packet should not be affected by > >TSO and I have no clue at this moment. > > I wasn't talking about ICMP ECHO. > > What happened was: > a) the client connected to my server, advertising a TCP MSS of X; > b) my server started sending with packets larger than X (possibly it > misinterpreted MSS size???); > c) an ICMP packet arrived, asking my server to send packets no larger > than Y (I guess it was ignored); > d) my server kept resending the same (too big) packets; > e) it eventually reduced packet size, but it was still larger than Y; > ... > > Wireshark showed some wrong checksums (I believe on the ICMP packet, but > I might remember wrong). You can check whether you received bad checksummed frames with netstat(1). > Of course this made a bell ring and removing TSO solved everything. > > > > >(Here, I assume you've > >captured packets on receiver side since bpf sees packets before > >hardware computes checksum.) > > Yes, although I don't have them anymore. > > > > >If you have a reliable way that reproduces the issue, let me know. > > I can turn TSO on again, save the packets and send them to you. > I just hope nothing changes on the Internet in between the server and > the client. > Let me know if you need/want this and I'll arrange in the next few days. > Let me know MSS of both client and server. Is simple downloading from client to server is enough to trigger the issue? Packet capture that shows the problem would be great to know what's going on here. > > > bye & Thanks > av.