From: "Emil Slavov" <slavov@optisprint.net>
To: lartc@vger.kernel.org
Subject: [LARTC] advice about priority
Date: Mon, 17 Nov 2003 20:24:59 +0000 [thread overview]
Message-ID: <marc-lartc-106910117316440@msgid-missing> (raw)
Hello,
I have 4 ISP providers with different speeds.
I mark the packets of every provider with ip precedence bits and create
classes for these 4 providers
tc qdisc add dev eth1 root handle 1: htb
tc class add dev eth1 parent 1: classid 1:20 htb rate 384Kbit ceil 384Kbit
burst 10k prio 1
tc class add dev eth1 parent 1: classid 1:80 htb rate 256Kbit ceil 256Kbit
burst 10k prio 1
tc class add dev eth1 parent 1: classid 1:60 htb rate 256Kbit ceil 256Kbit
burst 10k prio 1
tc class add dev eth1 parent 1: classid 1:40 htb rate 384Kbit ceil 384Kbit
burst 10k prio 1
tc qdisc add dev eth1 parent 1:20 handle 20: sfq
tc qdisc add dev eth1 parent 1:80 handle 80: sfq
tc qdisc add dev eth1 parent 1:60 handle 60: sfq
tc qdisc add dev eth1 parent 1:40 handle 40: sfq
I have high priority and low priority ips, and i wannt when high priority
ips do not use the bandwith the low priority to use full bandwith. Thats
why for every provider i create 2 classes
tc class add dev eth1 parent 1:20 classid 1:21 htb rate 380Kbit ceil
384Kbit burst 10k prio 1
tc class add dev eth1 parent 1:20 classid 1:22 htb rate 10Kbit ceil 380Kbit
burst 10k prio 3
tc class add dev eth1 parent 1:80 classid 1:81 htb rate 256Kbit ceil
256Kbit burst 10k prio 1
tc class add dev eth1 parent 1:80 classid 1:82 htb rate 10Kbit ceil
240Kbit burst 10k prio 3
tc class add dev eth1 parent 1:60 classid 1:61 htb rate 256Kbit ceil
256Kbit burst 10k prio 1
tc class add dev eth1 parent 1:60 classid 1:62 htb rate 10Kbit ceil
240Kbit burst 10k prio 3
tc class add dev eth1 parent 1:40 classid 1:41 htb rate 380Kbit ceil
384Kbit burst 10k prio 1
tc class add dev eth1 parent 1:40 classid 1:42 htb rate 10Kbit ceil
380Kbit burst 10k prio 3
filters for high prefered IP's
tc filter add dev eth1 parent 1: protocol ip u32 match ip dst IP match ip
precedence 0x20 0xff classid 1:21
tc filter add dev eth1 parent 1: protocol ip u32 match ip dst IP match ip
precedence 0x80 0xff classid 1:81
tc filter add dev eth1 parent 1: protocol ip u32 match ip dst IP match ip
precedence 0x60 0xff classid 1:61
tc filter add dev eth1 parent 1: protocol ip u32 match ip dst IP match ip
precedence 0x40 0xff classid 1:41
.............................................................
filters for other IP's
tc filter add dev eth1 parent 1: protocol ip u32 match ip dst IP match ip
precedence 0x20 0xff classid 1:22
tc filter add dev eth1 parent 1: protocol ip u32 match ip dst IP match ip
precedence 0x80 0xff classid 1:82
tc filter add dev eth1 parent 1: protocol ip u32 match ip dst IP match ip
precedence 0x60 0xff classid 1:62
tc filter add dev eth1 parent 1: protocol ip u32 match ip dst IP match ip
precedence 0x40 0xff classid 1:42
........................................................
This configuration do not work propertly. Is anyone that have idea why it
does not work or have any recommendations or ideas according this scenario
?
Thanks
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-11-17 20:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-106910117316440@msgid-missing \
--to=slavov@optisprint.net \
--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.