known client ending up in unknown pool

[James Clark Calloway]

We had another one that exhibited the same behavior
and fixed itself ...

REQUEST (good ip) -- several lease unavailable messages

then

DISCOVER
OFFER (unknown pool) -- even though the guy was known
Several ACKS of that addresss

then later

REQUEST for the bad address
NAKS to the bad address (lease unavailable message)
DISCOVER
OFFER -- good address

Now its ACKing the good address.



On Thu, 9 Nov 2006, James Clark Calloway wrote:

>
> Shared and identified as such.
>
> In this case the fixed address was valid
> for the one it was physically connected to ...
> one of these was a workstation that had not
> moved in quite some time.
>
> Thanks in advance.
>
>
>
> On Thu, 9 Nov 2006, Simon Hobson wrote:
>
>> James Clark Calloway wrote:
>> 
>> <snip>
>>> host ahostdef {
>>>       hardware ethernet mac;
>>>       fixed-address (good ip);
>>>       option host-name   "host";
>>>       option domain-name "domain";
>>> }
>> 
>> You don't say anything about the network topology. Is it a shared
>> network ? If so, is it correctly identified as such ?
>> 
>> When a client gets a 'wrong' address, is it's fixed address in the
>> host statement valid for the subnet it's physically connected to ?
>> 
>> 
>> 
>