netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: netdev@vger.kernel.org
Subject: Routing over multiple interfaces
Date: Mon, 01 Nov 2010 17:12:02 -0400	[thread overview]
Message-ID: <1288645922.5977.41.camel@macbook.infradead.org> (raw)

I have two ADSL lines, and the ISP routes the same set of addresses over
both of them -- so I can saturate my incoming bandwidth over both lines
with a single TCP connection. This is not MLPPP; just two separate PPP
connections.

TCP can cope with a little bit of packet re-ordering, which obviously
happens when packets come over both lines.

Everything works really well for downstream traffic -- but not so well
for upstream, because Linux doesn't use the full available upstream
bandwidth. I have the default route set up thus:

default  src 90.155.92.214 
	nexthop dev ppp0 weight 1
	nexthop dev ppp1 weight 1

But when I do a large upload, I find that the kernel is only ever using
a *single* link at a time, rather than both. How can I make it use
*both* links? It's fine to confine each flow to a single link if it
doesn't saturate that link... but once the queue is full, it should
overflow onto the other device.

I worked around this earlier today by splitting the large file I needed
to upload into two parts, shifting one of them to a *different* machine,
connecting that to the VPN too and then uploading the two parts
separately. But that isn't really a viable option in the general case.

-- 
dwmw2


             reply	other threads:[~2010-11-01 21:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 21:12 David Woodhouse [this message]
2010-11-01 21:16 ` Routing over multiple interfaces David Miller
2010-11-01 21:35   ` Eric Dumazet
2010-11-01 22:15     ` David Woodhouse
2010-11-02 19:46     ` Pascal Hambourg
2010-11-02 20:04       ` Eric Dumazet
2010-11-02 22:56         ` Pascal Hambourg
2010-11-10 14:50     ` David Woodhouse
2010-11-10 15:08       ` Eric Dumazet
2010-11-10 15:51         ` David Woodhouse
2010-11-02 18:47   ` Bandan Das
2010-11-02 22:10   ` Arnd Hannemann
2010-11-04 12:51     ` Patrick Schaaf
2010-11-04 14:01       ` Eric Dumazet
2010-11-01 21:21 ` Benjamin LaHaise

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=1288645922.5977.41.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=netdev@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).