Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 06 Jan 2003 10:02:38 -0700 (MST)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        eyurtese@turkuamk.fi
Cc:        sten.daniel.sorsdal@wan.no, michaelx.l.wright@intel.com, fkittred@gwi.net, kudzu@tenebras.com, dmagda@ee.ryerson.ca, freebsd-stable@FreeBSD.ORG, wpaul@ctr.columbia.edu
Subject:   Re: wi0 and mtu setting [bad idea]
Message-ID:  <20030106.100238.69366019.imp@bsdimp.com>
In-Reply-To: <Pine.A41.4.10.10301041436440.19242-100000@bessel.tekniikka.turkuamk.fi>
References:  <0AF1BBDF1218F14E9B4CCE414744E70F07DE29@exchange.wanglobal.net> <Pine.A41.4.10.10301041436440.19242-100000@bessel.tekniikka.turkuamk.fi>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <Pine.A41.4.10.10301041436440.19242-100000@bessel.tekniikka.turkuamk.fi>
            Evren Yurtesen <eyurtese@turkuamk.fi> writes:
: Yes, actually this is why I asked first about MTU settings in wi. I use
: PPPoE and it has 8bytes overhead. It could be nice to set MTU to 1508 so
: 1500 byte ethernet frames can be encapsualted in PPPoE without
: fragmentation.
: 
: I just dont understand why FreeBSD people have to make this wi driver so
: tight in standarts even though there are wireless cards which support
: non-standard(and sometimes nice) things which can be useful. I definetely
: disagree that something should be in standard so you will allow setting of
: it!

Dude, you are being way too confrontational here.  Since I am the wi
driver maintainer, and I haven't said I wouldn't support this, you are
just being an ass rather than doing things in a way that would
motivate people to allow you the flexibility to do.

I'm not conversant on all the technical issues, but so far I've missed
patches that I could test to see if they cause problems or not.

Warner

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030106.100238.69366019.imp>