Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Socket options to support IPv6 z/OS Communications Server: IPv6 Network and Application Design Guide SC27-3663-00 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A group of socket options is defined to support IPv6. These options are defined with a level of IPPROTO_IPV6. The individual options begin with IPV6_ or with MCAST_. Restriction: The options that begin with IPV6_ are allowed
only on AF_INET6 sockets.
In most cases, an IPV6_xxx option can be set on an AF_INET6 socket that is using IPv4-mapped IPv6 addresses but have no effect. For example, the IPV6_UNICAST_HOPS socket option is used to set a hop limit value in the IPv6 header. Because IPv4 packets are used with IPv4-mapped IPv6 addresses, the hop limit value is not used. Guideline: The Sockets Extended macro/call
APIs do not use level as an input to getsockopt() and setsockopt().
However, other IPv6-enabled APIs do use level as input. For detailed
information about setsockopt() and getsockopt() input and output,
see the API-specific information.
|
Copyright IBM Corporation 1990, 2014
|