similar to: Limited number of bands in PRIO qdisc

Hi, I''m trying 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

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

Hi, Sorry to bother you all. I have a typical problem sharing DSL upstream bandwidth with users. I have 3 types of traffic high-priority, medium-priority and low priority. My upstream rate is 960kbits. Traffic (any priority) can vary in bandwidth from 0 to 960kbits. I have a test setup where I can pump 600kbit of high priority sustained and I have 400kbit of low priority traffic sustained. I

Hi, I have done this setup to give the machine 192.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

Hello everybody, sorry for bothering you, but after some hours, I''m stuck. I''m living in a student''s foundation where I want to connect lots of people to a tiny DSL link. We have exactly four types of traffic. We want a really hard PRIO solution (as I promised to someone that group X will only use the link capacity which isn''t used by group Y). I could make a

Hi, all I am interested in Linux related QoS, especially PRIO queue discipline (qdisc). I test some experiments about PRIO qdisc. Host A ------ Router A --- Router B --- Host C | 1Gbps | Host B ---------+ +-------- Host D flow 1 : Host A -> Host C (TCP) flow 2 : Host B -> Host D (UDP) priority 1 queue (pfifo, size 1000 packets ) : flow 1 priority 2

hello to all i''m trying to set a filter but doesn''t want to work. i''ve set ut the qdiscs and the classes like this : tc qdisc add dev ppp0 root handle 1: htb default 20 tc class add dev ppp0 parent 1: classid 1:1 htb rate 120kbit tc class add dev ppp0 parent 1:1 classid 1:20 htb rate 30kbit ceil 120kbit tc class add dev ppp0 parent 1:1 classid 1:21 htb rate 30kbit ceil

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

Hello Mailing list, I have a problem 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;

Hello all, I might make a fool out of me, but I think the prio qdisc doesn''t work as advertised in any document I could lay my hands on. The following tests and observations were made with Linux kernel 2.6.20.21. This makes it up-to-date in the 2.6.20.x kernel family. My problem was that the link quality reported by the olsr.org olsrd degraded depending on the amount of payload

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 priomap explanation for this section of the HOWTO, if you like it as it is I could

I''m trying to build a wan latency test environment, where packets from different "remote" locations get delayed by different amounts of time, depending on which remote location we''re pretending they are from. Currently, I''m doing this using the ''prio'' qdisc to obtain multiple bands, and hanging a different netem qdisc off each of the branches

Hi, I am not sure if this 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

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

Hi to all! I''m studying qdisc prio but I have some problems. I want to create 3 queue (3 bands prio), each one associated to a workstation. I mark (with iptables) packets using workstation mac address and then send all packets in a particular queue. qdisc prio with handle 10: (default priomap) WS1 -> queue 10:1 WS2 -> queue 10:2 WS3 -> queue 10:3 I set it correctly (with

Hello, I am using a simple script, which is based on prio. The point is, that it is not possible to use htb on wifi networks, so I thought that prio will work fine, but it does almost nothing. All I wanted was to make the important packets like icmp, games, VoIP,... to go first, and to slow the things like FTP data transfer, etc. When I use $TC -s qdisc show dev ${IFACE}, I see, that the

Hi, I''m trying to use prio qdisc with htb, however not the "usual" way (like for example FairNAT). Here is my idea: Root has HTB shaping traffic to link speed -> then goes PRIO queues -> each prio queue has HTB with sublasses for each user, should look like this: 1: htb qdisc | 1:1 htb class

Hi, I have a router/firewall running Linux (like the most of you) and I wanted to do some traffic control. I''ve created an root PRIO qdisc like the example in paragraph 9.5.3.1 (http://www.lartc.org/howto/lartc.qdisc.classful.html#AEN903) with three SFQ child-classes. I wanted for interactive (ssh, telnet, ftp-control) and dns-traffic to be placed in the first queue, http should go in

Hi all, based on the information in the "Linux Advanced Routing & Traffic Control HOWTO", I was trying to set up traffic shaping on my firewall. While I found the HOWTO very useful, in the process I ran into some problems that I did not forsee: According to the HOWTO it seems that it should have worked, even after spending some time going through the sections looking for answers,

Hello I''m doing some qdisc programming and I want to get/read the current ingress rate from a kernel module I was wondering what is the most convenient of achieving this My idea is to load the ingress qdisc and the police filter if necessary. and modify the source to export a structure or function so I can read the ingress rate. How does this sound? Is there a simpler way? With