From: Eddie <eddieknows@ananzi.co.za>
To: lartc@vger.kernel.org
Subject: [LARTC] tc&htb
Date: Wed, 12 Nov 2003 06:37:53 +0000 [thread overview]
Message-ID: <marc-lartc-106861937701569@msgid-missing> (raw)
Hi all.
I'm very new to Linux and the whole traffic shaping thing.
Now this is what I've got.A 128Kbit line on eth0 and a 100+ network on
eth1.The mail server is on the internal network(eth1 side).
This is what I want.
They run banking software that uses port 15000-15010.I want the bank
ports and if I'm going to ssh INTO the box to get all bandwidth,that is
128Kbit.Then I want the internal users limited to 96Kbit for web,32 for
mail in and out and 10Kbit for other stuff.I also want them all to share
bandwidth if not use(banking is not done most of the time but if it is
it should get the most)
I got this far and have no idea,I've been reading advance routing and
traffic control,but as the song goes,I'm not the sharpest tool int the
shed.
This is what I've got so far(taken from
15.10. Example of a full nat solution with QoS)
My main problem,if this is right,is with the filter.I don't know how
Please help me because I'm thinking traffic control is a myth?
Thanks Eddie
CEIL\x128
tc qdisc add dev eth0 root handle 1: htb default 13
tc class add dev eth0 parent 1: classid 1:1 htb rate ${CEIL}kbit ceil ${CEIL}kbit
tc class add dev eth0 parent 1:1 classid 1:10 htb rate $(CEIL)kbit ceil $(CEIL)kbit prio 0
tc class add dev eth0 parent 1:1 classid 1:11 htb rate 96kbit ceil ${CEIL}kbit prio 1
tc class add dev eth0 parent 1:1 classid 1:12 htb rate 32kbit ceil ${CEIL}kbit prio 2
tc class add dev eth0 parent 1:1 classid 1:13 htb rate 10kbit ceil ${CEIL}kbit prio 2
tc qdisc add dev eth0 parent 1:10 handle 120: sfq perturb 10
tc qdisc add dev eth0 parent 1:11 handle 130: sfq perturb 10
tc qdisc add dev eth0 parent 1:12 handle 140: sfq perturb 10
tc qdisc add dev eth0 parent 1:13 handle 150: sfq perturb 10
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-11-12 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 6:37 Eddie [this message]
2003-11-12 18:07 ` [LARTC] tc&htb 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-106861937701569@msgid-missing \
--to=eddieknows@ananzi.co.za \
--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.