From: Deepak singhal dsinghal@spacewayindia.com
To: lartc@vger.kernel.org
Subject: [LARTC] CBQ Conf files
Date: Fri, 16 Feb 2001 11:30:21 +0000 [thread overview]
Message-ID: <marc-lartc-98373940417025@msgid-missing> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="iso-8859-1", Size: 721 bytes --]
Hi All,
I am using CBQ init file v 0.6.1 and doing banwidth allocation . I have to make seperate file fo reach group or ip i want to cap .
for e.g. if I have to cap say ten ips from 192.168.1.10 to 192.168.1.20 , each ip to say 32 Kbits , then do i have to make seperate file for each . I try doing something like this but this didn`t worked .
Sample Config file :
DEVICE=eth1,10Mbit,1Mbit
RATE=32Kbit
WEIGHT=3Kbit
PRIO=5
RULE=192.168.1.10
RULE=192.168.1.11
RULE=192.168.1.12
and so on
But instead of allocating each Ip a bandwidth of 32 KBit , it capped for all ips combined to 32 Kbit.
Is there a work around of this or i have to make a seperate file for each IP.
Thanks
Deepak
[-- Attachment #2: Type: text/html, Size: 2326 bytes --]
reply other threads:[~2001-02-16 11:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-98373940417025@msgid-missing \
--to=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