[26865] in North American Network Operators' Group
RE: Napster & other bandwidth hogs
daemon@ATHENA.MIT.EDU (Charley Kline)
Mon Jan 24 16:03:00 2000
From: "Charley Kline" <kline@uiuc.edu>
To: "Ryan Bek" <rbek@gborocollege.edu>
Cc: <nanog@merit.edu>
Date: Mon, 24 Jan 2000 14:51:16 -0600
Message-ID: <NDBBLJEILKJEKNKGEOAMAEIPCAAA.kline@uiuc.edu>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20000124175658983.AAA495.371@callisto>
Errors-To: owner-nanog-outgoing@merit.edu
> Since these apps are becoming more and more prevalent, as college
> students are
> huge collectors of digital music, and as bandwidth is always a
> concern, I am
> wondering what others in either the educational or business community are
> doing in light of this. Even having logistical information such
> as, "close
> ports x, x, and x" would be of assistance. I'd just like to have some
> ammunition in case others higher on the food chain ask for this to happen.
The decision to block access to napster here was made at a higher level than
this writer, so I can't speak to the policies involved. I can however,
without further comment, reproduce the access list that seems to have
effectively cut them off:
deny ip 208.49.228.0 0.0.0.255 any
deny ip 208.184.216.0 0.0.0.255 any
deny ip 208.49.239.240 0.0.0.15 any
deny ip 208.178.175.128 0.0.0.7 any
deny ip 208.178.163.56 0.0.0.7 any
It's the second line that gets most of the hits.
--
Charley Kline, Principal Research Programmer kline@uiuc.edu
Data Communications Architect (217) 333-3339
Computing and Communications Services Office
University of Illinois at Urbana-Champaign
