From owner-freebsd-current@freebsd.org  Mon Apr 11 18:07:52 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5391B0C9BA
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 11 Apr 2016 18:07:52 +0000 (UTC)
 (envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id A1176175A;
 Mon, 11 Apr 2016 18:07:52 +0000 (UTC)
 (envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.55.3])
 by phk.freebsd.dk (Postfix) with ESMTP id 530F24FB55;
 Mon, 11 Apr 2016 18:07:50 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u3BI7m5N016648;
 Mon, 11 Apr 2016 18:07:48 GMT (envelope-from phk@phk.freebsd.dk)
To: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
cc: Cy Schubert <Cy.Schubert@komquats.com>,
 Michael Butler <imb@protected-networks.net>, "K. Macy" <kmacy@freebsd.org>,
 FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject: Re: CURRENT slow and shaky network stability
In-reply-to: <20160409105444.7020f2f1.ohartman@zedat.fu-berlin.de>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <20160405082047.670d7241@freyja.zeit4.iv.bundesimmobilien.de>
 <201604050646.u356k850078565@slippy.cwsent.com>
 <20160409105444.7020f2f1.ohartman@zedat.fu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <16646.1460398068.1@critter.freebsd.dk>
Date: Mon, 11 Apr 2016 18:07:48 +0000
Message-ID: <16647.1460398068@critter.freebsd.dk>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2016 18:07:52 -0000

--------

I have been trying to capture a packet trace for the breaking SSH
and while not a statistically rigid conclusion, it doesnt seem
to happen when I run a tcpdump on wlan0.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.