Date: Thu, 23 Apr 2015 10:02:19 -0400 From: John Baldwin <jhb@freebsd.org> To: Gleb Smirnoff <glebius@freebsd.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r281885 - head/sys/net Message-ID: <1643843.xLCHLSf0Gm@ralph.baldwin.cx> In-Reply-To: <201504231319.t3NDJ1tW060060@svn.freebsd.org> References: <201504231319.t3NDJ1tW060060@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1643843.xLCHLSf0Gm>