From owner-svn-src-all@FreeBSD.ORG Thu Apr 23 14:02:35 2015 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA97BF3F; Thu, 23 Apr 2015 14:02:35 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B629C1123; Thu, 23 Apr 2015 14:02:35 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 10BE9B923; Thu, 23 Apr 2015 10:02:34 -0400 (EDT) From: John Baldwin To: Gleb Smirnoff Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r281885 - head/sys/net Date: Thu, 23 Apr 2015 10:02:19 -0400 Message-ID: <1643843.xLCHLSf0Gm@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <201504231319.t3NDJ1tW060060@svn.freebsd.org> References: <201504231319.t3NDJ1tW060060@svn.freebsd.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 23 Apr 2015 10:02:34 -0400 (EDT) X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2015 14:02:36 -0000 On Thursday, April 23, 2015 01:19:01 PM Gleb Smirnoff wrote: > Author: glebius > Date: Thu Apr 23 13:19:00 2015 > New Revision: 281885 > URL: https://svnweb.freebsd.org/changeset/base/281885 > > Log: > Don't propagate SIOCSIFCAPS from a vlan(4) to its parent. This leads to > quite unexpected result of toggling capabilities on the neighbour vlan(4) > interfaces. > > Reviewed by: melifaro, np > Differential Revision: https://reviews.freebsd.org/D2310 > Sponsored by: Nginx, Inc. Can you look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194855 or grab it? It seems to be closely related. I'm not sure if it is useful to allow vlans to use independent MTUs. It does not seem to make sense for a VLAN to have a larger MTU than the trunk though (perhaps the other direction can make sense, but maybe we should let a VLAN's MTU track the trunk unless the VLAN's MTU is set explicitly?) -- John Baldwin