similar to: filtering ipv6

i wrote a C++ program that executes "tc" using the std::system call. this fairly reduces the performance if many tc calls are required. i want to be able to rename tc''s main function to tc_main and pass argv and argc. has someone done something like this? please let me know how i can compile for netem. thanks. __________________________________________________ Do You

Hi, I''m trying to use HTB for IPv6 packets. In the LARTC archive I found a thread on this issue where a solution was described. The idea is to mark a user-defined chain then use the fwmark for filtering. However my attempt wasn''t successful. I''m thinking of trying my luck with the u32 filter. This is what I did, any comment is greatly appreciated. Thank you all. tc

Hello, Perhaps I am mising something; I am trying to implement a hashing filter nearly identical to that outlined in the iproute2 docs at http://www.opens.com.br/documentacao/IPRoute2/lartc.adv-filter.hashing.html However, I dont get very far because I get "invalid argument" whenever I issue any filtering commands, eg: [root@localhost root]# tc filter add dev eth1 parent 1:0 prio 5

Hi, here I have another newcomer question :-) in the section 9.6.1 of this how too http://tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.qdisc.filters.html we can read commands about filters : ------------------------------------------ # tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match \ ip dport 22 0xffff flowid 10:1 # tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match \

Hello, I''m wondering which of these filters is the best method for filtering ACK packages to achieve lowest delay possible on a dsl-link. This one ist from the wondershaper from the lartc-site: /sbin/tc filter add dev $EXTIF parent 1:0 protocol ip prio 0 u32 \   match ip protocol 6 0xff \   match u8 0x05 0x0f at 0 \   match u16 0x0000 0xffc0 at 2 \   flowid 1:10 Thats a suggestion

Hi All Is the filter rule bellow supposed to classify icmp request/reply packets? $TC filter add dev eth2 protocol ip \ parent 1:0 prio 1 u32 \ match ip dst 192.168.0.1 \ match icmp type 8 0xff flowid 100 $TC filter add dev eth2 protocol ip \ parent 1:0 prio 1 u32 \ match ip dst 192.168.0.1 \ match icmp type 0 0xff flowid 100 it is accepted by tc but I think it is not

Hi all. I''m going on my 3rd week trying to get a simple traffic shapping to work the right way :( !! My goal it to shape the traffic coming from one machine (pc1) to another machine (pc2) throught the "eth0" interface. My test configuration is as follows: PC1   IP: 192.168.105.237   Mask: 255.255.255.0   OS: Red Hat Linux Kernel 2.4.20-8   Rules:

Hi All Is the filter rule bellow supposed to classify icmp request/reply packets? $TC filter add dev eth2 protocol ip \ parent 1:0 prio 1 u32 \ match ip dst 192.168.0.1 \ match icmp type 8 0xff flowid 100 $TC filter add dev eth2 protocol ip \ parent 1:0 prio 1 u32 \ match ip dst 192.168.0.1 \ match icmp type 0 0xff flowid 100 it is accepted by tc but I think it is not

I have a wireless internet connection.the nat is done by linux machine. eth0----lan eth1---service-provider now the script.. tc qdisc add dev eth0 root handle 1: htb default 12 tc class add dev eth0 parent 1: classid 1:1 htb rate 512kbps ceil 512kbps tc class add dev eth0 parent 1:1 classid 1:10 htb rate 384kbps ceil 512kbps-----Admin-Network tc class add dev eth0 parent 1:1 classid 1:11 htb

Hi I have defined a single HTB qdisc on eth0 with one root class 1:1 further subdivided as below, nothing complicated. 1: (root qdisc) | | 1:1 (root class) /\ / \ / \ / \ / \ 1:10 \

Simple police filter below works for IPv4 traffic, but not for IPv6 traffic. Tested with 2.4.26 and 2.6.6 kernel. Am I doing something wrong or is it bug? Same filter logic works with imq+htb for both IPv4 and IPv6 traffic. iptables -A PREROUTING -i eth1.101 -t mangle -j MARK --set-mark 0x101 ip6tables -A PREROUTING -i eth1.101 -t mangle -j MARK --set-mark 0x101 tc qdisc add dev eth1.101

hi- i''ve been trying to setup an outgoing queue that prioritizes traffic depending on whether it recognizes the MAC address the packet is destined to -- and i''ve not been having any luck. i think my ebtables rule is correct as the packet count when i do an --Lc is increasing in an expected way, but when i look at the tc statistics, i don''t think the packets are

Hi All, I used MasterShaper (The frontend of tc), after setting the high priority on ack packets, our university website just can''t be accessed while all the other website got no problems. The website is hosted on IIS 6.0, Windows 2003 The tc code below just make our university website can''t be accessed: tc qdisc add dev eth1 handle 1: root htb default 1 tc class add dev eth1

I tried to implement a multi-homed box using this faq 4.2.1 split access http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.multiple-links.html But it says table is invalid. Can someone tell me what the difference is in Centos? I assume the FAQ is leaving out how to add tables to the iproute files? I am trying to have eth0 and eth1 service two different subnets for apache and not act as a

Le 26 juil. 07 à 13:55, Georgi Alexandrov a écrit : > Vincent Dautremont wrote: > >> Hi, >> here I have another newcomer question :-) >> in the section 9.6.1 of this how too >> http://tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.qdisc.filters.html >> we can read commands about filters : >> ------------------------------------------ >> >> # tc

Hi all! On http://lartc.org/howto/lartc.adv-filter.html I read that a classifiers available bases the decision on how the firewall has marked the packet and on http://lartc.org/howto/lartc.qdisc.filters.html the following example: "tc filter add dev eth1 protocol ip parent 1:0 prio 1 handle 6 fw flowid 1:1" "iptables -A PREROUTING -t mangle -i eth0 -j MARK --set-mark 6" My

Hi, I have recently started to use ''tc'' on ipv6 traffic and have come across an issue with tc filter. As per tc_filter.c in iproute2-050816, to match ''priority'' of an ipv6 packet, the u32 filter matches against the first 8 bits of the packet. From f_u32.c: if (strcmp(*argv, "priority") == 0) { NEXT_ARG();

In regards to my earlier post, I believe that my problem is that the filter is not matching ssh traffic properly. Here are the rules that I posted earlier, with the filter being the last one: tc qdisc add dev eth0 root handle 1: htb default 3 tc class add dev eth0 parent 1: classid 1:1 htb rate 102400kbps ceil 102400kbps tc class add dev eth0 parent 1:1 classid 1:2 htb rate 102400kbps ceil

Hi, The LARTC states that it is not possible to create filters with TC for IPv6 packets. Is this situation still unchanged? I''m in need for it for an implementation of a modified version of the TIA-1039, http://www.packet.cc/TIA1039ID.htm. I''m not sure if this is the correct mailing list. If not I apologize and hope that someone can point me in the right direction :-) Cheer,

https://bugzilla.netfilter.org/show_bug.cgi?id=1062 Bug ID: 1062 Summary: Kernel IPv6 event filtering not working Product: conntrack-tools Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: normal Priority: P5 Component: conntrack-daemon Assignee: