search for: priomap

Hi all, Here is something that i still haven''t understood. When installing PRIO, it creates 3 "classes" with priority level according to the TOS. That command line : # tc qdisc add dev eth0 root handle 1: prio give that result : # tc qd sh qdisc prio 1: dev eth0 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 How should i read that priomap, what does it mean and how to change it. thanks for the help if you can and good night Emmanuel _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc...

IMHO, the priomap explanation in the 9.2.1.1. of the LARTC HOWTO is not clear enough. I only understood it''s real behavior until I read this document from Russell Stuart: http://ace-host.stuart.id.au/russell/files/tc/doc/tc/priority.txt So, based in this information, I''ve prepared an alternative pr...

Dear list, before writeing this mail I really searched in the mailing list and deeply red the HOWTO, but I didn''t find a clear and univoque answer to my doubt. What is the meaning of the priomap? And what kind of TOS concerns? My first opinin was the one-to-one correspondence of the priomap and the 16 values of the four TOS bits. I mean priomap 1 2 0 3 0 0 0 0 0 0 0 0 0 0 0 1 implies packet with tos 00000000 and 11111111 in band 1 packet with tos 00000001 in band 2 packet with tos 00...

Today I''ve noticed a bit strange (?) behaviour when prio qdisc is used. Example (having no filters/qdisc/etc. at the start) : Add simple 9 bands qdisc, set each mapping to lowest priority band: tc qdisc add dev $eth root handle 1: prio bands 9 priomap 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 If I do just that, all is fine - whole traffic ends in 9th band, what can easily be verified by tc -s class show dev $eth But, if I added following filter: tc filter add dev $eth parent 1:0 protocol arp prio 1 u32 classid 1:1 match u32 0 0 I can immediately see t...

Hello, is it possible that the number of bands for the PRIO qdisc is limited to 16? tc qdisc add dev $DEVICE root handle 1: prio bands 16 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 succeeds but tc qdisc add dev $DEVICE root handle 1: prio bands 17 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 returns: ''RTNETLINK answers: Invalid argument'' Is there any possibility to raise the number of bands to a higher value? Thank you in ad...

Hi, I have a server and ten clients in a Gigabit network. The server has 125mbps network bandwidth. I want that the server has 40Mbps bandwidth reserved for client 1 (IP 192.168.5.141), and the rest bandwidth is for all other clients. My script looks like this (I use IFB for incoming traffic): #!/bin/bash export TC="/sbin/tc" $TC qdisc add dev ifb0 root handle 1: htb default 30

...4 Int. Bulk 1 0x1c 14 mr+mt+md 4 Int. Bulk 1 0x1e 15 mmc+mr+mt+md 4 Int. Bulk 1 If I read this correctly, packets with tos 0x0 would be mapped to band 1, packets with tos 0x2 would be mapped to band 2, etc etc. However, the default priomap is 1, 2, 2, 2, 1, 2, 0, 0, 1, 1, 1, 1, 1, 1, 1, 1. These numbers do not correspond to the numbers in the table above. Is there something I have overlooked or is the information in the above table incorrect? Thanks for any help, roel

Beta 1 is now available for testing. ---------------------------------------------------------------------------- I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E ---------------------------------------------------------------------------- 1) Previously /var/log/shorewall*-init.log was created in the wrong Selinux context. The rpm''s have been modified to

Beta 1 is now available for testing. ---------------------------------------------------------------------------- I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E ---------------------------------------------------------------------------- 1) Previously /var/log/shorewall*-init.log was created in the wrong Selinux context. The rpm''s have been modified to

...ip src 192.168.2.2 flowid 1:22 tc filter add dev ppp0 parent 1:0 prio 1 u32 match ip src 192.168.0.1 flowid 1:21 says : RTNETLINK answers: Invalid argument --------------------------------------------------------------------- my system : router:~# tc qdisc show dev ppp0 qdisc prio 23: bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 qdisc prio 22: bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 qdisc prio 21: bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 qdisc prio 20: bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 qdisc htb 1: r2q 10 default 20 direct_packets_stat 0 router:~# tc class s...

This is my first attempt at understanding lartc: I want to throttle outgoing bandwidth fo a certain tcp port and leave other traffic the way it was. so I put a prio qdisc at the root of eth0 (dummy priomap since i want to use filters to switch bands): $ tc qdisc add dev eth0 root handle 1: prio bands 2 priomap 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 then attach a tbf qdisc at 1:2 : $ tc qdisc add dev eth0 parent 1:2 handle 20: tbf rate 2kbit buffer 100 limit 300 now i want traffic to port 4662 to be enqueu...

...rror? Am I missing some kernel feature? My versions: Kernel 2.6.10 and newest iproute from Debian unstable (20041019-2). Thank you for reading, Viktor. --------> CONFIGURATION SCRIPT <-------- # Create the main PRIO qdisc tc qdisc add dev ppp0 root handle 1: prio bands 2 priomap 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 # Create the two PRIO sub-qdiscs tc qdisc add dev ppp0 parent 1:1 handle 10: prio bands 2 priomap 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 tc qdisc add dev ppp0 parent 1:2 handle 20: prio bands 2 priomap 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 # Create the four subclasses tc qdisc ad...

...92.168.1.4 (masqueraded over dialup) the highest priority: #! /bin/bash WHAT="add" iptables -A PREROUTING -i eth0 -s 192.168.1.1 -t mangle -j MARK --set-mark 1 iptables -A PREROUTING -i eth0 -s 192.168.1.4 -t mangle -j MARK --set-mark 4 tc qdisc $WHAT dev ppp0 root handle 1: prio bands 3 priomap 0 1 2 tc qdisc $WHAT dev ppp0 parent 1:1 handle 2: pfifo limit 1024 tc qdisc $WHAT dev ppp0 parent 1:2 handle 3: pfifo limit 1024 tc qdisc $WHAT dev ppp0 parent 1:3 handle 4: pfifo limit 1024 tc filter add dev ppp0 protocol ip parent 1:0 prio 0 handle 4 fw classid 1:2 tc filter add dev ppp0 protoco...

...ity queue - AF11 (0x28) goes to the normal priority queue, and - BE traffic goes to the low priority queue - For stat collection, I need to see: - how many bytes and packets are in each of the four queues - My configuration thus far is: tc qdisc add dev eml_test root handle 1: prio bands 4 priomap 0 1 2 3 tc filter add dev eml_test parent 1:0 prio 1 protocol ip u32 match ip tos 0xb8 0xff flowid 1:1 tc filter add dev eml_test parent 1:0 prio 2 protocol ip u32 match ip tos 0x80 0xff flowid 1:2 tc filter add dev eml_test parent 1:0 prio 3 protocol ip u32 match ip tos 0x50 0xff flowid 1:3 tc...

...problem has been discussed already. I am running red-hat LINUX 2.2.14 and the version of iproute that comes with it. The problem is that whatever I give as a command it tells me RTNETLINK answers : Invalid argument Example : tc qdisc add dev eth2 handle 10: root estimator 1sec 8sec prio bands 3 priomap 0 1 2 I have tried all kinds of combinations and it refuses to do anything...Can anyone please help me?? Thanks, Anand Get 250 color business cards for FREE! http://businesscards.lycos.com/vp/fastpath/

...or international traffic $IPT -t mangle -A INAT -j CLASSIFY --set-class 20:100 $IPT -t mangle -A INAT -j ACCEPT # Rules for local traffic $IPT -t mangle -A NATI -j CLASSIFY --set-class 20:200 $IPT -t mangle -A NATI -j ACCEPT # Build output rules $TC qdisc add dev $IFOUT root handle 1: prio bands 2 priomap 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 $TC qdisc add dev $IFOUT parent 1:1 handle 10: pfifo limit 10 $TC qdisc add dev $IFOUT parent 1:2 handle 20: htb default 100 r2q 1 $TC class add dev $IFOUT parent 20: classid 20:10 htb rate ${OUTBW}kbit ceil ${OUTBW}kbit prio 0 $TC class add dev $IFOUT parent 20:10...

...traffic goes to the low priority queue > > > >- For stat collection, I need to see: > > > > - how many bytes and packets are in each of the four queues > > > >- My configuration thus far is: > > > >tc qdisc add dev eml_test root handle 1: prio bands 4 priomap 0 1 2 3 > > > >tc filter add dev eml_test parent 1:0 prio 1 protocol ip u32 match ip tos > >0xb8 0xff flowid 1:1 > > > >tc filter add dev eml_test parent 1:0 prio 2 protocol ip u32 match ip tos > >0x80 0xff flowid 1:2 > > > >tc filter add dev eml_test...

...g to set up 15 different delay intervals for packets leaving on an interface, using netems hanging off of a 16-band prio. I''m having trouble adding anything to bands higher than 10. Here''s what I tried: tc qdisc add dev eth0 root handle 1: prio bands 16 \ priomap 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 I want all default traffic to go to the highest priority band (0), regardless of the TOS bits and whatever. I''ll add filters to place select packets in lower priority bands (1..15). So far, so good. Next: tc qdisc add dev eth0 parent 1:10 handle 10...

...0.0.9/30 # echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter # echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter [root@machine1]# tc qdisc ls qdisc netem 1: dev eth0 limit 1000 delay 100.0ms qdisc teql0 10: dev eth0 parent 1:1 qdisc teql0 8001: dev eth1 qdisc pfifo_fast 0: dev teql0 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.8 0.0.0.0 255.255.255.252 U 0 0 0 teql0 10.0.0.0 0.0.0.0 255.255.255.252 U 0 0 0 eth0 10.0.0.4 0.0.0.0 255.255.255.252 U 0 0 0 eth...

...lem with the prio qdisc and I don´t know what is wrong in my configuration This ist a sample configuration and looks like this: #include "fields.tc" #include "ports.tc" #define X16(i) i i i i i i i i i i i i i i i i dev ppp0 { dsmark { prio(bands 6, priomap X16($be)) { class if ip_proto == IPPROTO_UDP; class if tcp_dport == PORT_TELNET; class if tcp_dport == PORT_HTTP; class if tcp_dport == PORT_SMTP; class if ip_dst == 10.0.10.10; $be = class(6); } } } The tc-Code looks like this:...