We've seen problems with that classification as well, when we had software using HTTP on port 6699 and 7777....it was classified as Napster-Cmd as well. We put in a case for this with Packeteer, and even included a tracedump so they could rework the filter, but apparently they haven't fixed it. We ended up just ignoring traffic to that machine eith an exception rule. --Matt Julian Y. Koh wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > We've got a bunch of people here trying to talk to a MUD server outside our > campus. For some reason our PacketShaper is classifying the traffic as > Napster-Cmd. They telnet to port 7777 on the MUD server. Does the > Napster-Cmd class simply look at port number or what? > > Currently I've set up a general exception class to ignore all IP traffic > inbound/outbound from this external server. Would it be better to set up > the exception within the Napster class itself?
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature