From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Sharing bandwidth
Date: Fri, 18 Jun 2004 17:34:57 +0000 [thread overview]
Message-ID: <40D327C1.1080107@wildgooses.com> (raw)
In-Reply-To: <40D30F07.2050703@atlascollege.nl>
Peter Kaagman wrote:
> Hi there,
>
> I've got the following problem on my hand.....
> I'm a sysop for a school in the netherlands. We have a network with 5
> different schools (and 1 administration). Each of those have their own
> ip range in the private network (10.4.0.0 10.5.0.0 and so on).
> For all these schools we have an internet uplink of 2mbit. And this
> bandwidth should be shared as fairly as possible.
>
> So I started reading the the lartc HOWTO but was startled by the
> technical terms I found there...... I kinda understand what i
> meant..... but would like some advice which option I should further
> investigate.
>
> What I want to do is spit up the 2mbit pipe in 6. Guarantee 1/6 of the
> bandwidth per network and allowing more if it is availlable.
>
> Is this possible? If so which traffic control scheme should I
> investigate?
As was suggested, HTB is your friend, with perhaps an SFQ or ESFQ attached.
However, it's worth just ploughing on with the LARTC readme - at the end
of that you will be an expert in the subject, and it only looks hard
when you start (keep going and reread it).
For scripts, I think that this one is by far the best starting point.
It's got just about everything in, and although it's designed for a
single user, I think with the help of LARTC you can modify it for your
network, and the incoming part is really quite powerful
http://digriz.org.uk/jdg-qos-script/
Good luck
Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-18 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 15:49 [LARTC] Sharing bandwidth Peter Kaagman
2004-06-18 16:07 ` Ben
2004-06-18 17:34 ` Ed Wildgoose [this message]
2004-06-18 21:07 ` Peter Kaagman
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=40D327C1.1080107@wildgooses.com \
--to=lists@wildgooses.com \
--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.