From owner-freebsd-net@FreeBSD.ORG Thu Jan 16 16:03:12 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5F339653 for ; Thu, 16 Jan 2014 16:03:12 +0000 (UTC) Received: from mx1.shrew.net (mx1.shrew.net [38.97.5.131]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2F4AF1A08 for ; Thu, 16 Jan 2014 16:03:11 +0000 (UTC) Received: from mail.shrew.net (mail.shrew.prv [10.24.10.20]) by mx1.shrew.net (8.14.7/8.14.7) with ESMTP id s0GFqtks058695 for ; Thu, 16 Jan 2014 09:52:56 -0600 (CST) (envelope-from mgrooms@shrew.net) Received: from [127.0.0.1] (216-110-21-66.static.twtelecom.net [216.110.21.66]) by mail.shrew.net (Postfix) with ESMTPSA id 67291187E7E for ; Thu, 16 Jan 2014 09:52:50 -0600 (CST) Message-ID: <52D8005F.8070104@shrew.net> Date: Thu, 16 Jan 2014 09:53:03 -0600 From: Matthew Grooms User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: TCP socket handling lo[X], buggy in 9.x? References: <52D4E633.1060000@shrew.net> <20140114100612.GR8472@FreeBSD.org> In-Reply-To: <20140114100612.GR8472@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mx1.shrew.net [10.24.10.10]); Thu, 16 Jan 2014 09:52:56 -0600 (CST) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jan 2014 16:03:12 -0000 On 1/14/2014 4:06 AM, Gleb Smirnoff wrote: > Matthew, > > On Tue, Jan 14, 2014 at 01:24:35AM -0600, Matthew Grooms wrote: > M> It looks like the 9.2 host is sending a reset before sending every PDU. > M> Weird. In any case, this is really easy to re-produce. Anyone have an > M> idea as to why this started happening? I didn't try FreeBSD 10, but I > M> suspect the problem is the same. > > I failed to reproduce that on couple of FreeBSD 11 boxes. > Gleb, Thanks for the sanity check. I upgraded my vSphere ESXi host, and the problem went away. Maybe some esoteric bug with the vswitch. I can't explain it, and I was seeing the issue on two different VMs that were running 9.2-RELEASE-p2. Super weird. Thanks again, -Matthew