From: Scott Baker <bakers@web-ster.com>
To: lartc@vger.kernel.org
Subject: [LARTC] tncg and bandwidth limiting
Date: Wed, 28 Jan 2004 00:07:09 +0000 [thread overview]
Message-ID: <5.2.0.9.0.20040127160516.02e378f0@mail.web-ster.com> (raw)
In-Reply-To: <5.2.0.9.0.20040127150331.00ac7bd0@mail.web-ster.com>
I think I got a little send happy with the last message and forgot to
include the "right" configuration. Here is REALLY what we're using. It's
working in the lab right now, I want to move it into production later.
Basically ignore that last message.
----------------------------
I'm trying to do some very simple rate-shaping on an interface. I want to
limit my 100baseT interface to 7 megs both ingress and egress of the
interface. I've been hacking my way through the documentation and some
examples and I've come up with the following configuration for tcng that
seems to do what I want.
I'm curious if some of the other experts out there wouldn't have a "better"
way to do what I'm doing. I'd like to do HTB ingress as well, but it
complains that the the ingress qdisc doesn't allow inside classes or
something like that. I think this will work for me, I just want to make
sure this is the best way to do things.
----------------------------
dev INTERFACE {
egress {
class ( <$all> ) if 1;
htb () {
class ( rate 100Mbps, ceil 100Mbps ) ;
$all = class ( rate 7Mbps, ceil 7Mbps ) ;
}
}
ingress {
$p = bucket(rate 7Mbps, burst 100kB, mpu 200B);
class (1) if (conform $p && count $p) || drop;
}
}
Scott Baker - Network Engineer - RHCE
bakers @ web-ster . com - 503.266.8253
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-01-28 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 23:24 [LARTC] tncg and bandwidth limiting Scott Baker
2004-01-28 0:07 ` Scott Baker [this message]
2004-01-28 2:12 ` rubens
2004-01-28 6:18 ` 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=5.2.0.9.0.20040127160516.02e378f0@mail.web-ster.com \
--to=bakers@web-ster.com \
--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.