Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Re: one-lease-per-client... seriously (Glenn Satchell)
----------------------------------------------------------------------
Message: 1
Date: Mon, 19 Sep 2016 11:17:25 +1000
From: "Glenn Satchell" <glenn.satch...@uniq.com.au>
To: "Users of ISC DHCP" <dhcp-users@lists.isc.org>
Subject: Re: one-lease-per-client... seriously
Message-ID:
<23c95d8373c13d8d93a3c49b828f182a.squir...@mail.uniq.com.au>
Content-Type: text/plain;charset=iso-8859-1
On Sun, September 18, 2016 5:21 pm, Chuck Anderson wrote:
> On Fri, Sep 16, 2016 at 08:00:15AM +0100, Simon Hobson wrote:
>>
>> On 15 Sep 2016, at 21:00, Brian Rak <b...@gameservers.com> wrote:
>>
>> > I'm running into an issue where DHCPD (v4.3.4 and older versions) is
>> issuing multiple leases to the same mac address. It appears to be
>> looking at the DHCP Client-ID field to determine what a unique client
>> is.
>>
>> That is by design as is **REQUIRED** by the RFCs.
>> It's a long standing problem that some real-world situations clash with
>> this - most notably when there is multi-boot with Windoze and anything
>> else since Windows defaults to using the MAC address as client-id and
>> everything else defaults to not sending one. But that's what the
>> standards require and the ISC implementation has always been intended to
>> be a "reference" implementation that completely meets the standards as
>> laid down (unlike several other servers which really do break the rules
>> a lot).
>>
>> > I'd much rather it ignore everything except for the client's mac
>> address, but I can't seem to find an option to do this.
>>
>> It used to require patches, but I see Jeff has suggested an option to
>> deal with this.
>
> A better way might be to identify the various boot stages and hand out
> very short leases for PXE, etc. That way you don't violate the
> standard, but the extra leases don't hang around for very long.
Here is how I do it:
# PXE boots for jumpstarting x86 boxes
class "PXE" {
match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";
next-server foo.example.com.au;
filename "pxegrub.I86PC.Solaris_10-1";
# 10 minutes should be long enough for PXE
max-lease-time 600;
}
regards,
-glenn
------------------------------
Subject: Digest Footer
_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 95, Issue 9
*****************************************
