From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Per-connection routing for multiple uplinks/providers
Date: Tue, 16 Apr 2002 13:57:25 +0000 [thread overview]
Message-ID: <marc-lartc-101896551429662@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101890143014670@msgid-missing>
Mihai RUSU wrote:
> I wont recommend the round robin packet load balancing as that would do
> more problems with TCP connections, asymetric routing , RTT values.
I guess if you'd use multiple connections to the same ISP (and same
access point) that would solve the problems of different RTT values.
Otherwise i can confirm there are problems, i had a lot more (needless)
retransmits using a dsl + two isdn links which was probably due to very
different RTT on both links.
> Cisco recommends the per destination load balancing solution. I think if
It's not always practical. For example in my case one of the links is
asymetric (256k upstresm/1mbit downstream), the other isn't. So
distributing traffic with a normal multipath route would result in some
connections (maybe downloads) beeing on the link with slow downstream.
Bye,
Patrick
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-04-16 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 20:08 [LARTC] Per-connection routing for multiple uplinks/providers ?? Bob Gustafson
2002-04-15 21:55 ` [LARTC] Per-connection routing for multiple uplinks/providers Arthur van Leeuwen
2002-04-16 6:01 ` Bob Gustafson
2002-04-16 6:56 ` Arthur van Leeuwen
2002-04-16 11:48 ` Patrick McHardy
2002-04-16 13:38 ` Mihai RUSU
2002-04-16 13:57 ` Patrick McHardy [this message]
2002-04-16 14:14 ` Mihai RUSU
2002-04-16 20:01 ` Bob Gustafson
2002-04-16 20:26 ` Don Cohen
2002-04-16 21:38 ` Bob Gustafson
2002-04-28 15:27 ` [LARTC] Per-connection routing for multiple uplinks/providers ?? mikee
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=marc-lartc-101896551429662@msgid-missing \
--to=kaber@trash.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.