You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UDP transport is allocated twice: once for IPv6, and if INET_CONFIG_ENABLE_IPV4 enabled (default for various platforms including linux) then also for IPv4, both on the server as well as controller/client side. However, the TCP transport seems to be only allocated with an endpoint and with listen parameters only for IPv6, even though the underlying endpoint supports IPv4 with the same compiler flag.
Other than probably expanding some unit tests, I believe the fix is the following which I also validated between a controller and server app:
@pidarped I'd also like to confirm if this was an intentional choice for TCP even if it is inconsistent with UDP, so we can make appropriate assumptions on the controller side for 1.4 devices.
Reproduction steps
The UDP transport is allocated twice: once for IPv6, and if
INET_CONFIG_ENABLE_IPV4
enabled (default for various platforms including linux) then also for IPv4, both on the server as well as controller/client side. However, the TCP transport seems to be only allocated with an endpoint and with listen parameters only for IPv6, even though the underlying endpoint supports IPv4 with the same compiler flag.Other than probably expanding some unit tests, I believe the fix is the following which I also validated between a controller and server app:
Bug prevalence
Consistent
GitHub hash of the SDK that was being used
3f62505
Platform
raspi, other, core
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: