We have a policy that allows P2P traffic but limits it to 64kbps. Whenever I add kazaa2 to the list of matched protocols, all web browsing slows down to a crawl and it appears that normal HTTP traffic is being matched by this protocol. We're using IOS Version 12.3(1a) on a 7206VXR. Here's my configuration:

class-map match-all CO-LOCATED-SERVERS

match access-group 2010

class-map match-all CAR-Multicast

match access-group 162

class-map match-any P2P

match protocol http url "\.hash=*"

match protocol http url "/.hash=*"

match protocol fasttrack file-transfer "*"

match protocol gnutella file-transfer "*"

match protocol napster

class-map match-all CAR-UDP

match access-group 160

class-map match-all CLIENTS-USING-P2P

match class-map P2P

match not access-group 105

class-map match-all NACHI

match access-group 199

match packet length min 92 max 92

class-map match-all WIRELESS-CLIENTS

match access-group 104

class-map match-all CAR-ICMP

match protocol icmp

!

!

policy-map LIMIT-UDP-ICMP-MULTICAST

class CAR-UDP

police 1024000 16000 16000 conform-action transmit exceed-action drop

class CAR-ICMP

police 64000 conform-action transmit exceed-action drop

class CAR-Multicast

police 512000 16000 16000 conform-action transmit exceed-action drop

policy-map NACHI-WORM

class NACHI

drop

policy-map POLICE-TRAFFIC

class WIRELESS-CLIENTS

police 512000 16000 16000 conform-action transmit exceed-action drop

class CLIENTS-USING-P2P

police 64000 2000 2000 conform-action transmit exceed-action drop

class CO-LOCATED-SERVERS

police 128000 4000 4000 conform-action transmit exceed-action drop

class class-default

service-policy LIMIT-UDP-ICMP-MULTICAST