similar to: filtering ipv6

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

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 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();

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

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:

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,

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:

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

hello, is there any tool to support IPv6 in IPv6 or IPv6 in UDP over IPv6 out of the box solution (preferably :P)? Greetings, Marius Corici _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

* sorry for the 2 previous schemas, they came out a mess. I hope this one is understandable. hi: I have this 2 boxes set up like this: 2020::2/128 2020::254/128 3030::254/128 192.168.0.2/24 192.168.0.254/24 192.168.30.254/24 +-------+ eth0 eth3 +-------+ | |==================== | | eth1 | A | | B | ---- | |

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

I have been studying traffic control in linux these days. I became to know there are several qeueuing displines such as tbf, cbq, htp, etc. But, there isn't the comment whether they support IPv6 traffic. I got this question because there is no comment about how to connect qdisc classes with IPv6 flow using "tc filter" command, and I think the "tc filter" command

I''m running fedora core 2 with 2.6.7 kernel when I have /proc/sys/net/ipv6/conf/all/forwarding Set on Listening Deamon''s will not respond to Sync requests. if I turn it off which breaks routing of course. then the Deamons can make connections. Is this suppost to be normal behavior when the box is routeing IPv6? This only happens with ipv6 connections.

Hi all, I have a dual stacked (IPv4/IPv6) Linux host (S) with two interfaces that can both be used to reach a destination (D) and are both up. In order to make sure a packet is transmitted over the correct interface I use policy based routing to choose the correct routing table based on the IP source address. The network setup is shown below: |---| | D | |---| | | |---|

hi i am running Debian/GNU Linux with 2.4.26 kernel and radius server my kernel conf looks like this <*> Packet socket [ ] Packet socket: mmapped IO < > Netlink device emulation [*] Network packet filtering (replaces ipchains) [*] Network packet filtering debugging [ ] Socket Filtering <*> Unix domain sockets [*] TCP/IP networking [*] IP: multicasting [*] IP: advanced

hi: *I have this 2 boxes set up like this:* 2020::2/128 2020::254/128 3030::254/128 192.168.0.2/24 192.168.0.254/24 192.168.30.254/24 +-------+ eth0 eth3 +-------+ | |=======================| | eth1 | A | | B |---- | | | |