Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Alessandro Ren <alessandro.ren@opservices.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problem with Load Balancing
Date: Fri, 29 Sep 2006 13:39:34 +0000	[thread overview]
Message-ID: <451D2216.6090804@opservices.com.br> (raw)
In-Reply-To: <BAY116-F9C9A3D94EC858237F43188C2E0@phx.gbl>


    The second connections will problably gets routed though the same 
link because of route cache I think.

    []s.

William T Mullaney wrote:
>
> Well, if you had a download manager and the system at the other side 
> allowed you to start your transfers in the middle of the file (which 
> isn't out of the question) that could potentially work.  The problem 
> is that as far as I see, there's nothing to force the second 
> connection onto the second line.  It's been kind of a crap shoot of 
> what line gets more information.  In theory you could start the first 
> download stream (and it's routed to ISP A), then perhaps your email 
> client goes out to check your POP account, so that goes over ISP B.  
> The next connection, the second stream, now goes out over ISP B 
> again.  Honestly I don't know exactly how the equalize command for ip 
> route works, though I would think it says to always use the "less 
> used" connection (perhaps on PPS, BPS, % use, whatever, on a per 
> second, 30 second, minute average?), but in my experience that and the 
> weight options don't ever get you exactly 50/50 (or whatever you 
> specify) traffic. 
>
> Things like bit torrent would probably perform better because there 
> are (possibly) many streams for each file, as would having 50 people 
> downloading files vs one.  It seems to be just like rolling dice, if 
> you only roll twice you might get two evens or two odds, but if you 
> roll tons of times, you should tend to get a more even distribution.
>
> -Will
>
> -----Original Message-----
> From: Raj Mathur [mailto:raju@linux-delhi.org]
> Sent: Sunday, September 24, 2006 2:49 PM
> To: lartc@mailman.ds9a.nl
> Subject: RE: [LARTC] Problem with Load Balancing
>
> >>>>> "William" = William T Mullaney <William> writes:
>
>     William> To my knowledge, there is no way to download one file
>     William> from two different connections connected to two different
>     William> ISPs at the same time.  If you are running BGP then you
>     William> might be able to load balance across the two links, but
>     William> that would require your upstream providers to allow you
>     William> to use it, and possibly the purchase of a public AS
>     William> number an IP address space depending on the setup.  If
>     William> you are doing NAT past this link (IE both of your lines
>     William> go two the same ISP and same address blocks, but they
>     William> want to give you 2x 10mb links for 20mb total), then you
>     William> can look at doing load balancing on layer 2 (Fast
>     William> EtherChannel, bonding, Link Aggregate Groups, whatever),
>     William> or creating 2 PPP style links between the computers and
>     William> using a routing protocol like OSPF, EIGRP (but not on
>     William> Linux) or something.  I believe OSPF does equal cost load
>     William> balancing, BGP and EIGRP can, I think, do unequal cost
>     William> load balancing.  But either way, I don't think that's the
>     William> solution in your case.
>
>     William> The only other option I can think of would be some sort
>     William> of software that sends every other packet to a different
>     William> IP or something, which would need to run at the end you
>     William> are downloading at or maybe at your ISPs, but I can't
>     William> think of anything like that.
>
> Wouldn't some download manager software that splits the file up into 
> multiple simultaneous downloads do the trick?  Agreed, not a single 
> download across multiple ISPs, but definitely a single file across 
> multiple ISPs.
>
> Regards,
>
> -- Raju
> -- 
> Raj Mathur                raju@kandalaya.org      http://kandalaya.org/
>        GPG: 78D4 FC67 367F 40E2 0DD5  0FEF C968 D0EF CC68 D17F
>                       It is the mind that moves 
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>   
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2006-09-29 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15  2:24 [LARTC] Problem with Load Balancing Vladimir Burciaga Aguilar
2006-09-15  4:12 ` William T Mullaney
2006-09-18 16:09 ` Vladimir Burciaga Aguilar
2006-09-24 18:18 ` William T Mullaney
2006-09-24 18:50 ` Raj Mathur
2006-09-26 18:47 ` William T Mullaney
2006-09-29 13:39 ` Alessandro Ren [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=451D2216.6090804@opservices.com.br \
    --to=alessandro.ren@opservices.com.br \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox