From owner-freebsd-net@freebsd.org  Mon Oct 16 12:06:53 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 80174E38D92
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon, 16 Oct 2017 12:06:53 +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 6E6427DD14
 for <freebsd-net@FreeBSD.org>; Mon, 16 Oct 2017 12:06:53 +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 v9GC6rKJ085076
 for <freebsd-net@FreeBSD.org>; Mon, 16 Oct 2017 12:06:53 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on
 uplink NIC for few seconds
Date: Mon, 16 Oct 2017 12:06:53 +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.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: mav@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-221122-2472-DYruJVCTkX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221122-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-221122-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, 16 Oct 2017 12:06:53 -0000

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

--- Comment #8 from Alexander Motin <mav@FreeBSD.org> ---
(In reply to Heinz N. Gies from comment #7)
Bridge+epair are the right tools, unless you wish to dedicate one NIC
completely to specific VNET Jail.

I've already told you how to workaround the problem:  when configuring upli=
nk
interface, you can explicitly disable its capabilities that bridge try to
disable otherwise (TSO, LRO, TOE, TXCSUM, TXCSUM6).  In that case bridge sh=
ould
be happy from the beginning and not modify capabilities any more.

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