Linux PPP protocol development
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: ppp_async: ioctl to set MTU needed
Date: Wed, 14 Jan 2015 00:10:35 +0000	[thread overview]
Message-ID: <54B5B3FB.8010801@workingcode.com> (raw)
In-Reply-To: <54B556D0.5090204@mirix.org>

On 1/13/2015 6:04 PM, Christoph Schulz wrote:
> Hello!
> 
> Christoph Schulz schrieb am Tue, 13 Jan 2015 23:56:25 +0100:
> 
>> By the way, how does Solaris solve this problem? [...]
> 
> Never mind, I forgot that pppd supports multilink PPP only under Linux.

Yes, exactly.  At Sun, we had a multilink implementation, but there
wasn't much call for it.  The best reason to use MP is to bond together
the two B channels in Basic-Rate ISDN or two or more B channels in
Primary-Rate ISDN.  Those links tend to be tightly controlled in terms
of delay and error rate, so they work well for MP.

And not many people ended up caring too much about ISDN.  (Yeah, I know
there are still aficionados out there ...)

If because the segmentation/reassembly process in MP works only as well
as the worst-performing link, it tends to be an overall loss if you have
links that differ.

A better plan is to use multipath IP routes -- ECMP across multiple
independent ordinary (non-MP) PPP links -- if you have links that differ.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

      parent reply	other threads:[~2015-01-14  0:10 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
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 [this message]

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=54B5B3FB.8010801@workingcode.com \
    --to=carlsonj@workingcode.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