From: Frank Cusack <fcusack@fcusack.com>
To: linux-ppp@vger.kernel.org
Subject: Re: ppp-2.4.2 released
Date: Mon, 02 Feb 2004 09:27:03 +0000 [thread overview]
Message-ID: <20040202012703.A1937@google.com> (raw)
In-Reply-To: <16391.33929.908463.444449@cargo.ozlabs.ibm.com>
On Sat, Jan 17, 2004 at 12:45:18PM +0200, Pasi K?rkk?inen wrote:
> On Sat, Jan 17, 2004 at 10:18:24AM +1100, Paul Mackerras wrote:
> > Pasi Kärkkäinen writes:
> >
> > > There's still the MTU bug (with MPPE) left..
What bug is that?
> > Well, somehow we have to allow for the extra 4 bytes that MPPE adds -
> > and it is reasonable and valid to have the network interface MTU be
> > smaller than the PPP mtu/mru values. Arguably the code that reduces
> > the MTU isn't expressed as well as it could be, but I'm not yet
> > convinced it's actually wrong.
> >
>
> Hmm.. I'm not very familiar with MPPE internals, but anyway this seems to
> cause problems in PMTUD with many web sites.. blocking access to them
> entirely.
>
> Are there any other opensource ppp/mppe packages that could be used to check
> how this in handled in them..
Everyone else ignores MTU and requires the user to manually set it. If
the user does not set it, the peer sends frames which are too large, and
just expects that the receiver will handle it.
> > Frank, what is your opinion?
One choice would be to require MPP and send frags when we PPP frame
would be too large. Reducing the interface MTU seems better.
How does this create a PMTU-D problem?
/fc
next prev parent reply other threads:[~2004-02-02 9:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 6:28 ppp-2.4.2 released Paul Mackerras
2004-01-16 8:48 ` Pasi Kärkkäinen
2004-01-16 12:16 ` Clive Nicolson
2004-01-16 16:21 ` Arvin Schnell
2004-01-16 22:57 ` Paul Mackerras
2004-01-16 23:18 ` Bill Unruh
2004-01-16 23:18 ` Paul Mackerras
2004-01-17 10:45 ` Pasi Kärkkäinen
2004-01-18 4:10 ` Jan Dubiec
2004-02-02 9:27 ` Frank Cusack [this message]
2004-02-02 9:34 ` Frank Cusack
2004-02-02 10:56 ` Pasi Kärkkäinen
2004-02-02 18:09 ` Frank Cusack
2004-02-02 23:11 ` James Cameron
2004-02-03 11:17 ` Pasi Kärkkäinen
2004-02-03 11:24 ` Pasi Kärkkäinen
2004-02-03 14:33 ` Frank Cusack
2004-02-03 15:10 ` Pasi Kärkkäinen
2004-02-03 15:13 ` Frank Cusack
2004-02-03 16:24 ` Andy Gay
2004-02-03 16:25 ` Frank Cusack
2004-02-03 22:01 ` James Cameron
2004-02-03 22:11 ` James Cameron
2004-02-04 12:58 ` Pasi Kärkkäinen
2004-02-04 13:00 ` Pasi Kärkkäinen
2004-02-04 13:01 ` Pasi Kärkkäinen
2004-03-02 23:13 ` Bernard Blackham
2004-03-03 9:09 ` Pasi Kärkkäinen
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=20040202012703.A1937@google.com \
--to=fcusack@fcusack.com \
--cc=linux-ppp@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 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).