Windows Sockets Support for IPv6 (Windows CE 5.0)
For Winsock IPv6 application development, the following tools are required:
- Microsoft® Windows SDK (October 2001 or later)
- Platform Builder OR eMbedded Visual C++ 4.0
- A device running Windows CE .NET 4.1 or later that includes IPv6 support
Changes to existing Windows Sockets functions for IPv6 are documented in RFC 2553. The IPv6 protocol for Windows CE supports RFC 2553 except for the following deviations:
- The header files listed in the RFC do not apply to Windows CE. The Windows CE header files are Winsock2.h and Ws2tcpip.h.
- The Windows CE socket structure does not include the sa_len member. Therefore, section 3.3 of RFC 2553 applies, but section 3.4 does not.
- IPv4-mapped addresses, as described in section 3.7 of RFC 2553, are not supported.
The following interface identification functions (described in section 4 of RFC 2553) are not supported:
unsigned int if_nametoindex(const char *ifname);char *if_indextoname(unsigned int ifindex, char *ifname);struct if_nameindex *if_nameindex(void);void if_freenameindex(struct if_nameindex *ptr);- Sections 6.1 through 6.3 and 6.6 are not supported because they are in the process of being made obsolete by the Internet Engineering Task Force (IETF).
See Also
Multiple Transport Protocols | Core Protocols of IPv6 | How to Convert an Application from IPv4 to IPv4/IPv6
Send Feedback on this topic to the authors