mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: kuznet@ms2.inr.ac.ru
Cc: roger@kea.GRace.CRi.NZ, linux-kernel@vger.kernel.org
Subject: Re: MTU and 2.4.x kernel
Date: Thu, 15 Feb 2001 18:47:31 +0000 (GMT)	[thread overview]
Message-ID: <E14TTRF-0000Ul-00@the-village.bc.nu> (raw)
In-Reply-To: <200102151821.VAA19711@ms2.inr.ac.ru> from "kuznet@ms2.inr.ac.ru" at Feb 15, 2001 09:21:28 PM

> 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.

Please cite an exact RFC reference.

The 576 byte requirement is for reassembled packets handled by the host.
That is if you send a 576 byte frame you know the other end will be able
to put it back together. Our handling of DF on syn frames is also broken
due to that misassumption, but fortunately only for crazy mtus like 70.

Alan


  reply	other threads:[~2001-02-15 18:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14 20:39 roger
2001-02-14 20:51 ` Alan Cox
2001-02-15 18:21 ` kuznet
2001-02-15 18:47   ` Alan Cox [this message]
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

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=E14TTRF-0000Ul-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®