MIME-Version: 1.0
In-Reply-To: <rt-3.8.6-35159-1403303073-8.36283-5-0@isc.org>
References: <RT-Ticket-36283@isc.org> <9232b43fab87d09a59793a268fa05c7b@www.isc.org> <rt-3.8.6-35159-1403303073-8.36283-5-0@isc.org>
Message-ID: <53A59391.5000702@ztk-rp.eu>
Content-Type: text/plain; charset=UTF-8; format=flowed
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.0
Subject: Re: [ISC-Bugs #36283] DHCP Server 4.2.2 - Abandoning IP address ....pinged before offer
Date: Sat, 21 Jun 2014 16:15:45 +0200
To: dhcp-bugs@isc.org
Content-Transfer-Encoding: 7bit
From: Rafał Pietrak <rafal@ztk-rp.eu>
RT-Message-ID: <rt-3.8.6-35138-1403360228-1340.36283-0-0@isc.org>
Content-Length: 1055

W dniu 21.06.2014 00:24, Shawn Routhier via RT pisze:
>   Were there any other log messages about the lease?
>
> If your client is using a valid lease it should remember
> that and do a renew or rebind which doesn't trigger a
> ping check. If your client isn't using a valid lease it
> shouldn't respond to the ping request.
>
If the logs are not yet recycled, I'll check that on monday. May be the 
actual sequence of msgs will tell you more.

But as I remember it, the notebook did run for a while afrer rewakening 
from sllep with and old IP, then had it changed because setver did 
"abondon" the old IP.

My impression is, that MAC of the notebook didn't change, so no matter 
what, the server should keep the same IP for the same MAC (if 
randomisation is not requested) e.g: "no matter what request was", and 
shold not ping at alll in such case... just to let live the "wrong 
clients", which don't know how to ask properly for renewal. The only 
concern is not to assign the same address twice, and this is ansured by 
comparing MACs. Right?

-R