enterprise 802.11

Robert E. Seastrom rs at seastrom.com
Wed Jan 18 18:00:37 UTC 2012


Jay Ashworth <jra at baylink.com> writes:

> ----- Original Message -----
>> From: "Jared Mauch" <jared at puck.nether.net>
>
>> network side. I'm personally not convinced of the value of very short
>> lease times (less than an hour)
>
> Less than an hour, perhaps not. 
>
> On small residential networks, though -- generally, anything where the 
> router (which will need to get rebooted occasionally) *is* the DHCP server --
> I tend to set the timeout to 30-60 minutes, to reduce the race window between
> when a router is rebooted, and when a new device shows up and conflicts 
> because it's given an IP another device still thinks it owns.

Another thing that works (in environments where you can get away with
it) is an enormous dhcp pool and super long leases with
walking-the-whole-space behavior and persistent-across-reboots
behavior on the part of the DHCP server.

The built-in server on the Mikrotik platforms will do this.
Configuring a /16 worth of 1918 space with a 3 week lease for a
campground that typically hosts 1 week long events has handily dodged
the issue for me.  Admittedly this is a corner case...

-r






More information about the NANOG mailing list