Displaying 1 result from an estimated 1 matches for "00000c38".
Did you mean:
  00000038
  
2001 Dec 13
14
tc: u32 match in nexthdr not working?
...kbit burst 10k drop flowid :1
Even if
# tc filter ls dev eth0 parent ffff:
filter protocol ip pref 50 u32
filter protocol ip pref 50 u32 fh 800: ht divisor 1
filter protocol ip pref 50 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid :1
police 4 action drop rate 40Kbit burst 10Kb mtu 2Kb
  match 00000c38/0000ffff at nexthdr+0
looks reasonable, TCP connections to port 3128 are not policed.
If I use "match ip dst <ip-address>" instead, the policing works.
Port based matching isn''t working for outgoing shapers either, as
can be seen with the statistics functions.
Any idea?...