[905] in resnet
Re: Forced Registration & DHCP
daemon@ATHENA.MIT.EDU (Daxter Gulje)
Thu Feb 28 12:23:31 2002
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Message-ID: <EF6375215231544B87FD58A965410B8AC5678F@exchange.housing.ucsb.edu>
Date: Thu, 28 Feb 2002 09:14:10 -0800
Reply-To: Resnet Forum <RESNET-L@listserv.nd.edu>
From: Daxter Gulje <dgulje@HOUSING.UCSB.EDU>
To: RESNET-L@listserv.nd.edu
Hi Keri-
As many folks on this list will probably tell you, there is an absolutely wonderful system designed to do just what you are asking about; register every student on your network, along with their MAC & IP address.
I can't imagine running static IPs for that many connections...we've got around 3500 or so active connections, and it's all done via DHCP. Yes, you will get problems with students running their own DHCP servers/Access Points/Airports that can cause headaches, but they are for the most part, easily surmountable. The risk of students running DHCP servers (maliciously or by accident) isn't so great with XP as it is with Win2k Server or Unix/Linux, as well as Apple's AirPort users.
Back to the registration issue - I can't recommend forcing registration enough. Keep in mind that using your network that is a demographic famous for either breaking the rules or actively finding ways around them. This means everything from DMCA violations, to DoS attacks, to massive e-mail spam (as I'm sure you're already well aware). Having every client registered through the NetReg system (http://www.southwestern.edu/ITS/netreg/) transforms the process of tracking down a user, something that could take over an hour, to a matter of seconds.
It may take a bit of tricking out on your part to get the system to work with your University (we ended up writing an entirely new authentication model), but it is absolutely worth it.
/Dax
__________________________________________
Daxter Gulje
Assistant ResNet Coordinator
University of California, Santa Barbara
805.893.4747
-----Original Message-----
From: Keri Budnovitch [mailto:kbudnov@MSSG.RUTGERS.EDU]
Sent: Thursday, February 28, 2002 8:51 AM
To: RESNET-L@listserv.nd.edu
Subject: Forced Registration & DHCP
Hello,
I am from Rutgers University and we have approximately 10,000+ resnet connections. We are using static IP addresses. I am anxious to switch to DCHP and forced registration to make it easier on the Help Desk at the beginning of the semesters.
There have been concerns about switching to DHCP because of the possibility of students running their own DHCP servers, especially with Win XP. Can anyone share if they have similar concerns and how you plan to handle it? Also, feel free to list your experience with the pros and cons of DHCP vs. static IPs.
Also, do you suggest forcing students to register their computer from day one?
Any insight would be appreciated.
Thanks!
Keri
_______________________________________________________
Keri Budnovitch, Manager, Help Desk and Educational Services
RUCS - New Brunswick Computing Services
54 Joyce Kilmer Ave, Lucy Stone Hall B304
Piscataway, NJ 08854-8045 Voice: 732-445-6967
kbudnov@mssg.rutgers.edu Fax: 732-445-3332
Help Desk: 732-445-HELP (4357)
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
