From: Christopher Schramm <netdev@shakaweb.org>
To: Rami Rosen <roszenrami@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: ip_rt_min_pmtu
Date: Wed, 05 Dec 2012 10:33:43 +0100 [thread overview]
Message-ID: <50BF14F7.8060105@shakaweb.org> (raw)
In-Reply-To: <CAKoUArn0EYaeebFXtCgqDSYeJD2oFKUfns7Lbk7Rsg=N=pnpHA@mail.gmail.com>
On Wed, 05 Dec 2012 09:46:18 +0100, Rami Rosen wrote:
> But RFC 791 also declares 576 as PMTU:
> "All hosts must be prepared to accept datagrams of up to 576 octets".
That's the common mistake I mentioned. The sentence goes on: "(whether
they arrive whole or in fragments)", so it says nothing about lower
layers, especially not about the MTU.
The 576 octects IP datagram every implementation is required to be able
to handle could be transferred in 12 up to over 60 fragments if we had
the minimal PMTU of 68, depending on the header size. Of course that
leads to an overhead of nearly 90 percent, but it should be possible
following the RFC.
With Linux, trying to send large data over a path with PMTU < 552 will
probably fail (unless you change the min_pmtu value).
prev parent reply other threads:[~2012-12-05 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 21:04 ip_rt_min_pmtu Christopher Schramm
2012-12-05 8:46 ` ip_rt_min_pmtu Rami Rosen
2012-12-05 9:33 ` Christopher Schramm [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=50BF14F7.8060105@shakaweb.org \
--to=netdev@shakaweb.org \
--cc=netdev@vger.kernel.org \
--cc=roszenrami@gmail.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).