: > This is a topic I get very soap-boxish about. I have too : > many problems with providers who don't understand the college : > student market. I can think of one university who requires : > students to login through a web portal before giving them a : > routable address. This is such a waste of time for both : > parties. Sure it makes tracking down the abusers much : > easier, but is it worth the time and effort to manage? This : > is a very legitimate idea for public portals in common areas, : > but not in dorm rooms. In a dorm room situation or an : > apartment situation, you again know the physical port the : > DHCP request came in on. You then know which room that port : > is connected to and you therefore have a general idea of who : > the abuser is. So whats the big deal if you turn off the : > ports to the room until the users complain and the problem is : > resolved? Since no one's mentioned it, the program everyone is referring to is netreg: www.netreg.org www.net.cmu.edu/netreg Also, most .edueyeball networks have (and have always had) a VERY low budget for networking stuff. As a result, generally, there is little to no plant map documentation, so it isn't the case of looking up the physical port on a map and shutting it off. Netreg allows you to "bad web" folks. They can go nowhere until they call the helpdesk. It's a great LART. >:-) <=== That's an evil smile... scott