The Winsock Error Reference at http://www.sockets.com/err_lst1.htm describes the 11004 error code (returned when STAF tried to call the setsockopt() function and logged in the error message) as follows: WSAEFAULT (10014) Bad address. Berkeley description: The system detected an invalid address in attempting to use an argument of a call. WinSock description: Same as Berkeley, and then some. Specifically, v1.1 WinSock spec notes that this error occurs if the length of the buffer is too small. For instance, if the length of a struct sockaddr is not equivalent to the sizeof(struct sockaddr). However, it also occurs when an application passes an invalid pointer value. Developer suggestions: Always check the return value from a memory allocation to be sure it succeeded. Always be sure to allocate enough space. WinSock functions: accept(), bind(), connect(), gethostname(), getpeername(), getsockname(), getsockopt(), recvfrom(), send(), sendto(), setsockopt() if buffer length is too small. Additional functions: Any functions that takes a pointer as an input parameter: inet_addr(), inet_ntoa(), ioctlsocket(), gethostbyaddr(), gethostbyname(), getservbyname(), getservbyport(), WSAAsyncGetHostByName() , WSAAsyncGetHostByAddr(), WSAAsyncGetProtoByName(), WSAAsyncGetProtoByNumber, WSAAsyncGetServByName(), WSAAsyncGetServByPort() , WSASetBlockingHook()User suggestions: see WSAHOST_NOT_FOUND for details.
So, maybe there's a problem within how STAF is calling the setsockopt() when IPv6 is configured. I'm not sure. If you configure the STAFTCP interface using PROTOCOL=IPv6 instead of PROTOCOL=IPv4_IPv6, do you get the same error? -------------------------------------------------------------- Sharon Lucas IBM Austin, luc...@us.ibm.com (512) 286-7313 or Tieline 363-7313 From: Yike Zhang <ykzh...@vmware.com> To: <staf-users@lists.sourceforge.net>, Date: 03/27/2014 04:26 AM Subject: [staf-users] STAF IPv6 address ping error on Win2003 server Hi all, I encounter an issue during my usage of STAF and searched everywhere (wiki, web, forum) but could not find useful clues. So would you help to give me some hints about how to fix that? The environment I used: OS: Win2003 Server 32 bits STAF Version: 3.4.16 My OS is configured with IPv6 stack and I installed on it STAF with IPv4_IPv6 option. I checked with staf command for the interfaces (staf local misc list interfaces) and it seems that I do have v6 interface for staf. I could still staf ping v4 address without issues, but when I tried to staf ping v6 address, I came across an error Staf fe90::92b1:1cff:fe3b:eacf ping ping Error submitting request, RC:16 Additional info -------------------- STAFConnectionProviderConnect: Error Setting SO_KEEPALIVE option:setsockopt() RC=10014:22, Endpoint:ssl://fe90::92b1:1cff:fe3b:eacf I tried to put SO_KEEPALIVE related parameters in the registry for IPv6 under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP6\Parameters but no help. Could you help? Thanks Yike ------------------------------------------------------------------------------ _______________________________________________ staf-users mailing list staf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/staf-users
------------------------------------------------------------------------------
_______________________________________________ staf-users mailing list staf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/staf-users
