From owner-freebsd-net@freebsd.org  Mon Sep 11 08:11:41 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@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 73477E221F5
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon, 11 Sep 2017 08:11:41 +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 6227175C53
 for <freebsd-net@FreeBSD.org>; Mon, 11 Sep 2017 08:11:41 +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 v8B8B9Cj074251
 for <freebsd-net@FreeBSD.org>; Mon, 11 Sep 2017 08:11:41 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 217606] Bridge stops working after some days
Date: Mon, 11 Sep 2017 08:11:09 +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: 11.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: mops@punkt.de
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217606-2472-OjWGGAeDno@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217606-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-217606-2472@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-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 08:11:41 -0000

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

--- Comment #17 from punkt.de Hosting Team <mops@punkt.de> ---
Hi there,

we applied Fabian's patches for TCP and if_bridge (thanks!) but unfortunate=
ly
the production server's jails came to a halt again last night. Depending on
your point of view at a fortunate time of day (2am). The customers were har=
dly
affected but the operator on duty might see that differently. ;-)

Uptime of the system was roughly 10 days. The colleague was too tired when =
the
alarm woke him to think of trying things like `/etc/rc.d/netif restart` or
similar, so he just rebooted the system.

Is there any way we could help to nail this and fix it?

Some suggestions on a suitable course of action at the next incident would =
be
greatly appreciated.

Kind regards,
Patrick

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