Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc not working
Date: Mon, 08 Oct 2001 15:27:44 +0000	[thread overview]
Message-ID: <marc-lartc-100255487627569@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100238958132380@msgid-missing>

On Sat, Oct 06, 2001 at 11:31:59AM -0600, oarmas@mpsnet.net.mx wrote:

> 
> I have a computer with RH 7.1 and want to control bandwith to a set of
> networks.
> 
> This is the configuration:
> 
> Internet
>     |
> eth0: 200.39.191.182
> eth1: 200.39.178.129
>     |
>   client network (200.39.178.128/26)
> 
> 
> I use the next script:
> 
> --------------------begin-----------------------
> 
> tc qdisc add dev eth0 root handle 10: cbq bandwidth 10Mbit avpkt 1000
> tc class add dev eth0 parent 10:0 classid 10:1 cbq bandwidth 10Mbit rate \
> 10Mbit allot 1514 weight 1Mbit prio 8 maxburst 20 avpkt 1000
> tc class add dev eth0 parent 10:1 classid 10:64 cbq bandwidth 10Mbit rate
> \
> 64Kbit allot 1514 weight 6Kbit prio 5 maxburst 20 avpkt 1000 bounded
> tc class add dev eth0 parent 10:1 classid 10:128 cbq bandwidth 10Mbit rate
> \
> 128Kbit allot 1514 weight 12Kbit prio 5 maxburst 20 avpkt 1000 bounded
> tc class add dev eth0 parent 10:1 classid 10:256 cbq bandwidth 10Mbit rate
> \
> 256Kbit allot 1514 weight 25Kbit prio 5 maxburst 20 avpkt 1000 bounded
> tc class add dev eth0 parent 10:1 classid 10:512 cbq bandwidth 10Mbit rate
> \
> 512Kbit allot 1514 weight 51Kbit prio 5 maxburst 20 avpkt 1000 bounded
> tc class add dev eth0 parent 10:1 classid 10:1024 cbq bandwidth 10Mbit
> rate \
> 1024Kbit allot 1514 weight 102Kbit prio 5 maxburst 20 avpkt 1000 bounded
> 
> 
> tc qdisc add dev eth0 parent 10:64 sfq quantum 1514b perturb 15
> tc qdisc add dev eth0 parent 10:128 sfq quantum 1514b perturb 15
> tc qdisc add dev eth0 parent 10:256 sfq quantum 1514b perturb 15
> tc qdisc add dev eth0 parent 10:512 sfq quantum 1514b perturb 15
> tc qdisc add dev eth0 parent 10:1024 sfq quantum 1514b perturb 15
> 
> tc filter add dev eth0 parent 10:0 protocol ip prio 100 u32 match ip dst
> 200.39.178.128/26 flowid 10:256
> -------------------------end----------------------------
> 
> It shoud limit this network to 256, but it does not.
> 
> When I test it, it shows no bandwidth limit, since I get  rates higher
> than the allowed from the client side(32kB/s should be maximum).
> Example:

Can you show the output of tc statistics?
> 

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
Trilab                                 The Technology People
Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  reply	other threads:[~2001-10-08 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-06 17:31 [LARTC] tc not working oarmas
2001-10-08 15:27 ` bert hubert [this message]
2001-10-08 17:24 ` Omar Armas Aleman
2001-10-12  6:51 ` Stef Coene

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-100255487627569@msgid-missing \
    --to=ahu@ds9a.nl \
    --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