From owner-freebsd-net@FreeBSD.ORG Fri May 28 01:41:38 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D23516A4CF for ; Fri, 28 May 2004 01:41:37 -0700 (PDT) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DE7943D1D for ; Fri, 28 May 2004 01:41:33 -0700 (PDT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.9p2/8.12.9) with ESMTP id i4S8eh3F080373; Fri, 28 May 2004 12:40:43 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.9p2/8.12.9/Submit) id i4S8egY8080372; Fri, 28 May 2004 12:40:42 +0400 (MSD) (envelope-from yar) Date: Fri, 28 May 2004 12:40:42 +0400 From: Yar Tikhiy To: Brooks Davis Message-ID: <20040528084042.GG76909@comp.chem.msu.su> References: <200405251449.i4PEnkIa098672@repoman.freebsd.org> <20040525164251.GA3245@ip.net.ua> <20040525173458.GA18554@comp.chem.msu.su> <20040525184757.GA5546@ip.net.ua> <20040526032055.GA42697@comp.chem.msu.su> <20040526064152.GD24738@cell.sick.ru> <20040527141055.GA32704@comp.chem.msu.su> <20040527150228.GB30789@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040527150228.GB30789@Odin.AC.HMC.Edu> User-Agent: Mutt/1.5.6i cc: net@freebsd.org Subject: Re: VLAN_MTU (was Re: cvs commit: src/sys/dev/fxp if_fxp.c if_fxpvar.h) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2004 08:41:38 -0000 On Thu, May 27, 2004 at 08:02:28AM -0700, Brooks Davis wrote: > > > > Y> Another way I see is to drop automatic fiddling with VLAN_MTU in > > > Y> the first place and implement an option for ifconfig(8) so that a > > > Y> user/admin can control the capability WRT a particular case, e.g., > > > Y> disable it if a NIC displays erroneous behaviour in long frame mode. > > > > > > From my point of view this is a good idea. > > > > The longer I've been thinking of the issue, the more I'm inclined > > to take the latter path. I believe that it would conform to the > > good tradition of Unix to offer a user as much control as possible > > and avoid doing "automagic" tricks behind user's back. > > > > Therefore I'd like to ask the community: Would anybody mind if > > vlan(4) gave up playing with VLAN_MTU on parent interfaces > > while a new option to ifconfig(8), say `vlanmtu', was introduced > > so that a user could control the feature manually? > > This seems OK as long as you enabled VLAN_MTU by default as I see you > have just done with fxp. Thanks for your comment! Presently all our network interfaces supporting VLAN_MTU have it enabled by default. -- Yar