After going through some related posts, i understand that its better to use
netifapi_netif_common(n, NULL, dhcp_start) instead of dhcp_start( ) as its
protects the lwip core from concurrent access.
Hope that enabling LWIP_TCPIP_CORE_LOCKING feature is fine -
As i saw the lines. (EXPERIMENTAL!
Am 7. November 2019 08:59:54 MEZ schrieb vinu :
>Hi Simon,
>
>Is it safe to call dhcp_network_changed() from application thread ? I
>tried
>it ans seems to be working properly.
No, it's not safe. Don't do that.
> Also, should i call
>netif_set_down()
>and netif_set_addr() before dhcp_network_ch
Hi Simon,
Is it safe to call dhcp_network_changed() from application thread ? I tried
it ans seems to be working properly. Also, should i call netif_set_down()
and netif_set_addr() before dhcp_network_changed() ?
regards,
Vinu
--
Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html
___
Am 06.11.2019 um 15:16 schrieb vinu:
Hi all,
I have come across an issue related to DHCP and link status.
The device does not restart the dhcp negotiation whenever the link goes down
and up automatically. Note that I have an interrupt callback for PHY link
up/down.
How should the dhcp be handl
Hi all,
I have come across an issue related to DHCP and link status.
The device does not restart the dhcp negotiation whenever the link goes down
and up automatically. Note that I have an interrupt callback for PHY link
up/down.
How should the dhcp be handled when the link up/down event occurs
