This is a list of the current Temporary Unregistered Dormnet IP address assignments made by the OIT DHCP servers. For general information about Temporary Unregistered Dormnet (TUD) IP addresses, see Temporary Unregistered Dormnet IP Address Service.
See the How to Interpret This Table section at the end of this document for information to help you interpret this data.
This document is updated several times each hour; this one was produced at 11:16:03 pm Fri May 16 2008. It is based upon snapshots from the following OIT DHCP servers:
It typically takes up to 10 minutes for a new DHCP lease (or the renewal or expiration of an old DHCP lease) to be reflected below.
| Client's Hardware Address | Temporary Unregistered Dormnet IP Address and Hostname | TUD Service First Began | Lease Duration and Expiration Time | DHCP Server |
|---|---|---|---|---|
| 0:12:3f:e0:3:c | 140.180.184.87 temp-oit-unregistered-dormnet-b-2 | 4:51 pm Thu May 15 2008 | 1 hour 12:13 am Sat May 17 2008 | alfrente |
| 0:14:22:f2:e7:17 | 140.180.184.86 temp-oit-unregistered-dormnet-b-1 | 11:11 am Thu May 15 2008 | 1 hour 11:50 pm Fri May 16 2008 | alfrente |
| 0:1e:8c:7c:dd:67 | 140.180.184.171 temp-oit-unregistered-dormnet-c-1 | 10:21 pm Fri May 16 2008 | 1 hour 11:48 pm Fri May 16 2008 | capserver |
| TUD IP Addresses currently leased to clients: 3 (out of 255) | ||||
The table above shows all the leases for Temporary Unregistered Dormnet IP Addresses that have not yet expired. If all TUD IP Address leases have expired, no table will appear above.
Each row of the table describes a single Temporary Unregistered Dormnet IP address assignment (a.k.a "lease"). At the end of the table is the number of Temporary Unregistered Dormnet IP addresses currently assigned to customers, along with the total number of allocated.
Only Temporary Unregistered Dormnet IP address assignments appear in this document. Assignments of static IP addresses and Mobile IP Addresses do not appear.
If a OIT DHCP server is down (e.g. for planned maintenance or due to a failure), the most recent snapshot from it may not be "recent". The information in this document will then reflect the most recent snapshot provided by that server, if any; you can judge for yourself if that's current by checking the section above entitled When Was This Document Updated.
If no snapshot is available from a DHCP server, this document will not reflect the assignments granted by that server; assignments granted by other servers will still appear.
A device that has become ineligible for TUD may continue to appear in this document for several hours after becoming ineligible, until its final lease expires.
As described in Temporary Unregistered Dormnet IP Address Service, TUD service is deemed to have ended when any of the following is true: the client is subscribed to Dormnet, the client is registered in the Host Database as an office machine, the client is absent from the Dormnet network for six or more days, or the client is declared a TUD Camper.
If the client device remains attached to the same network, continues to use IP, and has correctly-working DHCP software, then before the lease expires the client will automatically attempt to renew (extend) its lease from the OIT DHCP server that granted the lease.
OIT operates several DHCP servers to provide a measure of redundancy. Any of these servers can provide a new lease to a client; once a client has obtained a lease on a Temporary Unregistered Dormnet IP address, only the server that originally granted that lease can grant a renewal on it; the DHCP client is bound to this server.
Each DHCP server maintains its state across reboots or other failures; when the DHCP server restarts, any unexpired leases are still valid.
Because a DHCP client typically attempts to renew its lease halfway through its duration and will retry in the background until it succeeds or the lease expires, the client is not affected by a brief outage of the DHCP server to which it is bound. If a client is unable to renew its lease before it expires, the client loses the IP address, and must go through a discovery process to obtain a new one from any DHCP server (behavior on specific client platforms may vary).