From: "Stephan M. Ott" <webmaster@familie-ott.info>
To: lartc@vger.kernel.org
Subject: [LARTC] limiting doesn't work
Date: Sat, 10 Jul 2004 21:02:55 +0000 [thread overview]
Message-ID: <000001c466c1$5cc7b650$3700a8c0@nathanxp> (raw)
Hi folks,
I read the fantastic LARTC How-to and after that i tried to limit one
host in my LAN for both down-and upload bandwidth usage.
I took section 15.9. and added uplink-limiting as I understood it from
the previous chapters.
Unfortunately it doesn't work.
I ran the script and went to the specified PC, started a download, and
watched the rate. The rate was always about 2000 kbit/s, though I
defined (well, at least I thought so) 768 kbit/s as maximum rate.
Can anyone please look at the script and tell me, what must be corrected
in order for it to work ?
Thanks in advance.
This is the script:
#!/bin/bash
LIMITDOWNv8
LIMITUP–
DEV=ppp0
# clean up qdiscs
tc qdisc del dev $DEV root 2> /dev/null > /dev/null
# limit up- and downlink for benni
tc qdisc add dev $DEV root handle 1: cbq avpkt 1000 bandwidth 2mbit
tc class add dev $DEV parent 1: classid 1:1 cbq rate ${LIMITDOWN}kbit
allot 1500 prio 5 bounded isolated
tc class add dev $DEV parent 1: classid 1:2 cbq rate ${LIMITUP}kbit
allot 1500 prio 5 avpkt 1000
tc filter add dev $DEV parent 1: protocol ip prio 16 u32 match ip dst
192.168.0.51 flowid 1:1
tc filter add dev $DEV parent 1: protocol ip prio 16 u32 match ip src
192.168.0.51 flowid 1:2
#tc qdisc add dev $DEV parent 1:1 sqf perturb 10
#tc qdisc add dev $DEV parent 1:2 sqf perturb 10
I commented out the last 2 lines for testing so that the rate is always
limited.
Any ideas ?
Thanks.
Stephan
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-07-10 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 21:02 Stephan M. Ott [this message]
2004-07-11 0:49 ` [LARTC] limiting doesn't work gypsy
2004-07-11 1:46 ` Andrew Athan
2004-07-11 5:57 ` AW: " Stephan M. Ott
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='000001c466c1$5cc7b650$3700a8c0@nathanxp' \
--to=webmaster@familie-ott.info \
--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