From owner-freebsd-net@freebsd.org  Tue Sep 27 07:22:14 2016
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 0E5BEBEB17C
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Tue, 27 Sep 2016 07:22:14 +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 EB6BAF2B
 for <freebsd-net@FreeBSD.org>; Tue, 27 Sep 2016 07:22:13 +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 u8R7MDBQ091954
 for <freebsd-net@FreeBSD.org>; Tue, 27 Sep 2016 07:22:13 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 213015] openvswitch and vnet jails -  panic when bridge is
 destroyed and recreated
Date: Tue, 27 Sep 2016 07:22:13 +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-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: girgen@FreeBSD.org
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: cc
Message-ID: <bug-213015-2472-qRHAWIRZZU@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-213015-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-213015-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: Tue, 27 Sep 2016 07:22:14 -0000

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

Palle Girgensohn <girgen@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |girgen@FreeBSD.org

--- Comment #1 from Palle Girgensohn <girgen@FreeBSD.org> ---
I've hade exaclty the same problems with epair, switched to netgraph instead
which has proven rock solid.

I know there is a project to improve this area as well, can't remember frmo=
 the
top of my head who is working on it. Don't think it has hit the source tree=
 yet
though.

For epair problems, see for example this thread:
https://forums.freebsd.org/threads/31765/

If all you want is networking running in jails, I can document the procedur=
e we
use, using netgraph (not epoair). This is very solid.

Epair+vimage has alsway had this problem when tearing down the jail, sadly.

Palle

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