From owner-freebsd-ipfw@freebsd.org  Sat Jan 28 06:39:32 2017
Return-Path: <owner-freebsd-ipfw@freebsd.org>
Delivered-To: freebsd-ipfw@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 58420CC5C45
 for <freebsd-ipfw@mailman.ysv.freebsd.org>;
 Sat, 28 Jan 2017 06:39:32 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 419821E70
 for <freebsd-ipfw@FreeBSD.org>; Sat, 28 Jan 2017 06:39:32 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0S6dV07056346
 for <freebsd-ipfw@FreeBSD.org>; Sat, 28 Jan 2017 06:39:32 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ipfw@FreeBSD.org
Subject: [Bug 209680] ipfw: when enabled, net connections time out/ssh
 results in "broken pipe"
Date: Sat, 28 Jan 2017 06:39:31 +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: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: lwhite@nrw.ca
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ipfw@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-209680-7515-aURPmEoxRd@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209680-7515@https.bugs.freebsd.org/bugzilla/>
References: <bug-209680-7515@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ipfw/>
List-Post: <mailto:freebsd-ipfw@freebsd.org>
List-Help: <mailto:freebsd-ipfw-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jan 2017 06:39:32 -0000

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

Len White <lwhite@nrw.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lwhite@nrw.ca

--- Comment #11 from Len White <lwhite@nrw.ca> ---
I've been having the same issue, it's very random.  I've spent A LOT of time
debugging it, adding extra print statements in ipfw... unfortunately I can't
trigger the issue at will.  It does seem to happen more often if I start up
World of Warcraft from a system behind the ipfw machine.  But it seems like
whatever the issue is, it's causing the connections to "expire" prematurely=
.=20
When it happens new connections will die in 5-15 seconds over and over.  I =
can
reboot the system and it will come back up, still doing the same thing, then
5-10 mins later it will be fine.  Never any errors in logs or dmesg when it
happens.

Running 11.0-RELEASE-p5

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