https://community.hpe.com/t5/operating-system-openvms/openvms-8-3-tcpip-v5-6-9-the-getaddrinfo-socket-api-function-not/m-p/4751783#M60330 I am trying to update an existing socket-based C++ application to be address family independent for IPv6 support using getaddrinfo. However, if I try to lookup a numeric IPv6 address containing a scope reference (fe80::217:8ff:fe7c:6bc0%IE0) on a multi-homed machine it does not populate the sin6_scope_id member of the sockaddr_in6 structure returned in addrinfo when I use the address family hint AF_UNSPEC, but it does if I use AF_INET6. <BR /><BR />A Linux implementation always fills in the sin6_scope_id for AF_INET6 responses regardless of whether I specified AF_UNSPEC or AF_INET6.<BR /><BR />Anyone know if this is something that has been addressed in an ECO? I didn't find anything that talked about scope ids in IPv6 addresses. Fri, 11 Feb 2011 17:12:12 GMT Nigel Meachen 2011-02-11T17:12:12Z https://community.hpe.com/t5/operating-system-openvms/openvms-8-3-tcpip-v5-6-9-the-getaddrinfo-socket-api-function-not/m-p/4751783#M60330 I am trying to update an existing socket-based C++ application to be address family independent for IPv6 support using getaddrinfo. However, if I try to lookup a numeric IPv6 address containing a scope reference (fe80::217:8ff:fe7c:6bc0%IE0) on a multi-homed machine it does not populate the sin6_scope_id member of the sockaddr_in6 structure returned in addrinfo when I use the address family hint AF_UNSPEC, but it does if I use AF_INET6. <BR /><BR />A Linux implementation always fills in the sin6_scope_id for AF_INET6 responses regardless of whether I specified AF_UNSPEC or AF_INET6.<BR /><BR />Anyone know if this is something that has been addressed in an ECO? I didn't find anything that talked about scope ids in IPv6 addresses. Fri, 11 Feb 2011 17:12:12 GMT https://community.hpe.com/t5/operating-system-openvms/openvms-8-3-tcpip-v5-6-9-the-getaddrinfo-socket-api-function-not/m-p/4751783#M60330 Nigel Meachen 2011-02-11T17:12:12Z https://community.hpe.com/t5/operating-system-openvms/openvms-8-3-tcpip-v5-6-9-the-getaddrinfo-socket-api-function-not/m-p/4751784#M60331 Nigel,<BR /><BR /> Sounds like this issue is amenable to a very simple reproducer program? I'd build one, show &amp; document the differences you're seeing between operating systems, then log a case with your local customer support centre. Sun, 13 Feb 2011 21:05:54 GMT https://community.hpe.com/t5/operating-system-openvms/openvms-8-3-tcpip-v5-6-9-the-getaddrinfo-socket-api-function-not/m-p/4751784#M60331 John Gillings 2011-02-13T21:05:54Z