From: Christoph Schulz <develop@kristov.de>
To: linux-ppp@vger.kernel.org
Subject: Re: ppp_async: ioctl to set MTU needed
Date: Tue, 13 Jan 2015 21:56:33 +0000 [thread overview]
Message-ID: <20150113225633.17486bmcnrxa4osx@berry.schulz.ip-v6.eu> (raw)
In-Reply-To: <54B556D0.5090204@mirix.org>
Hello!
James Carlson schrieb am Tue, 13 Jan 2015 16:31:29 -0500:
> Not so much "wrong" as "pointless." Why bother to ask for less? You
> don't have to pad the packets out to the full MRU, so why do you care
> what the peer has advertised as a maximum? All that matters is that (by
> acking the value) you've promised not to send anything bigger. By
> adhering to a smaller limit, you're certainly in compliance with the
> peer's limitations.
Yes. However, the problem lies in the mechanism the Linux kernel
determines the MTU of a link in a multilink bundle: It simply takes
the peer's MRU we ACKed. Obviously this is not correct if we are bound
to use a smaller (channel) MTU due to other constraints (tunnel
overhead). But there is currently no possibility to tell the Linux
kernel what channel MTU to use.
Regards,
Christoph Schulz
next prev parent reply other threads:[~2015-01-13 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 17:33 ppp_async: ioctl to set MTU needed Matthias-Christian Ott
2015-01-13 20:30 ` James Carlson
2015-01-13 20:57 ` Christoph Schulz
2015-01-13 21:31 ` James Carlson
2015-01-13 21:56 ` Christoph Schulz [this message]
2015-01-13 22:22 ` James Carlson
2015-01-13 22:56 ` Christoph Schulz
2015-01-13 23:04 ` Christoph Schulz
2015-01-13 23:24 ` Matthias-Christian Ott
2015-01-13 23:39 ` Matthias-Christian Ott
2015-01-14 0:10 ` James Carlson
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=20150113225633.17486bmcnrxa4osx@berry.schulz.ip-v6.eu \
--to=develop@kristov.de \
--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).