|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Mon, 24 Jan 2000 15:30:59 -0500 (EST) From: Ryan Tucker <rtucker@netacc.net> To: Ryan Bek <rbek@gborocollege.edu> Cc: nanog@merit.edu In-Reply-To: <20000124175658983.AAA495.371@callisto> Message-ID: <Pine.BSF.4.21.0001241505190.23361-100000@shell.netacc.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Errors-To: owner-nanog-outgoing@merit.edu The data port is set in the user config... however, Napster's servers seem to be within the 208.178.175.128/29 block. There is a Napster FAQ at http://napster.cjb.net/ which could be useful... there's also a protocol specification wandering around, but I can't find it any more. -rt -- Ryan Tucker <rtucker@netacc.net> Unix Systems Administrator NetAccess, Inc. Phone: +1 716 756-5596 3495 Winton Place, Building E, Suite 265, Rochester NY 14623 www.netacc.net On Mon, 24 Jan 2000, Ryan Bek wrote: > > Hello all - > > I (and I presume many others) have had concerns brought to us about the > bandwidth hogging apps & services, like Napster Music Community. As many have > discovered, applications such as these can consume a good deal of a broadband > connection, as users can serve up files from their own machines, subverting [...]
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |