Quantcast
Channel: Forum - Recent Threads
Viewing all articles
Browse latest Browse all 5781

Error while getting socket name

$
0
0

Hi,

Using NetX in SSP 1.4.0 I face a curious issue.

I create a TCP client socket and attempt to connect to a remote server socket. By doing so, during the call to connect, the stack calls nx_tcp_client_socket_bind to retrieve a local port and assign it to the client socket. In the end, I get a client TCP socket with a nx_bsd_socket_local_port set, the NX_NSD_SOCKET_BOUND flag set, but a nx_bsd_socket_local_bind_interface set to 0.

Later on, I call getsockname on this socket. Since the socket is supposed to be bound, the nx_bsd_socket_local_bind_interface value is checked, but since it's 0 a EINVAL is returned.

Shouldn't nx_bsd_socket_local_bind_interface be set during the connect or nx_tcp_client_socket_bind?

 

Regards,

Bastien


Viewing all articles
Browse latest Browse all 5781

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>