Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How does my existing Windows Sockets for IPv4 code need to be modified to support IPv6?

0
Posted

How does my existing Windows Sockets for IPv4 code need to be modified to support IPv6?

0

A. The Windows Platform SDK includes a tool called Checkv4.exe. Checkv4.exe scans source code files to identify code that needs to be changed to support IPv6. Checkv4 displays the line number and a message recommending how the code should be changed. Here is an example of Checkv4.exe output: test.c(35) : gethostbyname : use getaddrinfo instead test.c(40) : gethostbyaddr : use getnameinfo instead test.c(48) : SOCKADDR_IN : use SOCKADDR_STORAGE instead, or use SOCKADDR_IN6 in addition for IPv6 support test.c(57) : AF_INET : use AF_INET6 in addition for IPv6 support test.c(89) : inet_addr : use WSAStringToAddress or getaddrinfo with AI_NUMERICHOST instead For more information, see Using the Checkv4.exe Utility. For detailed information about modifying your applications to work over both IPv4 and IPv6, see the IPv6 Guide for Windows Sockets Applications.

0

A. The Windows Platform SDK includes a tool called Checkv4.exe. Checkv4.exe scans source code files to identify code that needs to be changed to support IPv6. Checkv4 displays the line number and a message recommending how the code should be changed. Here is an example of Checkv4.exe output: test.c(35) : gethostbyname : use getaddrinfo instead test.c(40) : gethostbyaddr : use getnameinfo instead test.c(48) : SOCKADDR_IN : use SOCKADDR_STORAGE instead, or use SOCKADDR_IN6 in addition for IPv6 support test.c(57) : AF_INET : use AF_INET6 in addition for IPv6 support test.c(89) : inet_addr : use WSAStringToAddress or getaddrinfo with AI_NUMERICHOST instead Checkv4.exe is found in the \Bin folder in the location where the IPv6 Protocol files were extracted. Checkv4.exe is not copied to the %Systemroot%\System32 directory. And here’s a link to the entire faq: URL submitted by user. Hope this helps!

0

Asked in Computers & Accessories at 7:19 AM on November 03, 2008 Tags: existing, windows, sockets, code, modified, support

Related Questions

Thanksgiving questions

*Sadly, we had to bring back ads too. Hopefully more targeted.