Re: Napster..

[John Ladwig <jladwig () aravox com>]

> I simply dropped all traffic to/from www.napster.com's class C.
> Seems to have done the trick quite nicely.

And it will continue to do so until someone learns how to use one of the
(many) public SOCKS proxies for the Napster directory service agents,
and then tells everyone else.

That took about 48 hours at the major US university I used to be affiliated
with.

And, responding to another note in the thread, blocking 6699/tcp will stop
any Napster user who doesn't have the wit to change the transfer
port on his user agent.  The transfer port can be changed without
penalty, because (IIRC) the directory includes information on the user 
agents' transfer ports.


Napster's really a fascinating piece of work, from a protocol standpoint.

    -jml

_______________________________________________
firewall-wizards mailing list
firewall-wizards () nfr com
http://www.nfr.com/mailman/listinfo/firewall-wizards