From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) on a router
Date: Sat, 24 Apr 2004 05:27:13 +0000 [thread overview]
Message-ID: <200404240127.13635.jasonb@edseek.com> (raw)
In-Reply-To: <46799.82.82.95.252.1082769835.squirrel@mail.surakware.net>
On Friday 23 April 2004 21:23, trapni@surakware.net wrote:
> Hi all,
Hello.
> this is really not really very easy to understand, or, to get in.
I spent several weeks playing to tcng. I found a few useful references.
http://tldp.org/HOWTO/Traffic-Control-tcng-HTB-HOWTO/index.html
http://mailman.ds9a.nl/pipermail/lartc/2003q4/010826.html
http://linux-ip.net/gl/tcng/tcng.html
> Well, I've the following configuration on the router box:
>
> LAN
> - interface: eth0
> - network: 192.168.2.5/24
> - bandwidth: 100Mbit/s
> INET interface
> - interface: ppp0
> - network: .dynamic.ip./0
> - bandwidth: DOWN\x1536kbit/s and UP%6kbit/s
>
> the LAN interface is to serve 6 other clients with internet and local
> services. My goal NOW was, or is, to garrantie each client with a fair
> amount of bandwith for both, up and down.
Egress is easy. Ingress seems to be a topic that is discussed often on LARTC,
and I believe your options are to either use an ingress policer or the IMQ
target. The former you can do directly with tcng, the latter I believe you
cannot.
> That is, each client inside the LAN should get garrantied
> - PER_CLIENT_DOWN%6kbit/s
> - and PER_CLIENT_UPBkbit/s
> Each unused bandwith may be shared between them.
>
> The LAN clients have IP pool:
> 192.168.2.2-192.168.2.4, and
> 192.168.2.6-192.168.2.8
>
> But how exactly do I now express my wish in TCNG syntax?
>
> Some kind of pseudo code like below...
>
<snip>
> The "device" object is meant to represent the device's configuration
> specific data. "input" as child of "device" represents the input
> bandwidth configuration - same goes for "output". class is just like
> tc/tcng, I guess. "catch ip IP" just tells, what IP packets should be
> queued in this class. The queuing discipline to be used is rarely
> unimportant, maybe htb, cbq, or tbf, what ever(?) best fits right here.
You'd probably use HTB for egress. If you decide to use IMQ you might use it
in both directions.
> Sorry, this is *my* brain-dead-pseudo-code to explain, what I want, with a
> syntax associated to the tcc(tcng) examples I have found on the net.
>
> Could someone *now* show me, how my goal should look in tcng syntax?
I don't think you can use IMQ from within tcng, so you may not be able to do
ingress and egress with a single tool.
> Many thanks,
> Christian Parpart.
--
Jason Boxman
Perl Programmer / *NIX Systems Administrator
Shimberg Center for Affordable Housing | University of Florida
http://edseek.com/ - Linux and FOSS stuff
_______________________________________________
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-04-24 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 1:23 [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) on a router trapni
2004-04-24 5:27 ` Jason Boxman [this message]
2004-04-25 7:06 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) Andy Furniss
2004-04-25 17:43 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) on a router Christian Parpart
2004-04-26 8:01 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) Andy Furniss
2004-04-28 8:42 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) on a router Christian Parpart
2004-05-02 23:44 ` Andreas Klauer
2004-05-05 8:34 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) Andy Furniss
2004-05-05 10:39 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) on a router Andreas Klauer
2004-05-05 12:33 ` [LARTC] newbie: TC[NG] with (256kbit/s down and 768kbit/s up) Andy Furniss
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=200404240127.13635.jasonb@edseek.com \
--to=jasonb@edseek.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.