nanog mailing list archives
Re: enterprise 802.11
From: "Robert E. Seastrom" <rs () seastrom com>
Date: Wed, 18 Jan 2012 13:00:37 -0500
Jay Ashworth <jra () baylink com> writes:
----- Original Message -----From: "Jared Mauch" <jared () 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
Current thread:
- Re: enterprise 802.11, (continued)
- Re: enterprise 802.11 Joel jaeggli (Jan 16)
- Re: enterprise 802.11 Jon Sevier (Jan 16)
- Re: enterprise 802.11 Valdis . Kletnieks (Jan 16)
- SV: enterprise 802.11 Andreas Larsen (Jan 16)
- RE: enterprise 802.11 Martin Hotze (Jan 16)
- Re: enterprise 802.11 Anurag Bhatia (Jan 16)
- RE: enterprise 802.11 Martin Hotze (Jan 16)
- Re: enterprise 802.11 Tim Franklin (Jan 16)
- Re: enterprise 802.11 Jared Mauch (Jan 16)
- Re: enterprise 802.11 Jay Ashworth (Jan 16)
- Re: enterprise 802.11 Robert E. Seastrom (Jan 18)
- Re: enterprise 802.11 Anurag Bhatia (Jan 16)