There are a lot of servers in clusters that have nothing to do with the Napster
corporation -- look up "opennap" for one example -- these servers are run by
individuals and can be on almost any port and don't require users to register
at the main Napster servers.
A much better way to handle this is to simply make sure the AUP contains a
clause that Napster and other music/video sharing software is not permitted (or
only permitted up to a certain traffic level) and then use Snort or another
traffic watching program to watch for the Napster command sequences in packets
-- that logging can then be used to reprimand and/or point out to users that
you're serious.
Note: I have frequently used Napster to grab copies of songs I own at home
while I'm at work.
brett king wrote:
> correct me if I'm wrong, but the napster application needs to contact a
> server, somewhere on 64.124.41.0/24, to register the user as being 'online',
> send a list of what is shared on the client, and retrieve stats of users/
> files, and eventually mp3s =]. Would blocking all traffic from inside to
> 64.124.41.0/24, on the appropriate services (7777, 8875, 8888) hence be
> effective in controlling registration - upstream of controlling file sharing
> ?. This is what I do, and it seems effective, I also set to mail myself when
> a user attempts to connect to the above network (gets dropped), or connects
> to other networks on the above services, (gets allowed, eg sun answerbook
> uses 8888).
> Although this might not be absolute in controlling registration (other
> napster servers outside 64.124.41.0/24), it's better than finding out your
> traffic bill is largely comprised of sharing music =]
--
Michael T. Babcock (PGP: 0xBE6C1895)
http://www.fibrespeed.net/~mbabcock/
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
