From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bonding of 2 lines
Date: Mon, 30 Jul 2007 18:31:33 +0000 [thread overview]
Message-ID: <46AE2E85.1070001@riverviewtech.net> (raw)
In-Reply-To: <253C3920940FF849ACA6FAFE18044BDA180645@tgs-mail.gamesyndicate.nl>
On 07/30/07 09:15, Laurence vd Krieken wrote:
> I am working on a test-project at the moment, in witch I want to
> actually bundle ('trunk') some connections. In the LARTC-manual I
> found the chapter about TEQL (see chapter 10). The situation in that
> example is too link 2 networks. I need to link a network to 1 remote
> gateway.
I don't think you will get Teql to do what you are wanting it to do. It
is my understanding that Teql is meant to load balance across serial links.
> The main goal is that 'network 1' can use the full network speed
> (4mbit/s up/down) of both connections. (2x 2mbit SDSL)
The first thing that comes to mind is PPP Multi-Linking. Establish an
L2TP / PPtP tunnel between your to end nodes and then have PPP bond the
two tunnels together. This use to be called "Shotgunning" with dial up
and T1s. There is however no reason why it can not be done with VPNs.
The other (preferred) option that comes to mind would be Equal Cost
Multi Path routing (and the associated config(s) and / or patch(s)).
Seeing as how you do have two equal cost routes that you want to spread
traffic across, this should be possible. However getting it set up
right will be a bit tricky.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-07-30 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 14:15 [LARTC] bonding of 2 lines Laurence vd Krieken
2007-07-30 18:31 ` Grant Taylor [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=46AE2E85.1070001@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.