similar to: Fw: tc filter match u8 problem??

Hi All Can someone tell me what am I doing wrong? These was suposed to catch icmp type 8. Why ''match u8'' does not work? # tc filter add dev eth0 protocol ip parent 1: prio 2 \ u32 \ match u16 0x0800 0xffff at -2 \ match u8 8 0xff at 20 \ flowid 1:5 Illegal "match" # # tc filter add dev eth0 protocol ip parent 1: prio 2 \ u32 \ match

Update to iproute2 is available. Most of the changes were to repair the things that broke with the introduction of the batch mode to the ip command. http://developer.osdl.org/dev/iproute2/download/iproute2-2.6.14-051107.tar.gz For info on CVS ans other info see: http://linux-net.osdl.org/index.php/Iproute2 Masahide NAKAMURA * Updating for 2.6.14 - Show UPD{SA,POLICY} message

Hi, all I''ve got problems with tc qdisc ingress. I''m using vanillia kernel 2.6.14.4 patched with http://www.ssi.bg/~ja/routes-2.6.14-12.diff, and iproute2-2.6.14-051107. i am using ingress to limit incoming traffic : (DEV is eth1 / DOWNLINK is 7700) # attach ingress policer: tc qdisc add dev $DEV handle ffff: ingress # filter *everything* to it (0.0.0.0/0), drop everything

em_canid is an ematch capable of classifying CAN frames according to their CAN IDs. This RFC/Patch contains a reworked classifier initially posted in http://www.spinics.net/lists/netdev/msg200114.html The functionality is the same however there is almost 50% reduction in the source code length. There is a slight difference between this ematch and other available ematches. Other ematches

A few days ago I had a very big problem with tc. On the machine tc is used in many ways: - from crontab to load night-time and day-time bandwidth (at 1am and 8am) - from crontab to get statistics for qdiscs on WAN interfaces (every minute) - from perl/php database for changing user bandwidth (sometimes) What happened: At 1am the night-time bandwidth should be loaded. tc hanged up, and also

Hi ; HTB2 patch for kernel 2.2.17 HTB2 patch for iproute2 Here is my script : tc qdisc del dev eth0 root tc qdisc add dev eth0 root handle 10： htb default 20 tc class add dev eth0 parent 10: classid:10:1 htb rate 90mbit ceil 90mbit burst 2000 tc class add dev eth0 parent 10:1 classid 10:100 htb rate 10mbit ceil 30mbit prio 1 tc class add dev eth0

Hello! I need to switch from htb2 to htb3, because of speed issues (for me, htb2 is unable to handle more then 100mbit duplex with ~550 classes), kernel profiling shows htb_dequeue_prio at 1st place with 3x isolation. So, I''ve moved from 2.4.19 to 2.4.25 kernel (hi-pac for classification/marking and htb3 for queueing), and traffic rate drop from 100 to 20mbit. What can be wrong? The

http://developer.osdl.org/dev/iproute2/download/iproute2-050816.tar.gz Update to iproute2 to include: * Limit ip neigh flush to 10 rounds * tc ematch support (thomas) * build cleanups (thomas, et al) * Fix for options process with ipt (jamal) * Fix array overflow in paretonormal distribution build * Update include files to 2.6.13 * Decnet doc update (Steven Whithouse) Note: the ematch

I ''m having a problem identical to one encountered on this list awhile back: >I''m trying to configure dsmark qdisc on 2.6.11.4 user mode linux and >tc from iproute2-2.6.11-050314. > > >I think I have some mismatch in my setup since adding dsmark qdisc >fails *unless* I specify "set_tc_index" argument which I believe should >be optional:

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:

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

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

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

Hi, I am tring to setup AF on my router using GRED/HTB. I plan to mark and set the DSCP with iptables and the ingress qdisc to set the tc_index for the proper GRED vq(1-12). My question is: Is there a way to allow for priority between the af classes and within the af classes? also would it be possible to to the following: HTB(6Mb) | GRED(1)grio HTB1 (af1) (1MB) GRED(1-3)grio |

Hello all, I am compiling a 2.4.19 kernel. I downloaded the kernel source from familiar project, which is a project working on porting linux to ipaq handheld devices. The question I have is what patch should I apply: htb3 or htb2? Also, I looked into htb3 patch. There are the source for sch_htb.c and some definitions that should be added to pkt_sch.h. I already have a sch_htb.c in my kernel

Hello! One simple question regaring htb2->htb3 way. I''m using 2.4.25 kernel with tc3 from Devik''s site, RH9. My data flow is about 100Mbit duplex and is subject to grow, so I''m creating root class with 200Mbit rate, with r2q=10, quantum = rate/r2q, and 1500 < quantum < 200000 (sch_htb.c) with such r2q my default shaping window will be from 120Kbit to 16Mbit,

hello is there any one who lnow what is the signification of ''@@ -2,6 +2,7 @@'' in the patch file htb2-2.4.17.diff thanks ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

I have a doubt. What''s the correct use of mangle for the next network: eth0: 200.39.190.249 (public) eth1: 192.168.101.254 (private) I make nat with iptables and have the following htb script: tc qdisc add dev eth1 root handle 1: htb default 30 tc class add dev eth1 parent 1: classid 1:1 htb rate 10mbit burst 15k tc class add dev eth1 parent 1:1 classid 1:10 htb rate 15kbit ceil 10mbit