From: Ivo Vachkov <ivo@unilans.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] load balancing
Date: Fri, 28 Nov 2003 12:38:17 +0000 [thread overview]
Message-ID: <marc-lartc-107002548231041@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102512835209719@msgid-missing>
Евгени Гечев wrote:
> Hi!
> Can somebody tell what is the best way for load balancing with one ISP.
> Here is the scenario (there is a LAN behind the wireless clients):
>
> linux wireless client--------\
> ---Access Point (Orinoco
> AP1000)----linux router----ISP
> linux wireless client--------/
>
> The two wireless clients are connected to the two different wireless
> interfaces of the Access Point.
> They could be two PC's or one PC with two wi-fi cards (I don't think it
> matters). Since the configuration is in use now it is not recommended to
> make very long lasting experiments:).
> The idea is to balance (increase) the speed for the PC's behind the
> wireless client(s). Single wireless client achieves 5Mbit/s, but is
> shaped to 4 Mbit/s since at 5Mbit there is big lag, so a PC in the LAN
> when using static routes can't use more than 4Mbit even the other
> channel is free.
I would probably use CBQ + [e]SFQ. You can define classes for both linux
wireless clients on the linux router which borrow traffic between each
other and use [e]SFQ to equal connection speed inside these classes; or
the [e]SFQ part may run on the linux wireless clients
> Has somebody some experience with similar configuration, and what is the
> best solution:
> (t)eql, multipath routing, some variant of bonding, something else?
multipath routing ... where you find multipath routes on that picture ?
bonding ... it's applied in
PC1 | NIC | - - - - - - - - | NIC | PC2
| NIC | - - - - - - - - | NIC |
enviroment.
> Is it at all possible to use bonding in such situation?
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-11-28 12:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 21:52 [LARTC] Load balancing Greg Scott
2002-06-28 5:27 ` William L. Thomson Jr.
2002-07-04 14:52 ` bert hubert
2003-02-19 19:27 ` Paul English
2003-05-08 11:50 ` [LARTC] load balancing Lucas Aimaretto
2003-05-08 13:08 ` Sjaak Nabuurs
2003-05-09 15:44 ` Víctor Nuño
2003-05-09 15:55 ` Martin A. Brown
2003-11-28 1:41 ` Евгени Гечев
2003-11-28 12:38 ` Ivo Vachkov [this message]
2003-11-28 18:47 ` Evgeni Gechev
2003-11-28 19:02 ` Artūras Šlajus
2003-11-28 23:22 ` Ivo Vachkov
2004-07-26 1:35 ` [LARTC] Load Balancing XMundo - Soporte Tecnico
2004-07-26 23:58 ` XMundo - Soporte Tecnico
2004-09-15 17:10 ` [LARTC] load balancing pbruna
2004-09-17 3:21 ` Glen Mabey
2005-01-12 21:15 ` Antonio Pérez
2005-11-16 20:13 ` comp.techs
2006-10-13 8:54 ` Indunil Jayasooriya
2006-10-13 8:55 ` Indunil Jayasooriya
2006-12-13 22:07 ` Charlie Meyer
2006-12-13 22:42 ` Grant Taylor
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-107002548231041@msgid-missing \
--to=ivo@unilans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox