From: <mjoachimiak@poczta.onet.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB classifying
Date: Thu, 23 Jan 2003 22:21:58 +0000 [thread overview]
Message-ID: <001001c2c32d$d8abd640$0200a8c0@monster> (raw)
Maybe it's my oversight but shoudn't you have "tc qdisc add dev eth0 root
handle 1:0 htb" before rest of your instructions ??
> I am trying to shape a client (somewhat advanced).
>
> This is my target:
> Client is 192.168.2.224. I would like to allow him to download with
> 500000 bits/sec in general. But, for a specific port(say 22), i would
> like him to download with 300000 bit/sec only. The problem is that my
> configuration (maybe wrong) allows him to download with 800000 bit/sec.
> (500000 generally + 300000 on port 22)
> I thought that having classes 1:11 and 1:12 being children of a class
> with rate 500000, 500000 would be the maximum...
> Can htb to this? Can another queue do this?
>
> /sbin/tc class add dev eth0 parent 1: classid 1:10 htb rate 500000
>
> /sbin/tc class add dev eth0 parent 1:10 classid 1:11 htb rate 300000
> /sbin/tc filter add dev eth0 parent 1:0 protocol ip prio 100 u32 match ip
src 192.168.2.224/32 \
> match ip sport 80 0xffff classid 1:11
>
> /sbin/tc class add dev eth0 parent 1:10 classid 1:12 htb rate 500000
> /sbin/tc filter add dev eth0 parent 1:0 protocol ip prio 100 u32 match ip
src 192.168.2.224/32 classid 1:12
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-01-23 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 22:21 mjoachimiak [this message]
2003-01-23 23:13 ` [LARTC] HTB classifying mjoachimiak
2003-01-25 0:48 ` mjoachimiak
2004-07-24 18:51 ` Mpourtounis Dimitris
2004-07-24 22:39 ` Mpourtounis Dimitris
2004-07-25 2:53 ` Martin A. Brown
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='001001c2c32d$d8abd640$0200a8c0@monster' \
--to=mjoachimiak@poczta.onet.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.