Abandoning ip address issue
sraja97 at gmail.com
Sat Apr 5 15:36:47 UTC 2014
Thanks for the responses. This was caused due to a omapi client (foreman
in this case) which was wrongly configured to allocate addresses from the
pool. Foreman allocates as fixed addresses and so obviously this
configuration caused the problem.
On Sat, Apr 5, 2014 at 6:41 AM, Peter Capriccio <peter.capriccio at hp.com>wrote:
> On 4/5/2014 Steven Carr wrote:
>> Date: Sat, 5 Apr 2014 02:18:47 +0100
>> From: Steven Carr<sjcarr at gmail.com>
>> To: Users of ISC DHCP<dhcp-users at lists.isc.org>
>> Subject: Re: Abandoning ip address issue
>> <CALMep04N9255Hgv461J8URFROmr5ms+f729yvFr8QsCWt-7=1A at mail.
>> Content-Type: text/plain; charset=UTF-8
>> On 5 April 2014 01:48, Suresh Rajagopalan<sraja97 at gmail.com> wrote:
>>> > Apr 4 13:59:04 gateway2 dhcpd: Abandoning IP address 192.168.109.235
>>> > pinged before offer
>> The IP address is in use. DHCPd wont lease out an IP that responds to
>> a ping. You have manually configured clients in a DHCP range. Fix your
> A manually configured client may not be the problem, but seemingly more
> like a problem with the DHCP client (or configuration for the latter) -- in
> a recent reply I had mentioned that I see the same symptoms from certain
> clients -- we have some embedded systems on our network that use the udhcp
> 1.13.3 client and they consistently hold on to their DHCP-issued IP address
> and bring said address up on their interface following a reboot, so when
> they issue their discover, the ping-check comes back positive and their
> lease gets abandoned -- the discover cycle repeats until the client
> eventually removes the IP address from its interface and then a "normal"
> handshake completes. Just my two pesos...
> Pete C.
> dhcp-users mailing list
> dhcp-users at lists.isc.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dhcp-users