search

Microchip-MPLAB-Harmony / net

Harmony 3 Network library
https://onlinedocs.microchip.com/v2/keyword-lookup?keyword=MH3_net&redirect=true
29 stars 9 forks source link

MCC / Harmony default setting for TCPIP_STACK_INTERFACE_CHANGE_SIGNALING is false #48

Closed nwright-mcc closed 1 week ago

nwright-mcc commented 4 weeks ago

The Manager Module help at https://microchip-mplab-harmony.github.io/net/GUID-B37C4F4C-DC2D-48D9-9909-AACBA987B57A.html states that the default setting for this setting is true. However, MCC v5.5.1 initializes this to false when using the TCP/IP Configuration plugin.

This resulted in incorrect behavior on a network where the DHCP client timed out and used the default IP address and the TCP socket was opened with this address, but the DHCP server subsequently assigned an address to the device. The TCP socket did not update to the new address.

adrian-aur commented 4 weeks ago

Can you please describe what setting is exactly the problem. It may be just some documentation error or the setting has been changed from its default value. But to check it I need to know which one you're referring to.

nwright-mcc commented 4 weeks ago

In MCC, it is set under TCPIP CORE - Advanced Settings - Enable Interface Address Change Signaling.

adrian-aur commented 4 weeks ago

Yes, it's a documentation issue. The default value is false. I'll make the request to change it. However, it's always a good idea to verify the settings of your project, especially the 'advanced' ones, if your app is relying on them. Especially when starting from another app and then add functionality to it.

Please note that if this feature is enabled the client sockets will be killed and the server sockets will be disconnected. For client sockets the app intervention is necessary anyway.

adrian-aur commented 1 week ago

An internal request has been made to update the documentation for this.