Subject: Re: IMQ again WAS(Re: iptables breakage WAS(Re: dummy as IMQ replacement

From: Andy Furniss <[email-masked]>
Date: Mon, 28 Mar 2005 15:12:21 +0100

jamal wrote:
> On Mon, 2005-03-28 at 08:45, jamal wrote:
> 
> 
>>Dont see why this shouldnt work. You are saying it works with
>>non-aliased interface addreses?
>>
> 
> 
> Tested - worked fine here. I know those error messages suck and we can
> do better in the future. Double check your kernel has police compiled
> in.

Hmm - it works on ingress and all I really wanted to do was

tc filter add dev eth0 parent 0: protocol ip prio 10 u32 match ip src 
0/0 action mirred egress redirect dev dummy0

[root@amd /home/andy/Qos]# tc qdisc add dev eth0 ingress
[root@amd /home/andy/Qos]# tc filter add dev eth0 parent ffff: protocol 
ip prio 10 u32 match ip src 192.168.200.200/32 flowid 1:2 action police 
rate 100kbit burst 90k drop

[root@amd /home/andy/Qos]# tc -s filter ls dev eth0 parent ffff:
filter protocol ip pref 10 u32
filter protocol ip pref 10 u32 fh 800: ht divisor 1
filter protocol ip pref 10 u32 fh 800::800 order 2048 key ht 800 bkt 0 
flowid 1:2  (rule hit 3 success 0)
   match c0a8c8c8/ffffffff at 12 (success 0 )
         action order 1:  police 0x1 rate 100000bit burst 90Kb mtu 2Kb 
action drop
ref 1 bind 1
         Action statistics:
         Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
         rate 0bit 0pps backlog 0b 0p requeues 0

Andy.