From owner-freebsd-net@freebsd.org Mon Apr 25 20:54:17 2016 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 B5834B1C8C7 for ; Mon, 25 Apr 2016 20:54:17 +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 A64B619A2 for ; Mon, 25 Apr 2016 20:54:17 +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 u3PKsHV6028166 for ; Mon, 25 Apr 2016 20:54:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208910] if_bridge does not work properly with vlans and VIMAGE Date: Mon, 25 Apr 2016 20:54:17 +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: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: shawn@debnath.net 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: 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.21 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, 25 Apr 2016 20:54:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208910 --- Comment #2 from Shawn Debnath --- Per kp@, current patch by delphij is not a proper fix for the issue (see review). I am going to dig deeper to try to find the root cause for two iss= ues I am running into, which according to kp@ are unrelated but would be good to hunt down: 1) why the bridge is not accepting and retaining the mac address of the fir= st interface attached to it. 2) why the bridge is unable to disable capabilities on the parent interface (likely IFCAP_LRO, but could be others as well). Regardless, kernel shouldn't be exposing all of SIOCSIFCAP to the parent interface. --=20 You are receiving this mail because: You are the assignee for the bug.=