From: David Woodhouse <dwmw2@infradead.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, uweber@astaro.com
Subject: Re: Routing over multiple interfaces
Date: Wed, 10 Nov 2010 15:51:01 +0000 [thread overview]
Message-ID: <1289404262.8076.13.camel@i7.infradead.org> (raw)
In-Reply-To: <1289401704.2860.182.camel@edumazet-laptop>
On Wed, 2010-11-10 at 16:08 +0100, Eric Dumazet wrote:
> Its a bit problematic, as you said you want to use both links to do
> one upload ;)
When it's *necessary*, yes :)
> Maybe it is possible to instruct teql to try to not change links
> unless one link is full...
Hm... teql doesn't have any visibility into which packets belong to
which flow, does it?
Perhaps the answer is based on my previous setup ('ip route add default
src 90.155.92.214 nexthop dev ppp0 nexthop dev ppp1'). That would
naturally distribute connections between the interfaces, so all we need
on top is a qdisc which will move packets from one interface to the
other when one queue becomes full (or at a given rate limit).
--
dwmw2
next prev parent reply other threads:[~2010-11-10 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 21:12 Routing over multiple interfaces David Woodhouse
2010-11-01 21:16 ` 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 [this message]
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=1289404262.8076.13.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=uweber@astaro.com \
/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).