From: Jordan Mendelson <jordy@napster.com>
To: Rick Jones <raj@cup.hp.com>
Cc: kuznet@ms2.inr.ac.ru, roger@kea.GRace.CRi.NZ,
linux-kernel@vger.kernel.org
Subject: Re: MTU and 2.4.x kernel
Date: Thu, 15 Feb 2001 12:54:26 -0800 [thread overview]
Message-ID: <3A8C4202.83C197D6@napster.com> (raw)
In-Reply-To: <200102151821.VAA19711@ms2.inr.ac.ru> <3A8C3EB5.BAB148B0@cup.hp.com>
Rick Jones wrote:
>
> > Default of 536 is sadistic (and apaprently will be changed eventually
> > to stop tears of poor people whose providers not only supply them
> > with bogus mtu values sort of 552 or even 296, but also jailed them
> > to some proxy or masquearding domain), but it is still right: IP
> > with mtu lower 576 is not full functional.
>
> I thought that the specs said that 576 was the "minimum maximum"
> reassemblable IP datagram size and not a minimum MTU.
RFC 1191 (Path MTU Discovery as it happens):
Plateau MTU Comments Reference
------ --- -------- ---------
65535 Official maximum MTU RFC 791
65535 Hyperchannel RFC 1044
65535
32000 Just in case
17914 16Mb IBM Token Ring ref. [6]
17914
8166 IEEE 802.4 RFC 1042
8166
4464 IEEE 802.5 (4Mb max) RFC 1042
4352 FDDI (Revised) RFC 1188
4352 (1%)
2048 Wideband Network RFC 907
2002 IEEE 802.5 (4Mb recommended) RFC 1042
2002 (2%)
1536 Exp. Ethernet Nets RFC 895
1500 Ethernet Networks RFC 894
1500 Point-to-Point (default) RFC 1134
1492 IEEE 802.3 RFC 1042
1492 (3%)
1006 SLIP RFC 1055
1006 ARPANET BBN 1822
1006
576 X.25 Networks RFC 877
544 DEC IP Portal ref. [10]
512 NETBIOS RFC 1088
508 IEEE 802/Source-Rt Bridge RFC 1042
508 ARCNET RFC 1051
508 (13%)
296 Point-to-Point (low delay) RFC 1144
296
68 Official minimum MTU RFC 791
Jordan
prev parent reply other threads:[~2001-02-15 20:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 20:39 MTU and 2.4.x kernel roger
2001-02-14 20:51 ` Alan Cox
2001-02-15 18:21 ` kuznet
2001-02-15 18:47 ` Alan Cox
2001-02-15 19:33 ` kuznet
2001-02-15 20:27 ` Alan Cox
2001-02-15 20:41 ` kuznet
2001-02-15 21:01 ` Alan Cox
2001-02-18 19:53 ` kuznet
2001-02-19 1:44 ` Alan Cox
2001-02-19 18:26 ` kuznet
2001-02-19 22:20 ` Rick Jones
2001-02-16 12:54 ` Rik van Riel
2001-02-18 11:26 ` Pierfrancesco Caci
2001-02-16 12:51 ` Rik van Riel
2001-02-18 19:55 ` kuznet
2001-02-18 9:39 ` David S. Miller
2001-02-18 20:17 ` kuznet
2001-02-18 20:32 ` kuznet
2001-02-15 20:40 ` Rick Jones
2001-02-15 20:54 ` Jordan Mendelson [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=3A8C4202.83C197D6@napster.com \
--to=jordy@napster.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=raj@cup.hp.com \
--cc=roger@kea.GRace.CRi.NZ \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.