[142930] in North American Network Operators' Group
Re: high performance open source DHCP solution?
daemon@ATHENA.MIT.EDU (Jay Ashworth)
Wed Jul 20 20:19:50 2011
Date: Wed, 20 Jul 2011 20:19:40 -0400 (EDT)
From: Jay Ashworth <jra@baylink.com>
To: NANOG <nanog@nanog.org>
In-Reply-To: <CAAAwwbUDj4yGudeVRohAPywj=39ZjMApt0KYJw8Wa2sZhb9qcg@mail.gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
----- Original Message -----
> From: "Jimmy Hess" <mysidia@gmail.com>
> Of course, committing to a RAMDISK tricks the DHCP server software.
> The danger is that if your DHCP server suffers an untimely reboot, you
> will have no transactionally safe record of the leases issued, when
> the replacement comes up, or the DHCP server completes its reboot cycle.
>
> As a result, you can generate conflicting IP address assignments,
> unless you:
> (a) Have an extremely short max lease duration (which can increase
> DHCP server load), or
> (b) Have a policy of pinging before assigning an IP, which limits DHCP
> server performance and is not fool proof.
I think a lot of this depends on the target audience of your server.
It sounds like he's in a commercial WAN environment, which of course is what
those rules were written for. But I can't tell you how many service calls I
have to take because of address conflicts on home LANs behind consumer
routers... which don't generally cache the assignments at all, IME.
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
_____
NANOG mailing list
NANOG@nanog.org
https://mailman.nanog.org/mailman/listinfo/nanog
