RE: IPV4LL and EXPIRE
David Hauck
Fri Oct 24 15:08:44 2014
On Friday, October 24, 2014 8:00 AM, Roy Marples wrote:
> On 24/10/2014 15:38, David Hauck wrote:
>>> The below example this is a valid transition where the DHCP server
>>> went down and didn't get back up until the DHCP lease had already
>>> expired.
>>>
>>> BOUND
>>> RENEW
>>> REBIND
>>
>> Shouldn't there be an EXPIRED here?
>>
>>> IPv4LL
>>> BOUND
>
> Uh, yes :)
>
>>> Does this help explain it?
>>
>> I think so, but: I guess there is no IPV4LL (specific) state
>> transition that
> indicates the IPV4LL state is no longer active? That is, the
> IPV4LL->BOUND transition *implies* this but a transition to the BOUND
> state can now occur from any number of prior states (not exactly sure
> of the full set of prior states but they at least include REBIND,
> IPV4LL, CARRIER,...). Perhaps any state transition to (!IPV4LL &&
> !EXPIRED) indicates IPV4LL state machine is no longer active?
>
> Correct.
> If the last state run is IPv4LL then it's an IPv4LL address, otherwise
> there is no state (expired, no carrier, etc) or a DHCP (or static, fallback, etc) address.
OK, thx.
> Roy
Archive administrator: postmaster@marples.name