On Mon, 30 Apr 2001 [EMAIL PROTECTED] wrote:
<snip>
> The best way, if they are lab classes anyway, is administrative.
yup... block everything that you can and tell them what they can and
can't do ... then trust them ... and have a packet sniffer just for backup
;)
IMHO, i'd block everything from workstation students use and give them
private ip's (from rfc1918) . Then I'd use a proxy for http (and/or ftp)
traffic... and if you catch students going to "disallowed" or "unethical"
sites, you've got the logs to back you up.
<snip>
> .. traffic shape all connections to and from the official
> napster servers.
I don't think this would be feasible. napster clients directly connect to
other clients for file transfers... totally bypassing the servers .. the
servers just contains client ips and the files that they have.
hth,
-mark
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
