similar to: Advanced routing (Tc filter)

Hi, I am currently working on the TC. I have seen some behaviour which seems to be odd. I know someone in the mailing list would have seen this problem or may have some fix for this problem. When I try to include u32 filters with different priority or pref, I could see the filters being set on all the priority''s irrespective of the priority number. See my sample script below and the

I shape my upstream cable link with HTB from a script. My voip traffic (from the 192.168.0.14 host) gets priority over everything else to the near-starvation of other classes; the rest of the traffic is split up based on some priority rules (qos, empty ack packets, etc). eth1 is the uplink I''ve been using HTB and fw marking for the job until recently, when I changed the queue structure

Hi How can I control which filter a packet will meet first? I have tried changing the order of applying the tc filter scripts and switching flowid number, but ''protocol ip u32 match ip src <ip net> match ip src 0.0.0.0/0'' always kicks in first? >From my script -------------------- # All traffic - Priority: Low tc filter add dev eth0 parent 1:0 prio 2 protocol ip u32

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

On Sat, 17 Dec 2005, Andy Furniss wrote: > The u8 test works OK for me as does the one below. My mistake. I cleaned the rules and removed the ones that collided with the u8 one. There is no error on this. (see explanation bellow). > > When playing with tc filters I always tc qdisc del dev eth0 root and enter > the whole lot again between tests. I always took that as mandatory.

The interface is setup like this: # tc qdisc del dev eth0 root # tc qdisc add dev eth0 root handle 1: htb default 2 # tc class add dev eth0 parent 1: classid 1:2 htb rate 20mbit ceil 20mbit If I add a second class and a filter to send traffic to it like this: # tc class add dev eth0 parent 1: classid 1:130 htb rate 1Mbit ceil 1Mbit # tc filter add dev eth0 protocol ip parent 1:0 prio 130 u32

I''ve done some tests with TC FILTER and his PRIO and think that is an error or OMISION on TC FILTER DOCUMENTATION from: http://lartc.org/howto/lartc.qdisc.filters.html#AEN1100 Let''s say we have a PRIO qdisc called ''10:'' which contains three classes, and we want to assign all traffic from and to port 22 to the highest priority band, the filters would be:

Hi Guys, I have a couple of problems that are driving me nuts. This is the script I am using to setup restirctions and bw limitations: #Adding root class. tc qdisc add dev eth0 root handle 1: htb default 10 &>/dev/null tc class add dev eth0 parent 1: classid 1:1 htb rate 100Mbit ceil 100Mbit burst 2k quantum 1536 tc qdisc add dev eth1 root handle 1: htb default 10 &>/dev/null tc

Hi, I am very new to tc. I added a filter using the following command: tc filter add dev eth0 V parent 20:0 protocol ip prio 1 handle ::128 u32 match ip tos 0x44 0xfc flowid 20:1 To check if the filter rule was indeed added, I run tc filter show dev eth0 parent 20: This gave me the following output: filter protocol ip

The following (occuring on debian/testing with kernel-image-2.6.8-2-386 version 2.6.8-13 and iproute version 20041019-3) confuses me: # tc qdisc add dev eth0 root handle 1: prio # tc filter add dev eth0 parent 1: proto ip pref 1 handle 1 fw classid 1:2 # tc filter ls dev eth0 filter parent 1: protocol ip pref 1 fw filter parent 1: protocol ip pref 1 fw handle 0x1 classid 1:2 # tc filter del dev

Hi, I am currently using TC for setting up user MAC based filters,and I am seeing a problem when I try to assign different priorities to the MAC Match filter apart from the root qdisc and parent class. Here is my script. /*****************************************************/ First of all I create the qdisc and class based on priority 2 and also the Hash mask tc qdisc add dev eth1 root handle

I''m attempting to set up a hierarchy of tc qdiscs with filters, but the filters don''t seem to be working correctly.  I''m running iptables 1.3.5 with iproute 2.6.16.20060323 on a Gentoo 2.6.18 kernel.  The system takes all my tc setup, but does not filter packets as I am expecting it to based on my ruleset. My tc qdiscs and classes are added correctly and report as

Dear all, I have big question in my mind about "tc filter" sintax. If I give "tc -s -d filter sh dev eth0" command, then the output is like below : filter parent 1: protocol ip pref 1 u32 filter parent 1: protocol ip pref 1 u32 fh 800: ht divisor 1 filter parent 1: protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 1:2 (rule hit 21553629 success 37907)

Dear All I am trying a very simple set up: (a bit long message follows) #Flush previous definitions $TC qdisc del dev $VVNET root >&/dev/null $TC qdisc del dev $INTERNET root >&/dev/null $IPT -t mangle -D PREROUTING -i $INTERNET -d 200.231.56.0/24 -j IMQ --todev 0 # Mothers off all disciplines $TC qdisc add dev $VVNET root handle 1: htb default FFFF r2q 1 $TC qdisc add dev

Hi fellows, i''m just a newbie to use the cool tc and played around the last 2 weeks. I''m quite confident - in theory - what''s possible and the basic difference between the queuing disciplines. We''re using a Fedora Core 3 box as Gateway (iptables,tc,iproute2 with NAT). Clients are coming in via eth1 and outgouing traffic (2Mbit/s SDSL) through eth0. So we

hi, all i run the following scripts : tc qdisc add dev eth0 handle ffff: ingress tc filter add dev eth0 parent ffff: protocol ip \ pref 4 u32 match ip dst 10.0.0.1 flowid :1 my question is : can i know how many packets are matched by this filter? if i can , what should i do to get this counter value, then. thanks :) _________________________________________________________________ MSN

Hi all! :) I see that this is partially covered in the mailing list archive but at the moment I can''t find a straight & working answer. I have an imq device with dynamically attacched classes/qdiscs/filters. There is a hashing filter that maps the last octet of an user''s IP address to a class (and associated qdisc). The "empty" filter looks like this: filter

I''m having trouble getting ingress policing to work on a bridged device. The bridge contains several interfaces: peth0, vif0.0, vif[1-7]0.1, vif[25].1 . (This is under xen, in case the vif''s didn''t give that away, so peth0 is renamed eth0.) The tc rules I have are: tc qdisc del dev peth0 root tc qdisc del dev peth0 ingress handle ffff: tc qdisc add dev peth0 root

Hello I''ve been messing with traffic controlling for some time and encountered singularities I''d like to talk about. First explaining of my pow (can''t tell how much each point is relevant) Box with Debian, Intel PII*2 old and fancy:), ADSL link with dyn IP, some servers (f. ex. squid), loc net with dhcp, (although IP statically given by MAC); MASQ. Such circumstances

Hi all, I''m having a hell of a time getting tc and IFBs to co-operate. I''ve copied the following from http://linux-net.osdl.org/index.php/IFB: -- export TC="/sbin/tc" $TC qdisc add dev ifb0 root handle 1: prio $TC qdisc add dev ifb0 parent 1:1 handle 10: sfq $TC qdisc add dev ifb0 parent 1:2 handle 20: tbf rate 20kbit buffer 1600 limit 3000 $TC qdisc add dev ifb0