On Mon, Jun 25, 2001 at 05:23:18PM -0500, Jonathan Lemon wrote:
> On Tue, Jun 26, 2001 at 07:56:24AM +1000, Peter Jeremy wrote:
> > On 2001-Jun-25 14:25:42 -0500, Jonathan Lemon <[EMAIL PROTECTED]> wrote:
> > >On Mon, Jun 25, 2001 at 11:02:55PM +0400, Yar Tikhiy wrote:
> > >>
> > >> While more and more Ethernet NIC drivers start supporting long
> > >> frames (>1518 bytes), the user/admin still cannot raise MTU on an
> > >> Ethernet interface above the 1500 byte limit due to outdated code
> > >> in net/if_ethersubr.c
> > [patch removed]
> >
> > >I'm not at all sure how this change will help anything, unless each
> > >driver alters if_hdrlen.
> >
> > One benefit is for 802.1Q VLAN support - the existence of lots of
> > hard-wired values that restrict frames to 1518 bytes makes configuring
> > VLAN's a pain. It would be nice if attaching a vlan(4) to a driver that
> > handled 1522 byte frames resulted in a 1500 byte MTU on the vlan.
>
> Maybe I'm being dense here, but even with 1522 byte frames, the MTU
> of the device should still be 1500. MTU in this context applies to IP,
> so it wouldn't include either the vlan header or the ethernet header.
You have a point there! I mistook the layer 3 (IP, IPX etc) MTU
for the physical MTU of the ethernet NIC, which is rather high by
default for many adapter types, unlike MRU. To run VLANs, one don't
need to increase the IP MTU on the trunk interface. So I recall
the patch, sorry.
-- Yar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
