We have had short lease times [10 minutes] in the past. The problem is that if you have to track down an IP for network "forensics", you could be sure you were talking about the same device.
We found that we could feel more confident about our network troubleshooting if we had longer leases. Since we use NAT, I'd rather have the longer lease time and add additional networks as needed. Our configuration allows a user to move across campus and maintain the same IP; but with a short lease one might not be able to get across campus and get the same IP. Dennis Rigdon, MCSE Asst. Dir. Campus Technology - Network Services Okla. City Univ. 405-208-5849 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Garrett Harmon Sent: Wednesday, September 30, 2009 1:09 PM To: [email protected] Subject: [WIRELESS-LAN] wireless DHCP lease time We're running into some issues at the ramp up of a quarter with our DHCP lease time attempting to utilize the /24's we currently pool for our main essid. We moved from 1hr. to 30 minutes, but are still running out of leases occasionally. For instance, we have 160 users in a /24, but due to the transient nature of wireless/classes leases that are used for a brief moment the cycle isn't quite efficient enough. What is everyone else using for wireless DHCP lease times? I know I can just add another /24 to the pool, but the networks are not being utilized enough. We want to try 15 minutes but are wondering if we will start to run into issues related with that? Your input is greatly appreciated!! Garrett Harmon Network Engineer Office of Information Technology The Ohio State University 614.292.2122 (o) 614.747.5539 (c) ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
