From: Srikanth W <srikanth_w@naturesoft.net>
To: lartc@vger.kernel.org
Subject: [LARTC] cbq.init for one port on a subnet
Date: Wed, 05 Feb 2003 05:57:34 +0000 [thread overview]
Message-ID: <marc-lartc-104442465412418@msgid-missing> (raw)
Sub:[LARTC] cbq init for one port on a subnet
Hello,
We use cbq.init to limit bandwidth. It works great on a per-user basis.
Now I'd like to limit traffic from a netblock to the Internet on port
6699.
Network is 192.168.0.160 mask 255.255.255.224
eth0 is the gateway
eth1 connects the netblock in question
Is this the proper syntax;
DEVICE=eth0,10Mbit,1Mbit
RATE\x100Kbit
WEIGHT\x10Kbit
PRIO=5
RULEf99 192.168.0.160/27,
Thanks!
Scott
Hi! Scott,
Your Config. file s'd be
DEVICE=eth0,10Mbit,1Mbit
RATE\x100Kbit
WEIGHT\x10Kbit
PRIO=5
RULE\x192.168.0.160/27:6699
like this & try.
Good Luck.
Srikanth.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-02-05 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 5:57 Srikanth W [this message]
2003-02-06 13:38 ` [LARTC] cbq.init for one port on a subnet Srikanth
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-104442465412418@msgid-missing \
--to=srikanth_w@naturesoft.net \
--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