From: Srikanth <srikanth_w@naturesoft.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] cbq.init for one port on a subnet
Date: Thu, 06 Feb 2003 13:38:51 +0000 [thread overview]
Message-ID: <marc-lartc-104453811314265@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104442465412418@msgid-missing>
Hi!
I've tried with the config. file
DEVICE=eth0,10Mbit,1Mbit
RATE\x100Kbit
WEIGHT\x10Kbit
PRIO=5
RULE\x192.168.0.160/27:6699
only,
It's works fine for me,
Find the stats for the same hereunder,
# ./cbq.init-v0.7.1 start
192.168.0.160/27:6699: match ip dst 192.168.0.160/27 match ip dport 6699
0xffff
# ./cbq.init-v0.7.1 stats
### eth0: queueing disciplines
qdisc tbf 5: rate 100Kbit burst 10Kb lat 488.3ms
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
qdisc cbq 1: rate 10Mbit (bounded,isolated) prio no-transmit
Sent 1924 bytes 28 pkts (dropped 0, overlimits 0)
borrowed 0 overactions 0 avgidle 624 undertime 0
### eth0: traffic classes
class cbq 1: root rate 10Mbit (bounded,isolated) prio no-transmit
Sent 1924 bytes 28 pkts (dropped 0, overlimits 0)
borrowed 0 overactions 0 avgidle 624 undertime 0
class cbq 1:5 parent 1: leaf 5: rate 100Kbit (bounded) prio 5
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
borrowed 0 overactions 0 avgidle 1.79878e+06 undertime 0
### eth0: filtering rules
filter parent 1: protocol ip pref 100 u32
filter parent 1: protocol ip pref 100 u32 fh 800: ht divisor 1
filter parent 1: protocol ip pref 100 u32 fh 800::800 order 2048 key ht 800
bkt 0 flowid 1:5
match c0a800a0/ffffffe0 at 16
match 00001a2b/0000ffff at 20
reg,
Srikanth.
On Wednesday 05 February 2003 09:30 pm, you wrote:
> Hi, Thanks for the quick reply. I tried that and got an error message
> when I started cbq.
> -----------------------------
> What is "ff"?
> Usage: ... u32 [ match SELECTOR ... ] [ link HTID ] [ classid CLASSID ]
> [ police POLICE_SPEC ] [ offset OFFSET_SPEC ]
> [ ht HTID ] [ hashkey HASHKEY_SPEC ]
> [ sample SAMPLE ]
> or u32 divisor DIVISOR
>
> Where: SELECTOR := SAMPLE SAMPLE ...
> SAMPLE := { ip | ip6 | udp | tcp | icmp | u{32|16|8} } SAMPLE_ARGS
> FILTERID := X:Y:Z
> ------------------------------
>
> If you can help me I'd really appreciate it.
>
> Thanks again,
>
> Scott
>
> > 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/
prev parent reply other threads:[~2003-02-06 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 5:57 [LARTC] cbq.init for one port on a subnet Srikanth W
2003-02-06 13:38 ` Srikanth [this message]
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-104453811314265@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 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.