From: "ISC Robert Kryczalo" <robert.kryczalo@iscnet.pl>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Bandwidth Restrictions in Linux
Date: Sat, 25 Jan 2003 08:43:24 +0000 [thread overview]
Message-ID: <marc-lartc-104348437004853@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104335929011822@msgid-missing>
Hi,
> So, you were limiting bandwidth with CBQ... and now you change to HTB...??
Yes.
>
> What bandwidth you limited with CBQ and to how many clients...??
In most cases 128 kbit/s and for some special classes of trafic
96,80,64,48,40,39,32,24 kbit/s. MInimum guaranted rates of 15kbit/s.
Of course there are higher rates... And we serve much, much more customers
and have complex classification scheme based on time, port, packet size and
type classification scheme... Anyway it take some time to regenerate HTB
tree and to create firewall rules.
> Another test I made was in the moment that I have high delays from the
> Server to a wireless client, I ping from the client to the AP and
> to others
> client.. the result was NORMAL DELAY IN PING... around 4 ms.
So.. really check your CBQ scripts.
>
> Roberto.
Robert
_______________________________________________
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-25 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 21:59 [LARTC] Bandwidth Restrictions in Linux Intercom - Roberto Ravetti
2003-01-24 9:08 ` ISC Robert Kryczalo
2003-01-24 15:16 ` Intercom - Roberto Ravetti
2003-01-24 18:57 ` ISC Robert Kryczalo
2003-01-25 8:43 ` ISC Robert Kryczalo [this message]
2003-01-27 5:38 ` S Mohan
2003-01-27 14:03 ` Mathieu Deziel
2003-01-27 14:52 ` Tushar Gupta
2003-01-27 15:15 ` Debreczeni Peter
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-104348437004853@msgid-missing \
--to=robert.kryczalo@iscnet.pl \
--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.