From owner-freebsd-net@freebsd.org Mon Oct 16 11:24:23 2017 Return-Path: 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 67EA9E37130 for ; Mon, 16 Oct 2017 11:24:23 +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 562B877D97 for ; Mon, 16 Oct 2017 11:24:23 +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 v9GBONNo018447 for ; Mon, 16 Oct 2017 11:24:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attatching vxlan interfaces to a bridge stops all traffic on it Date: Mon, 16 Oct 2017 11:24:23 +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: heinz@project-fifo.net 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: resolution bug_status Message-ID: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:24:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Heinz N. Gies changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|Works As Intended |--- Status|Closed |Open --- Comment #4 from Heinz N. Gies --- I understand that it acts as implemented i.e. is not a code bug. Before we close this I'd like to make a case that is not working as intended but rath= er working as accepted. The VNET system is rather new in FreeBSD, bridges, on the other hand, exist= for a lot longer. Historically bridges were used in a rather static manner, to bridge physical interfaces (they don't change often), or bridge between physical interfaces= and tunnels or other virtual but too rather static interfaces. This kind of use is often a one-time configuration that happens on system startup or in the case of tunnels in an incredibly rare basis. At those tim= es the loss of connectivity for a few seconds either has no impact (during startup), or the impact is neglectable (i.e. adding tunnel interfaces as no= one is connected to a nonexisting interface anyway). I suspect that when the decision was made to implement it this way all that= was taken into consideration and (rightfully so) it wasn't worth the work for finding an alternative as it was working good enough for its use. VNET and more so VNET jails change things a bit, they make network configuration more dynamic. It becomes required to add and remove interface= s to a bridge dynamically - something that I suspect wasn't foreseen. Features do not exist in a void, they exist in relation to their environmen= t. The environment for bridges changed and while it was fine before it becomes problematic in this changed environment. I agree it's not a 'bug' in the bridge driver. But we can not look at a sin= gle component in isolation and on a system level, I'm sure that 'starting/stopp= ing a vnet jail means all other vnet jails loose connectivity' is intended behavior. --=20 You are receiving this mail because: You are the assignee for the bug.=