Mirroring some functionality from ISC's now End Of Life dhclient, it will trigger exit hooks in the following circumstances:
- DISC_NO_OFFER - DISCOVER sent no OFFER seen - re-transmitting DISCOVER
- SOLICIT_NO_ADVERT - DHCPv6 equivalent
- REQ_NO_RESP - REQUEST sent no RESPONSE seen - falling back to DISCOVER
- REQ6_NO_REPLY - DHCPv6 equivalent after REQ_MAX_RC exceeded
- RENEW_NO_RESP - RENEW sent no RESPONSE seen - T2 expired, attempting REBIND
- RENEW6_NO_RESP - RENEW6 sent no RESPONSE - same but for DHCPv6
- RS_TIMEOUT_NO_RA - Router Solicitations have been sent without seeing a Router Advertisement in reply. Only seen if noipv6rs is not set.
Does not change dhcpcd behaviour, but will allow it to notify external monitors via exit hook that things are not going well. For example, in the *_NO_RESP, lease has hit T2 timer, and if it does not successfully rebind, lease is in danger of expiring. could be used to fire off a "help help I'm going to go offline" message before the lease actually expires.
ENHANCEMENT for 10.5.2 - but related to behaviour discussed in #558
Mirroring some functionality from ISC's now End Of Life dhclient, it will trigger exit hooks in the following circumstances:
Does not change dhcpcd behaviour, but will allow it to notify external monitors via exit hook that things are not going well. For example, in the *_NO_RESP, lease has hit T2 timer, and if it does not successfully rebind, lease is in danger of expiring. could be used to fire off a "help help I'm going to go offline" message before the lease actually expires.
ENHANCEMENT for 10.5.2 - but related to behaviour discussed in #558