Why don't you just block the TCP-ports used by Napster? Denying traffic
to/from ports 6699 and 8888 ought to do the trick. Or?
//Robert
"Young, Beth A." wrote:
>
> The white paper is not done (too many other projects right now to finish it)
> but here is the gist of the traffic patterns. Since I got enough off-list
> email expressing interest, it seems appropriate to post it here.
>
> I used a router to block incoming SYN packets to my IP address which blocked
> napster traffic from my machine until I changed the client setting to "I
> live behind the firewall." At that point, people started downloading from
> me again because my client would initiate the SYN. It also doesn't do any
> good to block the napster subnet range. While that works 95% of the time,
> there are other napster servers out there that do not live in the napster
> 64.124.41.0 network.
>
> A co-worker is looking at Packet Pup as a way to block napster but we are
> kind of unique in that we don't care if students download files but we don't
> want to be the main supplier of songs so we want to block downloads from us.
> *shugs* any suggestion on that front would appreciated.
>
> -Beth
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
