Permalink
Browse files

backout wrong commit

  • Loading branch information...
1 parent af1c951 commit a41809f0d8659e3977e1e099ec0a14284831fba8 itojun committed Feb 26, 2001
Showing with 13 additions and 11 deletions.
  1. +13 −11 kame/kame/man/man4/ip6.4
View
24 kame/kame/man/man4/ip6.4
@@ -1,4 +1,4 @@
-.\" $KAME: ip6.4,v 1.10.2.1 2001/02/26 09:30:36 itojun Exp $
+.\" $KAME: ip6.4,v 1.10.2.2 2001/02/26 09:32:21 itojun Exp $
.\"
.\" Copyright (C) 1999 WIDE Project.
.\" All rights reserved.
@@ -92,7 +92,7 @@ There are several
.Tn IPv6-level
.Xr setsockopt 2 / Ns Xr getsockopt 2
options.
-They are be separated into the basic IPv6 sockets API
+They are separated into the basic IPv6 sockets API
.Pq defined in RFC2553 ,
and the advanced API
.Pq defined in RFC2292 .
@@ -204,7 +204,7 @@ is the following structure:
.Bd -literal -offset indent
struct ipv6_mreq {
struct in6_addr ipv6mr_multiaddr;
- u_int ipv6mr_interface;
+ unsigned int ipv6mr_interface;
};
.Ed
.Pp
@@ -239,14 +239,14 @@ int range = IPV6_PORTRANGE_LOW; /* see <netinet/in.h> */
setsockopt(s, IPPROTO_IPV6, IPV6_PORTRANGE, &range, sizeof(range));
.Ed
.Pp
-.Dv IPV6_V6ONLY
+.Dv IPV6_BINDV6ONLY
controls behavior of
.Dv AF_INET6
wildcard listening socket.
The following example sets the option to 1:
.Bd -literal -offset indent
int on = 1;
-setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY, &on, sizeof(on));
+setsockopt(s, IPPROTO_IPV6, IPV6_BINDV6ONLY, &on, sizeof(on));
.Ed
.Pp
If set to 1,
@@ -267,7 +267,7 @@ you will end up accepting IPv4 traffic by
listening socket on the same port.
The default value for this flag is copied at socket instantiation time,
from
-.Li net.inet6.ip6.v6only
+.Li net.inet6.ip6.bindv6only
.Xr sysctl 3
variable.
The option affects
@@ -683,12 +683,14 @@ The ancillary data items were improperly formed, or option name was unknown.
.Sh STANDARDS
Most of the socket options are defined in
RFC2292 and/or RFC2553.
-.Dv IPV6_V6ONLY
-socket option is defined in draft-ietf-ipngwg-rfc2553bis-03.
-.Dv IPV6_PORTRANGE
-socket option
-and conflict resolution rule
+.Pp
+.Dv IPV6_PORTRANGE ,
+.Dv IPV6_BINDV6ONLY
+and
+conflict resolution rule
are not defined in the RFCs and should be considered implementation dependent.
+.Dv IPV6_BINDV6ONLY
+is supplied on KAME/NetBSD only.
.\"
.Sh HISTORY
The implementation is based on KAME stack

0 comments on commit a41809f

Please sign in to comment.