OIT Network Switching and Routing

Visitor IP Service Change to also Serve Registered Devices; Retirement of OIT Mobile IP Service on 'guestnet'

OIT Networking & Monitoring Services
November 20 2018
Last Updated: January 20 2019

On December 6 2018, the following changes will be made on the network guestnet. (The guestnet network is one designed for use by wired devices in Palmer House, the University's guest house.)

Prior to this change, devices registered in the Host Database visiting the guestnet network would receive OIT Mobile IP Service. Following this change, such devices will instead receive Visitor IP Service.

Detailed Information

OIT plans to replace its present CMU+PU DHCP service with Infoblox DHCP service in the near future. This is part of OIT's planned Retirement of the Princeton University Host Database and Related Services. Unlike the old CMU+PU DHCP service, the Infoblox DHCP service we will be deploying will not support both kinds of services (Visitor IP Service and Mobile IP Service) on a single network.

To allow us to continue to provide a service similar to Visitor IP Service on the guestnet network in the future, we must stop providing one of those services on that network.

As the primary purpose of guestnet is to provide service to Palmer House visitors' devices not necessarily registered in the Host Database, we are choosing to continue to provide Visitor IP Service and to retire Mobile IP Service on that network. To continue to provide service on that network to devices registered in the Host Database which visit guestnet, we are modifying the behavior of Visitor IP Service so it will also service registered devices.

Devices affected by this change are those which are registered in the Host Database as homed on a network other than guestnet, when these devices visit guestnet. Instead of continuing to obtaining OIT Mobile IP Service on that network, they will instead obtain Visitor IP Service on that network.

Visitor IP Service clients are in the princeton.org DNS domain (rather than the princeton.edu DNS domain). This could change the services the client has access to while using that service; for example, it may not be able to access services limited to clients in the princeton.edu DNS domain. If this presents a problem for the customer,the client should attach the device to the campus network via another mechanism; for example:


A service of OIT Network Switching and Routing
The Office of Information Technology,
Princeton University