similar to: Alternative section to the HOWTO...

Hi list, I have a quick question about the priority mapping of tos bits. The manpage of tc-prio shows a nice table with tos bits and the band they are mapped to: TOS Bits Means Linux Priority Band ------------------------------------------------------------ 0x0 0 Normal Service 0 Best Effort 1 0x2 1 Minimize Monetary Cost 1 Filler

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

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 all, First, let me say I''ve been most impressed with how quickly and professionally people on this list ask and answer questions. Next, let me say that with which I need help is properly configuring strict PQ, and gathering certain stats. Specifically: - I need to create a priority queue with four queues (let''s say they are of high, medium, normal, and low priority) - I

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

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,

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

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

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

Hep Trying to get pfifo to work. Setup : |------|<--->eth1 (192.168.10.0/24) eth0---| GW |<--->eth2 (192.168.11.0/24) |------|<--->eth3 (192.168.12.0/24) read all documentation : http://lartc.org/howto/lartc.cookbook.interactive-prio.html here is my TOS mangling rulse in iptables : $IPTABLES -A PREROUTING -i eth1 -t mangle -s 192.168.10.0/24 -p tcp --dport

Hi to everybody I''m trying to use PRIO qdisc to prioritize the traffic but i have strange problem maybe I''m missing sometging. First i add root qdisc like this tc qdisc add dev eth0 root handle 1: prio it''s fine after this i try to match traffic by tos field but i get error invalid match tc filter add dev eth0 parent 1:0 prio 1 protocol ip u32 \ match ip tos 0x10 0xff

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Guus, On 04/30/2015 03:42 PM, Guus Sliepen wrote: > On Thu, Apr 30, 2015 at 02:55:59PM +0200, Armin Schindler wrote: > >> we are using tinc 1.0.24 with 6 hosts (endpoints). Quality of service >> is used with prio qdisc on all network interfaces. This means depending >> on the TOS value of the IP header IP-packets will

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

Hi anyone using sangoma hardware with lartc? pls let me know Thanks Imthiyaz Original Message: ----------------- From: lartc-request@mailman.ds9a.nl Date: Fri, 15 Jun 2007 12:00:07 +0200 (CEST) To: lartc@mailman.ds9a.nl Subject: LARTC Digest, Vol 28, Issue 23 Send LARTC mailing list submissions to lartc@mailman.ds9a.nl To subscribe or unsubscribe via the World Wide Web, visit

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

I''m trying to use tc and netem to delay packets from several different machines as they exit via eth0. Assume two source IPs, 10.0.0.122 and 10.0.0.133. I''d like to delay packets from the first one by 200ms, and packets from the second one by 300 ms. Any other traffic should be sent out normally. Here''s what I tried: # make three classes, 1:1, 1:2, and 1:3: tc qdisc add

Hi all! I''m trying to shape traffic in a dorm''s network (4 mbit symmetrical internet link, about 200 computers, heavy p2p usage). The router is a p4xeon running linux 2.6.9 with the qnet patches (http://kem.p.lodz.pl/~peter/qnet/). When I activate ip_forward I get >20% packet loss and a lot of duplicates. Any ideas? I attach my shaping script. Thank you very much in advance,