From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bandwidth Shaping
Date: Fri, 04 Apr 2003 08:43:51 +0000 [thread overview]
Message-ID: <marc-lartc-104944590421092@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100201396316589@msgid-missing>
On Friday 04 April 2003 02:46, bbeverage@intelliwave.com wrote:
> I own a WIreless ISP and have recently began suppling bandwidth to college
> dorms. As I expected, 90% of the bandwidth they consume is downloading
> music with programs such as Kazaa. I would like to throttle this
> bandwidth, only as needed. As long as extra, unused bandwidth was present,
> the music folks should be able to use it, but when a web or email user
> needed more bandwidth, the music user should be throttled and the web user
> should access the Internet at full speed.
>
> I don't want to eliminate the music users ability to download music, I just
> would like them to receive the "left over" bandwidth and not the "Lion's
> share."
>
> Is there a way to accomplish this with Linux?
Yes.
The only problem is separating the bulk download traffic from the other.
Kazaa and other software uses dynamic ports.
> I have reviewed several applications and appliances that claim to do this
> very thing. I would however like to find a cost effective Linux solution
> as opposed to a $5000 packateer solution.
I can give you my bank account and create a black box for you for that money
:)
> I beleive the only way to accomplish this is to look at the application
> layer of the communication. Limiting via port is not sufficent as Kazaa
> and many other programs can be configured to operate on port 80.
What you also can do is put all non-bulk traffic in a class (http, https ftp,
smtp, ssh, telnet, DNS, SYN, ACK, ... can be easy filtered) and all other
traffic in the default bulk class.
The only thing you have to do is to check that you don't put non-bulk traffic
in the default, bulk class. But that's easy. If people complain that some
stuff is not working, you can filter it out and put it in the non-bulk class.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
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-04-04 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 9:24 [LARTC] bandwidth shaping bhalchandra sawant
2003-04-04 0:46 ` [LARTC] Bandwidth Shaping bbeverage
2003-04-04 8:43 ` Stef Coene [this message]
2003-08-23 16:55 ` Gustaf
2003-08-23 19:20 ` Stef Coene
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-104944590421092@msgid-missing \
--to=stef.coene@docum.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox