From owner-freebsd-bugs@FreeBSD.ORG  Tue Aug 12 16:04:13 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@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 E7DEDC5D
 for <freebsd-bugs@FreeBSD.org>; Tue, 12 Aug 2014 16:04:13 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CFFA024E5
 for <freebsd-bugs@FreeBSD.org>; Tue, 12 Aug 2014 16:04:13 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7CG4DnE061125
 for <freebsd-bugs@FreeBSD.org>; Tue, 12 Aug 2014 16:04:13 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 192599] zero window and persist timer not set
Date: Tue, 12 Aug 2014 16:04:14 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 9.2-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jlott@averesystems.com
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-192599-8-fFnftKjeT0@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-192599-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-192599-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Aug 2014 16:04:14 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192599

--- Comment #2 from Jeremiah <jlott@averesystems.com> ---
Created attachment 145717
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145717&action=edit
recv.py

I was asked to share my test programs, so I will.  However, I'm not sure that
it will help reproduce it in another environment.  It was very dependent on
network timing as well as the features of the network drivers on both side (do
they support tso/lro, etc.).  I tweaked it endlessly until I got something that
reproduced it somewhat consistently in our environment.

The names of the files are probably a bit of a misnomer, too (backwards from
what you would expect).  Run recv.py on the box you want to reproduce the
problem on and send.py on another freebsd box.  It does not work running on
same box, since MTU gets set to 16K in that case.  You can only tell if the
problem is reproduced by running a packet trace during the run and seeing if
there are zero window probes sent or not.  You'll have to SIGINT both programs
after checking the packet trace, they just wait in the zero window condition
forever whether the probes are sent or not.

-- 
You are receiving this mail because:
You are the assignee for the bug.