From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] isolated works fine for me
Date: Fri, 24 Jan 2003 20:31:09 +0000 [thread overview]
Message-ID: <marc-lartc-104344035003155@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104343487127786@msgid-missing>
On Friday 24 January 2003 21:21, Sebastian 'spax' Pape wrote:
> hi there,
>
> > > i've isolated a band of 5k for one of my friends in the network so he
> > > can play counter-strike .. if i don't use the isolated parameter he
> > > will have a bad ping since his class will borrow to another classes ..
> >
> > Can you post your script so I can take a look at it ?
>
> I tried to reserve bandwidth for cs, too, but it didn't really work. So if
> you work something out I would apreciate it if you post it here ;)
Reserving bandwidth for something is not so difficult. If you have a 100kbps
link and you want a minimum of 10kbps for cs, you have to create 2 class :
100
/ \
10 90
100 : rate = ceil = 100kbps
10 : rate = 10kbps, celi = 100kbps
90 : rate = 90kbps, ceil = 100kbps
The 10kbps class will always get at least 10kbps. If it's a low rate class,
you can even limit the 90kbps to 90kbps. So the remaining 10kbps is always
there for the 10kbps 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-01-24 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 18:57 [LARTC] isolated works fine for me Daniel Ditu
2003-01-24 19:24 ` Stef Coene
2003-01-24 20:21 ` Sebastian 'spax' Pape
2003-01-24 20:31 ` Stef Coene [this message]
2003-01-24 20:41 ` Sebastian 'spax' Pape
2003-01-25 10:36 ` Daniel Ditu
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-104344035003155@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