1 / 10

University of Michigan Residence Halls Networking

University of Michigan Residence Halls Networking. In-Room Student Registration System http://www.umich.edu/~insite. Overview. 3-tier system (Web/CGI, Oracle Daemon, Java Client) DHCP-based Automated - users provide minimal data Secure - interface-to-daemon communications are encrypted.

telma
Download Presentation

University of Michigan Residence Halls Networking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. University of Michigan Residence Halls Networking In-Room Student Registration System http://www.umich.edu/~insite

  2. Overview • 3-tier system (Web/CGI, Oracle Daemon, Java Client) • DHCP-based • Automated - users provide minimal data • Secure - interface-to-daemon communications are encrypted

  3. Communications • Campus routers configured to forward DHCP requests to single server • DHCP server issues 10.x.x.x addresses, based on network of request origin • User connects to internal SSL-protected web page • CGI obtains uniqname, MAC, network origin and sends information (protected by Kerberos) to the Oracle daemon

  4. Communications (cont) • Oracle daemon matches uniqname to prestuffed student housing data • Database maintains linkage between user/location data and MAC/IP address • Cron job reads Oracle information and generates a new DHCP configuration file • ISC DHCPD server restarted every five min

  5. Registration Diagram

  6. Diagram Guide • Client requests IP from DHCP server; server responds with a 10.x.x.x address • Client contacts internal, SSL-protected webpage; CGI uses kerberos to authenticate and verify the username and password • The CGI sends uniqname, IP address, and OS to the SQL daemon; • Sqld does an ARP lookup on the router to determine the MAC address • Sqld queries the Group Server to determine if user is allowed to access this specific network • Sqld attempts to associate username with prestuffed user location data; if this is not successful, it attempts to fill this data by doing and LDAP query to X.500 • If the registration is successful, a new entry is added to the DHCP configuration file, and the client machine is assigned a real, routed IP address which replaces the unrouted 10.x.x.x address. • The Java client is an administration tool that allows network administrators to use a GUI to configure and partitions subnets, and to make modifications to student data and IP assignments.

  7. Deployment Results

  8. Drawbacks • Users can bypass DHCP and assign themselves a static IP • DHCP server must be restarted for updates to take place • Users must go to a specific URL to complete the registration • Users can not have network access on another network without administrative intervention

  9. Advantages • Efficient use of IP space • Students are not required to know the MAC address of their NIC • Contact/location info is gathered from reliable source rather than having students or consultants enter the data • Requires very little administration time beyond initial configuration of networks

  10. Future Directions • Improved access control through use of V-LAN configurable switches • More feedback and options in the CGI, allowing users to submit changes to their registration • Continued development of the java administration tool • Modularization of code • Allow machines to “roam” on allowed networks

More Related