Any plan to fix the socket port binding limitation? I have a few cases where the fixed port would make the integration mush easier. Thanks.
Calls to tcp.bind
or udp.setsockname
may only specify port 0 to be assigned a port randomly, unless you are binding to a multicast IP address and have already set the reuseaddr
socket option to true
. This is to prevent unexpected collisions between drivers trying to bind to the same port. We’re looking into ways to allow binding to stable port numbers in a way that prevents conflicts, but don’t have solid plans yet. If you have a hard need this, let us know.