netif: add IPV4_ADDR_VALID ext status callback reason

This ext-callback reason is always issued when an IPv4 config
has been set, even if it has not changed (e.g. DHCP reboot)

See bug #55121
This commit is contained in:
Simon Goldschmidt
2020-01-12 20:30:22 +01:00
parent bb31fbd737
commit 8a8058a436
2 changed files with 8 additions and 0 deletions

View File

@@ -599,6 +599,8 @@ typedef u16_t netif_nsc_reason_t;
#define LWIP_NSC_IPV6_SET 0x0100
/** IPv6 address state has changed */
#define LWIP_NSC_IPV6_ADDR_STATE_CHANGED 0x0200
/** IPv4 settings: valid address set, application may start to communicate */
#define LWIP_NSC_IPV4_ADDR_VALID 0x0400
/** @ingroup netif
* Argument supplied to netif_ext_callback_fn.