VLAN_MTU (was Re: cvs commit: src/sys/dev/fxp if_fxp.c if_fxpvar.h)

Yar Tikhiy yar at comp.chem.msu.su
Fri May 28 08:41:38 GMT 2004


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


More information about the freebsd-net mailing list