All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bandwidth aggregation between 2 hosts in the same subnet
Date: Tue, 31 Jul 2007 15:25:57 +0000	[thread overview]
Message-ID: <46AF5485.1030205@riverviewtech.net> (raw)
In-Reply-To: <20070730141010.GA27667@p15145560.pureserver.info>

On 07/31/07 06:01, Ralf Gross wrote:
> But I don't have an isolated network. Maybe I'm still too blind to 
> see a simple solution.

This is why Paul's solution, though accurate, will not work in your 
scenario.

The fact that you are trying to go across an aggregated link in the 
middle between the two buildings where you have no control is going to 
hinder you severely.

The only other nasty thing that comes to mind is to assign additional 
MAC / IP sets to each system on their second interfaces.  Establish 
IP-IP (?) tunnels between the two systems via each pair of MAC / IP 
sets.  I.e. Machine A Primary MAC / IP set to machine B Primary MAC / IP 
set and Machine A Secondary MAC / IP set to machine B Secondary MAC / IP 
set.  Thus yielding two tunnels between the two machines.  Then if you 
were trying to get to an IP address that could be routed by the IP 
address at the end of either tunnel, you could then use something like 
Equal Cost Multi Path (a.k.a. ECMP) routing to send packets down both 
routes.  Seeing as how the traffic you are sending will be encapsulated 
in IP-IP tunnel packets, each of which should be between its own MAC / 
IP sets, the switch(s) so the switches should not cause a problem by 
doing what they are doing.



Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-07-31 15:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 14:10 [LARTC] bandwidth aggregation between 2 hosts in the same subnet Ralf Gross
2007-07-30 18:44 ` Grant Taylor
2007-07-30 18:46 ` Paul Zirnik
2007-07-30 20:12 ` Ralf Gross
2007-07-30 20:48 ` Ralf Gross
2007-07-30 21:19 ` Grant Taylor
2007-07-30 21:22 ` Grant Taylor
2007-07-31  7:52 ` Paul Zirnik
2007-07-31  8:05 ` Ralf Gross
2007-07-31 11:01 ` Ralf Gross
2007-07-31 15:25 ` Grant Taylor [this message]
2007-07-31 15:31 ` Ralf Gross
2007-07-31 16:31 ` Grant Taylor
2007-07-31 19:58 ` Jay Vosburgh
2007-07-31 21:00 ` Ralf Gross
2007-08-21 16:31 ` Ralf Gross

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=46AF5485.1030205@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.