BOOTP from dynamic client and no dynamic leases

Andrew Falanga af300wsm at gmail.com
Sun Aug 10 03:19:44 UTC 2008


On Sat, Aug 9, 2008 at 7:28 AM, Glenn Satchell
<Glenn.Satchell at uniq.com.au> wrote:
>
>>Date: Fri, 8 Aug 2008 12:03:48 -0600
>>From: "Andrew Falanga" <af300wsm at gmail.com>
>>To: dhcp-users at isc.org
>>Subject: BOOTP from dynamic client and no dynamic leases
>>
>>Hello,
>>
>>I'm searching for help in resolving the issue that manifests itself
>>with the error message, "BOOTP from dynamic client and no dynamic
>>leases," in my new dhcpd server setup.  This server is only to service
>>bootp clients, though these clients aren't actually using bootp to
>>boot anythng they're just getting an IP address, and I continually get
>>this error.  My IP setup is where I work and I don't run the IT
>>situations.  My team regularly changes hardware and to meet the demand
>>we were given a small block of IP within the subnet in which we
>>operate to use on a local bootp server.  Our existing server is having
>>problems and is dying a dramatic death.
>
> "BOOTP from dynamic client and no dynamic leases,"
>
> I think that answers the question. You have no dynamic range, by
> design. And there is a dynamic client requesting an address, so it is
> likely to be one that does not correspond to and of the 'hardware
> ethernet' lines.

I was wondering about that.  I even tried putting in the range that I
have, but that didn't fix the problem.  I'll check again when I get to
work, but I'm pretty sure it was one of the MACs listed in the file.
That was one of the first things I looked for.

>
> What is the mac address that is logged in syslog for that request? Is
> it supposed to be one of yours? Or is it every other host on the
> network?

As above, I'll check Monday morning when I get to work.

>
> If the latter then you may get around it by changing 'deny
> unknown-clients' to 'ignore unknown-clients'. The difference is that
> the latter does not log the fact that the client was denied.

Ok, I'll give that a try.

>
> If set to authoritative then this dhcp server will send a DHCPNAK to
> address requests it doesn't handle. If there's another DHCP server
> handling the rest then you don't want that. So in this case 'not
> authoritative' is correct.

Ah, thanks.  I was wondering about that.

>
> I assume that you are using dhcpd on your failing host. Can you copy
> that config file across to the new server? What platform (OS, version
> and dhcp version) are you using on the old and new dhcp servers?

Unfortunately, no.  The old system is an HP-UX system and the config
file for that is quite different, syntactically, from what dhcpd uses.


Thanks for the suggestions.

Andy


More information about the dhcp-users mailing list