[148490] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: enterprise 802.11

daemon@ATHENA.MIT.EDU (Jay Ashworth)
Mon Jan 16 12:44:23 2012

Date: Mon, 16 Jan 2012 12:43:33 -0500 (EST)
From: Jay Ashworth <jra@baylink.com>
To: NANOG <nanog@nanog.org>
In-Reply-To: <416410D3-653F-4716-BF68-84E0F81E3F1F@puck.nether.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

----- 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.

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra@baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274


home help back first fref pref prev next nref lref last post