From: "James Lista" <lista@umeda.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb
Date: Sun, 17 Oct 2004 12:41:59 +0000 [thread overview]
Message-ID: <00e601c4b446$b1be0fb0$480710ac@d3lta> (raw)
In-Reply-To: <marc-lartc-101661742904753@msgid-missing>
andreas,
having one class per user seems cool... please buddy, have a sample script
of that ?
so, if i have 600kbit / 7 = 86kbit for each, is it that ??? if so, is it
too few for a single user ?
about something that i read that say "borrowing", when a user borrow his
spare band to a "vampire", when will he gets it back when he needs it...?
thanks again
----- Original Message -----
From: "Andreas Klauer" <Andreas.Klauer@metamorpher.de>
To: <lartc@mailman.ds9a.nl>
Sent: Sunday, October 17, 2004 11:20 AM
Subject: Re: [LARTC] htb
> Am Sunday 17 October 2004 15:02 schrieb James Lista:
> > and about that you say take a look at ipp2p or l7-filter: errr, can
> > they identify when a user changed edonkey or any other p2p default port
> > and limit such packet even so ????
>
> They try to. I'm using IPP2P and it works okay for me.
>
> Although my shaping setup is a little different from what you want to do.
> I've got one class per user, so everyone gets the same share of bandwidth.
> This way it doesn't matter what kind of traffic a user generates, as it
> doesn't influence the others.
>
> Prioritization is then done within the user classes, the only effect of
> that is that a user can still have a lag free SSH connection while he's
> downloading stuff at the same time.
>
> So in my setup, if the user finds a way to trick the prioritization
> settings, he's only tricking himself, because he can't escape his user
> class :)
>
> Andreas
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
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-10-17 12:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 9:43 [LARTC] htb George Tsuladze
2002-03-20 12:20 ` Soulfly
2002-05-04 11:42 ` Stef Coene
2002-09-24 14:12 ` [LARTC] HTB Rimas
2002-09-24 14:12 ` Rimas
2002-09-24 14:17 ` Marc-Christian Petersen
2002-09-24 14:23 ` Esteban Maringolo
2002-09-24 14:30 ` Rimas
2002-09-24 14:55 ` Rimas
2002-09-24 15:00 ` Marc-Christian Petersen
2002-09-24 15:14 ` Rimas
2002-09-24 15:14 ` Rimas
2002-09-24 15:51 ` Esteban Maringolo
2002-09-24 16:16 ` Stef Coene
2002-09-25 4:27 ` mdew
2002-09-25 7:59 ` Stef Coene
2002-09-26 14:36 ` raptor
2002-11-08 13:45 ` Chandrashekhar Rane
2002-12-27 20:14 ` Reginald R. Richardson
2002-12-27 21:59 ` Stef Coene
2003-05-13 18:00 ` [LARTC] htb Evgeni Gechev
2003-05-13 18:34 ` Stef Coene
2003-05-13 19:03 ` Evgeni Gechev
2003-05-13 19:40 ` Stef Coene
2003-05-13 19:47 ` Evgeni Gechev
2003-05-13 19:53 ` Stef Coene
2003-05-13 20:47 ` Evgeni Gechev
2003-05-14 10:01 ` Stef Coene
2004-01-15 7:21 ` [LARTC] HTB Cristea Virgil Ionut
2004-01-15 12:12 ` Andre Correa
2004-04-09 23:09 ` Arturas Lapiene
2004-10-14 18:23 ` sistemas
2004-10-14 20:03 ` Jason Boxman
2004-10-17 11:44 ` [LARTC] htb James Lista
2004-10-17 12:08 ` James Lista
2004-10-17 12:19 ` Andreas Klauer
2004-10-17 12:41 ` James Lista [this message]
2004-10-17 12:53 ` ja
2004-10-17 13:02 ` James Lista
2004-10-17 13:20 ` Andreas Klauer
2004-10-17 13:22 ` Andreas Klauer
2004-11-10 14:48 ` [LARTC] HTB "Marcus Schäfer"
2007-06-10 16:27 ` Marco Aurelio
2007-06-11 8:09 ` m.innocenti
-- strict thread matches above, loose matches on Subject: below --
2002-05-04 8:53 [LARTC] htb Anjaneya Pal
2002-05-04 8:56 ` Martin Devera
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='00e601c4b446$b1be0fb0$480710ac@d3lta' \
--to=lista@umeda.com.br \
--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.