From: Corey Hickey <bugfood-ml@fatooh.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing Load balancing and traffic shaping through 2
Date: Fri, 01 Apr 2005 05:07:05 +0000 [thread overview]
Message-ID: <424CD6F9.10403@fatooh.org> (raw)
Joao Carneiro - DLS wrote:
> I have a couple of internet links: a leased line of 256kbit/s and
> an ADSL line of 1024kbit/s.
What is the upload speed of your ADSL line? ...and the leased line is
symmetric, right; i.e. 256kbit down and 256kbit up?
> What kernel is the most appropriate for this job?
Having used both 2.4.x and 2.6.x on a very busy router doing that sort
of thing, I would say that they are equal for the task in terms of
stability. Other people's opinions will vary. :) Most new development is
for 2.6 these days, so I'd say go with 2.6.
> By reading the howto I found one example that's clearly what I have:
> http://lartc.org/howto/lartc.rpdb.multiple-links.html
>
Since you have two very dissimilar lines, I would tentatively recommend
routing traffic based upon your users' needs for bandwidth and latency.
Without knowing what kind of users you have I can't recommend anything,
but I can loosely describe a setup I used to administrate.
ADSL line: 6000kbit down, 600kbit up
- local web browsing/downloads
- local streaming video viewing
SDSL line: 1300kbit up, 1300kbit down
* high priority, low bandwidth queue
- internet games
* medium priority, high bandwidth queue
- incoming connections to our servers
- ssh
- email
* low priority, any-remaining bandwidth queue
- p2p traffic
- unrecognized traffic
* lowest priority, almost no bandwidth queue
- bofh :-)
Your setup is different and your users probably have different usage
patterns, but there's a lot of flexibility in this general approach. If
you provide more details I may be able to help further.
-Corey
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2005-04-01 5:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=424CD6F9.10403@fatooh.org \
--to=bugfood-ml@fatooh.org \
--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.