Hosts placed on the Tufts network must have their MAC addresses registered. This is done to help correlate machine user/owner with network activity. New hosts can have their MAC address registered one of two ways:
1. From another machine that is already on the Tufts network, via the hostreg.net.tufts.edu registration portal. Regular users can utilize the user portal at https://hostreg.net.tufts.edu/ to register their own machines. The administrative limits on number of machines a user can have registered to their UTLN is enforced here for users. FSPs and other administrative portal users should use the admin portal at https://hostreg.net.tufts.edu/admin to do proxy registration for others. You can indicate the UTLN for the user in the "registered for" field on the administrative registration page. The administrative portal does not enforce the per-UTLN limit on registered machines.
2. From a new machine placed on a DHCP network or connected to the Tufts (non-guest) wireless network. Some systems will detect that they are behind a portal and immediately prompt the user for a UTLN login. If not, any attempt to connect to a remote web host will redirect the user to the captive portal, https://portal.net.tufts.edu. The captive portal enforces the per-user limits on number of machines registered to a given UTLN.
New DHCP registrations created via the portal.net.tufts.edu captive portal will take effect on that campus immediately if you do a DHCP release/renew to refresh the lease; if you let the lease expire and renew on its own, it should take 3-4 minutes, at most. New DHCP registrations created via portal.net.tufts.edu will be effective on other campuses within half an hour when the next scheduled DHCP deployment occurs.
New DHCP registrations created via the hostreg portal will take effect everywhere after the next scheduled DHCP deployment. These deployments occur every hour at 20 and 50 past the hour.