From: Pekka Pietikainen <pp@netppl.fi>
To: Carlos Velasco <carlosev@newipnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 Broken Path MTU Discovery?
Date: Mon, 3 Feb 2003 02:23:02 +0200 [thread overview]
Message-ID: <20030203002302.GA32336@netppl.fi> (raw)
In-Reply-To: <200302030108240978.2B66BB7E@192.168.128.16>
On Mon, Feb 03, 2003 at 01:08:24AM +0100, Carlos Velasco wrote:
> *Info added*
>
> This issue is not shown when MTU in router is 600 or bigger.
> If I set router MTU to 500 the problem is as show below.
See /proc/sys/net/ipv4/route/min_pmtu, which defaults to 552.
And there's a perfectly good reason to have a minimum value,
guess what happens if someone starts spoofing fragmentation needed
packets that suggest a MTU of 68 bytes would be appropriate?
next prev parent reply other threads:[~2003-02-03 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-02 18:58 2.4.20 Broken Path MTU Discovery? Carlos Velasco
2003-02-03 0:08 ` Carlos Velasco
2003-02-03 0:23 ` Pekka Pietikainen [this message]
[not found] <200302021958160177.2A4B5622@192.168.128.16.suse.lists.linux.kernel>
2003-02-03 0:29 ` Andi Kleen
[not found] ` <1044279732.20152.6.camel@irongate.swansea.linux.org.uk>
2003-02-03 14:45 ` Carlos Velasco
2003-02-04 6:54 ` David S. Miller
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=20030203002302.GA32336@netppl.fi \
--to=pp@netppl.fi \
--cc=carlosev@newipnet.com \
--cc=linux-kernel@vger.kernel.org \
/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.