|IPV6CTL_FORWARDING||(ip6.forwarding) Boolean: enable/disable forwarding of IPv6 packets. Also, identify if the node is acting as a router. Defaults to off.|
|IPV6CTL_SENDREDIRECTS||(ip6.redirect) Boolean: enable/disable sending of ICMPv6 redirects in response to unforwardable IPv6 packets. This option is ignored unless the node is routing IPv6 packets, and should normally be enabled on all systems. Defaults to on.|
|IPV6CTL_DEFHLIM||(ip6.hlim) Integer: default hop limit value to use for outgoing IPv6 packets. This value applies to all the transport protocols on top of IPv6. There are APIs to override the value.|
|(ip6.maxfragpackets) Integer: default maximum number of fragmented packets the node will accept. 0 means that the node will not accept any fragmented packets. -1 means that the node will accept as many fragmented packets as it receives. The flag is provided basically for avoiding possible DoS attacks.|
|IPV6CTL_ACCEPT_RTADV||(ip6.accept_rtadv) Boolean: the default value of a per-interface flag to enable/disable receiving of ICMPv6 router advertisement packets, and autoconfiguration of address prefixes and default routers. The node must be a host (not a router) for the option to be meaningful. Defaults to off.|
|(ip6.auto_linklocal) Boolean: the default value of a per-interface flag to enable/disable performing automatic link-local address configuration. Defaults to on.|
|IPV6CTL_KEEPFAITH||(ip6.keepfaith) Boolean: enable/disable "FAITH" TCP relay IPv6-to-IPv4 translator code in the kernel. Refer faith(4) and faithd(8) for detail. Defaults to off.|
|IPV6CTL_LOG_INTERVAL||(ip6.log_interval) Integer: default interval between IPv6 packet forwarding engine log output (in seconds).|
|IPV6CTL_HDRNESTLIMIT||(ip6.hdrnestlimit) Integer: default number of the maximum IPv6 extension headers permitted on incoming IPv6 packets. If set to 0, the node will accept as many extension headers as possible.|
|IPV6CTL_DAD_COUNT||(ip6.dad_count) Integer: default number of IPv6 DAD (duplicated address detection) probe packets. The packets will be generated when IPv6 interface addresses are configured.|
|(ip6.auto_flowlabel) Boolean: enable/disable automatic filling of IPv6 flowlabel field, for outstanding connected transport protocol packets. The field might be used by intermediate routers to identify packet flows. Defaults to on.|
|IPV6CTL_DEFMCASTHLIM||(ip6.defmcasthlim) Integer: default hop limit value for an IPv6 multicast packet sourced by the node. This value applies to all the transport protocols on top of IPv6. There are APIs to override the value as documented in ip6(4).|
|IPV6CTL_GIF_HLIM||(ip6.gifhlim) Integer: default maximum hop limit value for an IPv6 packet generated by gif(4) tunnel interface.|
|IPV6CTL_KAME_VERSION||(ip6.kame_version) String: identifies the version of KAME IPv6 stack implemented in the kernel.|
|(ip6.use_deprecated) Boolean: enable/disable use of deprecated address, specified in RFC2462 5.5.4. Defaults to on.|
|IPV6CTL_RR_PRUNE||(ip6.rr_prune) Integer: default interval between IPv6 router renumbering prefix babysitting, in seconds.|
|IPV6CTL_V6ONLY||(ip6.v6only) Boolean: enable/disable the prohibited use of IPv4 mapped address on AF_INET6 sockets. Defaults to on.|
|IPV6CTL_RTEXPIRE||(ip6.rtexpire) Integer: lifetime in seconds of protocol-cloned IP routes after the last reference drops (default one hour).|
|IPV6CTL_RTMINEXPIRE||(ip6.rtminexpire) Integer: minimum value of ip.rtexpire (default ten seconds).|
|IPV6CTL_RTMAXCACHE||(ip6.rtmaxcache) Integer: trigger level of cached, unreferenced, protocol-cloned routes which initiates dynamic adaptation (default 128).|
.Fx does not route IPv4 traffic to AF_INET6 sockets. The default behavior intentionally violates RFC2553 for security reasons. Listen to two sockets if you want to accept both IPv4 and IPv6 traffic. IPv4 traffic may be routed with certain per-socket/per-node configuration, however, it is not recommended to do so. Consult ip6(4) for details.
The behavior of AF_INET6 TCP/UDP socket is documented in RFC2553. Basically, it says this:
- A specific bind on an AF_INET6 socket ( bind 2 with an address specified) should accept IPv6 traffic to that address only.
- If you perform a wildcard bind on an AF_INET6 socket ( bind 2 to IPv6 address ::), and there is no wildcard bind AF_INET socket on that TCP/UDP port, IPv6 traffic as well as IPv4 traffic should be routed to that AF_INET6 socket. IPv4 traffic should be seen as if it came from an IPv6 address like ::ffff:10.1.1.1. This is called an IPv4 mapped address.
- If there are both a wildcard bind AF_INET socket and a wildcard bind AF_INET6 socket on one TCP/UDP port, they should behave separately. IPv4 traffic should be routed to the AF_INET socket and IPv6 should be routed to the AF_INET6 socket.
However, RFC2553 does not define the ordering constraint between calls to bind(2), nor how IPv4 TCP/UDP port numbers and IPv6 TCP/UDP port numbers relate to each other (should they be integrated or separated). Implemented behavior is very different from kernel to kernel. Therefore, it is unwise to rely too much upon the behavior of AF_INET6 wildcard bind sockets. It is recommended to listen to two sockets, one for AF_INET and another for AF_INET6, when you would like to accept both IPv4 and IPv6 traffic.
It should also be noted that malicious parties can take advantage of the complexity presented above, and are able to bypass access control, if the target node routes IPv4 traffic to AF_INET6 socket. Users are advised to take care handling connections from IPv4 mapped address to AF_INET6 sockets.
.Rs An Extension of Format for IPv6 Scoped Addresses
The inet6 protocol interfaces are defined in RFC2553 and RFC2292. The implementation described herein appeared in the WIDE/KAME project.
The IPv6 support is subject to change as the Internet protocols develop. Users should not depend on details of the current implementation, but rather the services exported.
Users are suggested to implement "version independent" code as much as possible, as you will need to support both inet(4) and inet6.