linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 22:56:25 +0000	[thread overview]
Message-ID: <20150113235625.442050ugwhi2l121@berry.schulz.ip-v6.eu> (raw)
In-Reply-To: <54B556D0.5090204@mirix.org>

Hello!

James Carlson schrieb am Tue, 13 Jan 2015 17:22:47 -0500:

> Ah, ok.  Are you referring to the individual link MTU rather than the
> bundle's overall MTU?

Yes.

>
> If so, then, yes, that does look like a problem.  It should be possible
> to limit individual link MTU values as desired, but I don't see a good
> way to do it.

Me neither, at least without introducing a system-specific ioctl that  
would have to be explicitly called by pppd. However, perhaps anyone  
has a better idea...

By the way, how does Solaris solve this problem? I see that PPPIO_MTU  
is sent in tty_send_config() in sys-solaris.c for setting the link  
MTU. Is that used when doing multilink PPP? The corresponding function  
in sys-linux.c does not send the link MTU to the kernel, it only saves  
the value in a global static variable "link_mtu" (line 1250) which is  
not used anywhere else.

>
> But, for what it's worth, running MP over a tunneled link sounds like
> extreme weirdness to me.  Unless you're trying to set new records for
> packet loss and link latency, why would you do that?

Don't ask me, ask Matthias-Christian ;-)

But nevertheless there is no obvious reason why it should be  
impossible to make it work.


Regards,

Christoph


  parent reply	other threads:[~2015-01-13 22: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
2015-01-13 22:22 ` James Carlson
2015-01-13 22:56 ` Christoph Schulz [this message]
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=20150113235625.442050ugwhi2l121@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).