From: Glen Turner <glen.turner@aarnet.edu.au>
To: Sven-Haegar Koch <haegar@sdinet.de>
Cc: netdev@oss.sgi.com
Subject: Re: Problem with e100.c and packets >mtu in 2.6.4
Date: Mon, 15 Mar 2004 11:59:26 +1030 [thread overview]
Message-ID: <1079314166.5676.103.camel@andromache> (raw)
In-Reply-To: <Pine.LNX.4.58.0403150035530.27707@mercury.sdinet.de>
> What is the reason behind this check? Could it be removed from the
> official sources again?
Alternatively, I'd like to suggest that too-big frames
be discarded by all drivers.
The configuration described (an inconsistent MTU in
a subnet) is wrong and having it fail-and-count rather
than subtly "work" (eg, frames up to some hardware-dependent
magic number are received but can't be sent, but frames
beyond that don't) is a significant help to network
operators.
Those operators then just need to know the RFCs, not
the inner details of the popular NICs and their drivers.
--
Glen Turner Tel: (08) 8303 3936 or +61 8 8303 3936
Network Engineer Email: glen.turner@aarnet.edu.au
Australian Academic & Research Network www.aarnet.edu.au
prev parent reply other threads:[~2004-03-15 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 23:51 Problem with e100.c and packets >mtu in 2.6.4 Sven-Haegar Koch
2004-03-15 1:29 ` Glen Turner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1079314166.5676.103.camel@andromache \
--to=glen.turner@aarnet.edu.au \
--cc=haegar@sdinet.de \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).