From: Jason Tackaberry <tack@auc.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] share 2Mbit between 90 users - what's sensible?
Date: Sun, 26 Jan 2003 17:18:28 +0000 [thread overview]
Message-ID: <marc-lartc-104360163316270@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104359772213086@msgid-missing>
On Sun, 2003-01-26 at 11:13, Björn Snippe wrote:
> which provides shaping of a 2 Mbit SDSL-Line for about 90 users.
> We have quite a lot of P2P-users (student's dorm *g*), so the link
I have a similar setup. I'm a bit better off -- 3Mbit for our small
campus, which includes about 50-60 dorm users.
I've allocated about 2.2Mbit up/down for the residences, so they can
never exceed that. We have our share of p2p users too. At first I
tried creating a p2p class and assigning known p2p ports to that class,
but it was just too difficult to keep up with it.
> Now I would like to prioritize interactive traffic for every user, too.
> What's the most elegant way to do this? Create 90 more classes with a
> better priority?
What you want is ESFQ (you can google it). This lets you hash based on
source and dest IPs as well. So, instead of creating 90 separate
subclasses, you just attach an esfq qdisc to your htb class that hashes
on source IP for your internet interface, and dest IP for your dorm
interface. When there is competition for bandwidth, it will be shared
evenly between users, no matter how many concurrent sessions they have
running. This means you don't need to make N subclasses for N users.
To improve responsiveness, I put ACKs and SYNs in a separate, high
priority class. With a reasonable burst rate (I use 50k), this means
that things like web browsing is still fairly snappy, even when there is
a fair bit of bandwidth competition going on.
I've been running this (HTB + ESFQ) for many months and am quite happy
with it. So are my users. I still try to educate everyone about
disabling uploading in their p2p programs, which tends to require
constant reminders, but overall they're pretty good.
Cheers,
Jason.
--
Jason Tackaberry :: tack@auc.ca :: 705-949-2301 x330
Academic Computing Support Specialist
Information Technology Services
Algoma University College :: www.auc.ca
_______________________________________________
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-01-26 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-26 16:13 [LARTC] share 2Mbit between 90 users - what's sensible? Björn Snippe
2003-01-26 17:18 ` Jason Tackaberry [this message]
2003-01-27 5:40 ` S Mohan
2003-01-27 9:15 ` Björn Snippe
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-104360163316270@msgid-missing \
--to=tack@auc.ca \
--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.