similar to: the mistery of 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

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

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

I have two machines a linux_amd64_x86 (gentoo_amd64) and a linux_x86. Both run R-2.1.0. I have a very long program (hopefully will become a package) that works perfectly on the linux_amd_x64. Great means no error, no problems and results that, where the analytic solution exists, coincide with it. I have problem making the code run on the x64 machine. I am baffled. The same code on the same version

Please bear with me as this is quite a complicated problem which has eluded me for days now... I recently upgraded a Samba 2.2 PDC to Samba 3.0 [3.0.20a as of now]. After upgrading, I had problems with two XP machines, among 16 of them. One of them didn't validate the domain users correctly. That was immediately taken care of by having said machine leave and re-join the domain. Nothing

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

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

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 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

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, 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

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

Thanks in advance! Summary: when I load netem and teql together, teql doesn''t work correctly. (If I load teql only, everything is fine) I loaded both netem and teql. Netem is associated with eth0, and teql is associated with both eth0 and eth1. But traffic only goes out of eth1. Attached are the commands that I used to configure teql and netem (on machine 1), and commands to

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;

Could someone give me some help in prioritizing uploading traffic on my ADSL connection. Currently, I have set up a Linux 2.4.12 router/firewall/NAT to allow our network of users to access the Internet. --------- eth0 ---- Linux router/firewall/NAT --- eth1 ---- Local network a.b.c.d 192.168.1.254 I can''t seem to find enough information

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 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

OK - this is starting to get frustrating... Are there any known issues with 2.6.9 and traffic shaping? I am using 2.6.9 with geoip 20041115, and get odd oopses. The following script oopses my box: ----------------------------------------------------- #!/bin/sh -x IFOUT=''eth1'' IFIN=''eth0'' TC=''/sbin/tc''

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

Hello, I am trying to revive an old linux server installation, which still has libc5. Sadly, most current software does not compile anymore on this system, including the tc utility. As with other tools (net-tools, coreutils, procps etc.) I tried to compile and statically link (LDFLAGS=-static) on a more recent linux machine and copy the static binaries over to the old machine. But no luck