Problems with blocking Kazaa2

[lawrenceroppcatv]

When I block Kazaa2 using the built-in kazaa2 pdlm on my ubr7223, it all works fine for a while (a few hours to a few days). But then, out of no where, it suddenly starts blocking other traffic, such as pop3 or DNS traffic. I can remove the kazaa2 block, and everything starts working again (including kazaa, which is NOT what I want). Anyone else having this issue, and how can I resove it? I can send a copy of my config if that would help.

[mesuti]

I tried to block kazaa2 and it was successful, but I don't know why it experiences you problems, I would propose you to try to block the fast-track

class-map X

match protocol fasttrack

also another solution is to block on http with string

match protocol http url "x-kazaa"

I'm not sure about the string x-kazaa, maybe you should sniff the kazaa packets before trying the http example.

hope it helps

Best Regards

Mesut Abdurrahmani

[lawrenceroppcatv]

I'm already blocking fasttrack, as well as others. I don't have a problem blocking them; only Kazaa. Here is a snip from my config file reguarding the file-share blocking.

*snip*

class-map match-any p2p

match protocol fasttrack

match protocol gnutella

match protocol winmx

match protocol http url "\.hash=*"

match protocol http url "/.hash=*"

!

!

policy-map p2p

class p2p

police cir percent 1

exceed-action drop

violate-action drop

interface Cable2/0

ip nbar protocol-discovery

service-policy input p2p

service-policy output p2p

*end-snip*

If I add kazaa2 to this mix, pop3 gets blocked or limited (depending on how I have the policy-map setup). And, of course, no one can check their e-mail then, which equals VERY ill customers.