| blob | c196466c812c419a4789866a08d7fd18f32bb398 |
1 '\" te
2 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH IP6 7P "Dec 2, 2008"
7 .SH NAME
8 ip6 \- Internet Protocol Version 6
9 .SH SYNOPSIS
10 .LP
11 .nf
12 #include <sys/socket.h>
13 #include <netinet/in.h>
14 #include <netinet/ip6.h>
15 .fi
17 .LP
18 .nf
19 s = socket(AF_INET6, SOCK_RAW, proto);
20 .fi
22 .LP
23 .nf
24 t = t_open ("/dev/rawip6", O_RDWR);
25 .fi
27 .SH DESCRIPTION
28 .sp
29 .LP
30 The \fBIPv6\fR protocol is the next generation of the internetwork datagram
31 delivery protocol of the Internet protocol family. Programs may use \fBIPv6\fR
32 through higher-level protocols such as the Transmission Control Protocol
33 (\fBTCP\fR) or the User Datagram Protocol (\fBUDP\fR), or may interface
34 directly to \fBIPv6\fR. See \fBtcp\fR(7P) and \fBudp\fR(7P). Direct access may
35 be by means of the socket interface, using a "raw socket," or by means of the
36 Transport Level Interface (\fBTLI\fR). The protocol options and \fBIPv6\fR
37 extension headers defined in the \fBIPv6\fR specification may be set in
38 outgoing datagrams.
39 .SH APPLICATION PROGRAMMING INTERFACE
40 .sp
41 .LP
42 The \fBSTREAMS\fR driver \fB/dev/rawip6\fR is the \fBTLI\fR transport provider
43 that provides raw access to \fBIPv6\fR.
44 .sp
45 .LP
46 Raw \fBIPv6\fR sockets are connectionless and are normally used with the
47 \fBsendto()\fR and \fBrecvfrom()\fR calls (see \fBsend\fR(3SOCKET) and
48 \fBrecv\fR(3SOCKET)), although the \fBconnect\fR(3SOCKET) call may also be used
49 to fix the destination for future datagrams. In this case, the \fBread\fR(2) or
50 \fBrecv\fR(3SOCKET) and \fBwrite\fR(2) or \fBsend\fR(3SOCKET) calls may be
51 used. Ancillary data may also be sent or received over raw \fBIPv6\fR sockets
52 using the \fBsendmsg\fR(3SOCKET) and \fBrecvmsg\fR(3SOCKET) system calls.
53 .sp
54 .LP
55 Unlike raw \fBIP\fR, \fBIPv6\fR applications do not include a complete
56 \fBIPv6\fR header when sending; there is no \fBIPv6\fR analog to the \fBIP\fR
57 \fBIP_HDRINCL\fR socket option. \fBIPv6\fR header values may be specified or
58 received as ancillary data to a \fBsendmsg\fR(3SOCKET) or
59 \fBrecvmsg\fR(3SOCKET) system call, or may be specified as "sticky" options on
60 a per-socket basis by using the \fBsetsockopt\fR(3SOCKET) system call. Such
61 sticky options are applied to all outbound packets unless overridden by
62 ancillary data. If any ancillary data is specified in a \fBsendmsg\fR(3SOCKET)
63 call, all sticky options not explicitly overridden revert to default values for
64 that datagram only; the sticky options persist as set for subsequent datagrams.
65 .sp
66 .LP
67 Since \fBsendmsg\fR(3SOCKET) is not supported for \fBSOCK_STREAM\fR upper level
68 protocols such as \fBTCP\fR, ancillary data is unsupported for \fBTCP\fR.
69 Sticky options, however, are supported.
70 .sp
71 .LP
72 Since \fBsendmsg\fR(3SOCKET) is supported for \fBSOCK_DGRAM\fR upper level
73 protocols, both ancillary data and sticky options are supported for \fBUDP\fR,
74 \fBICMP6\fR, and raw \fBIPv6\fR sockets.
75 .sp
76 .LP
77 The socket options supported at the \fBIPv6\fR level are:
78 .sp
79 .ne 2
80 .na
81 \fB\fBIPV6_BOUND_IF\fR\fR
82 .ad
83 .RS 24n
84 Limit reception and transmission of packets to this interface. Takes an integer
85 as an argument; the integer is the selected interace index.
86 .RE
88 .sp
89 .ne 2
90 .na
91 \fB\fBIPV6_UNSPEC_SRC\fR\fR
92 .ad
93 .RS 24n
94 Boolean. Allow/disallow sending with a zero source address.
95 .RE
97 .sp
98 .ne 2
99 .na
100 \fB\fBIPV6_UNICAST_HOPS\fR\fR
101 .ad
102 .RS 24n
103 Default hop limit for unicast datagrams. This option takes an integer as an
104 argument. Its value becomes the new default value for \fBip6_hops\fR that
105 \fBIPv6\fR will use on outgoing unicast datagrams sent from that socket. The
106 initial default is \fB60\fR.
107 .RE
109 .sp
110 .ne 2
111 .na
112 \fB\fBIPV6_CHECKSUM\fR\fR
113 .ad
114 .RS 24n
115 Specify the integer offset in bytes into the user data of the checksum
116 location. Does not apply to the \fBICMP6\fR protocol. Note: checksums are
117 required for all \fBIPv6\fR datagrams; this is different from \fBIP\fR, in
118 which datagram checksums were optional. \fBIPv6\fR will compute the \fBULP\fR
119 checksum if the value in the checksum field is zero.
120 .RE
122 .sp
123 .ne 2
124 .na
125 \fB\fBIPV6_SEC_OPT\fR\fR
126 .ad
127 .RS 24n
128 Enable or obtain IPsec security settings for this socket. For more details on
129 the protection services of IPsec, see \fBipsec\fR(7P).
130 .RE
132 .sp
133 .ne 2
134 .na
135 \fB\fBIPV6_DONTFRAG\fR\fR
136 .ad
137 .RS 24n
138 Boolean. Control fragmentation.
139 .RE
141 .sp
142 .ne 2
143 .na
144 \fB\fBIPV6_USE_MIN_MTU\fR\fR
145 .ad
146 .RS 24n
147 Controls whether path MTU discovery is used. If set to 1, path MTU discovery is
148 never used and IPv6 packets are sent with the IPv6 minimum MTU. If set to -1,
149 path MTU discovery is not used for multicast and multicast packets are sent
150 with the IPv6 minimum MTU. If set to 0, path MTU is always performed.
151 .RE
153 .sp
154 .ne 2
155 .na
156 \fB\fBIPV6_V6ONLY\fR\fR
157 .ad
158 .RS 24n
159 Boolean. If set, only V6 packets can be sent or received
160 .RE
162 .sp
163 .ne 2
164 .na
165 \fB\fBIPV6_SRC_PREFERENCES\fR\fR
166 .ad
167 .RS 24n
168 Enable or obtain Source Address Selection rule settings for this socket. For
169 more details on the Source Address Selection rules, see \fBinet6\fR(7P).
170 .RE
172 .sp
173 .LP
174 The following options are boolean switches controlling the reception of
175 ancillary data:
176 .sp
177 .ne 2
178 .na
179 \fB\fBIPV6_RECVPKTINFO\fR\fR
180 .ad
181 .RS 25n
182 Enable/disable receipt of the index of the interface the packet arrived on, and
183 of the inbound packet's destination address.
184 .RE
186 .sp
187 .ne 2
188 .na
189 \fB\fBIPV6_RECVHOPLIMIT\fR\fR
190 .ad
191 .RS 25n
192 Enable/disable receipt of the inbound packet's current hoplimit.
193 .RE
195 .sp
196 .ne 2
197 .na
198 \fB\fBIPV6_RECVHOPOPTS\fR\fR
199 .ad
200 .RS 25n
201 Enable/disable receipt of the inbound packet's \fBIPv6\fR hop-by-hop extension
202 header.
203 .RE
205 .sp
206 .ne 2
207 .na
208 \fB\fBIPV6_RECVDSTOPTS\fR\fR
209 .ad
210 .RS 25n
211 Enable/disable receipt of the inbound packet's \fBIPv6\fR destination options
212 extension header.
213 .RE
215 .sp
216 .ne 2
217 .na
218 \fB\fBIPV6_RECVRTHDR\fR\fR
219 .ad
220 .RS 25n
221 Enable/disable receipt of the inbound packet's \fBIPv6\fR routing header.
222 .RE
224 .sp
225 .ne 2
226 .na
227 \fB\fBIPV6_RECVRTHDRDSTOPTS\fR\fR
228 .ad
229 .RS 25n
230 Enable/disable receipt of the inbound packet's intermediate-hops options
231 extension header. This option is obsolete. IPV6_RECVDSTOPTS turns on receipt of
232 both destination option headers.
233 .RE
235 .sp
236 .ne 2
237 .na
238 \fB\fBIPV6_RECVTCLASS\fR\fR
239 .ad
240 .RS 25n
241 Enable/disable receipt of the traffic class of the inbound packet.
242 .RE
244 .sp
245 .ne 2
246 .na
247 \fB\fBIPV6_RECVPATHMTU\fR\fR
248 .ad
249 .RS 25n
250 Enable/disable receipt of the path mtu of the inbound packet.
251 .RE
253 .sp
254 .LP
255 The following options may be set as sticky options with
256 \fBsetsockopt\fR(3SOCKET) or as ancillary data to a \fBsendmsg\fR(3SOCKET)
257 system call:
258 .sp
259 .ne 2
260 .na
261 \fB\fBIPV6_PKTINFO\fR\fR
262 .ad
263 .RS 21n
264 Set the source address and/or interface out which the packet(s) will be sent.
265 Takes a \fBstruct\fR \fBin6_pktinfo\fR as the parameter.
266 .RE
268 .sp
269 .ne 2
270 .na
271 \fB\fBIPV6_HOPLIMIT\fR\fR
272 .ad
273 .RS 21n
274 Set the initial hoplimit for outbound datagrams. Takes an integer as the
275 parameter. Note: This option sets the hoplimit only for ancillary data or
276 sticky options and does not change the default hoplimit for the socket; see
277 \fBIPV6_UNICAST_HOPS\fR and \fBIPV6_MULTICAST_HOPS\fR to change the socket's
278 default hoplimit.
279 .RE
281 .sp
282 .ne 2
283 .na
284 \fB\fBIPV6_NEXTHOP\fR\fR
285 .ad
286 .RS 21n
287 Specify the \fBIPv6\fR address of the first hop, which must be a neighbor of
288 the sending host. Takes a \fBstruct\fR \fBsockaddr_in6\fR as the parameter.
289 When this option specifies the same address as the destination \fBIPv6\fR
290 address of the datagram, this is equivalent to the existing \fBSO_DONTROUTE\fR
291 option.
292 .RE
294 .sp
295 .ne 2
296 .na
297 \fB\fBIPV6_HOPOPTS\fR\fR
298 .ad
299 .RS 21n
300 Specify one or more hop-by-hop options. Variable length. Takes a complete
301 \fBIPv6\fR hop-by-hop options extension header as the parameter.
302 .RE
304 .sp
305 .ne 2
306 .na
307 \fB\fBIPV6_DSTOPTS\fR\fR
308 .ad
309 .RS 21n
310 Specify one or more destination options. Variable length. Takes a complete
311 \fBIPv6\fR destination options extension header as the parameter.
312 .RE
314 .sp
315 .ne 2
316 .na
317 \fB\fBIPV6_RTHDR\fR\fR
318 .ad
319 .RS 21n
320 Specify the \fBIPv6\fR routing header. Variable length. Takes a complete
321 \fBIPv6\fR routing header as the parameter. Currently, only type 0 routing
322 headers are supported.
323 .RE
325 .sp
326 .ne 2
327 .na
328 \fB\fBIPV6_RTHDRDSTOPTS\fR\fR
329 .ad
330 .RS 21n
331 Specify one or more destination options for all intermediate hops. May be
332 configured, but will not be applied unless an \fBIPv6\fR routing header is also
333 configured. Variable length. Takes a complete \fBIPv6\fR destination options
334 extension header as the parameter.
335 .RE
337 .sp
338 .ne 2
339 .na
340 \fB\fBIPV6_PATHMTU\fR\fR
341 .ad
342 .RS 21n
343 Get the path MTU associated with a connected socket. Takes a ip6_mtuinfo as the
344 parameter.
345 .RE
347 .sp
348 .ne 2
349 .na
350 \fB\fBIPV6_TCLASS\fR\fR
351 .ad
352 .RS 21n
353 Set the traffic class associated with outgoing packets. The parameter is an
354 integer. If the parameter is less then -1 or greater then 256, EINVAL is
355 returned. If the parameter is equal to -1, use the default. If the parameter is
356 between 0 and 255 inclusive, use that value.
357 .RE
359 .sp
360 .LP
361 The following options affect the socket's multicast behavior:
362 .sp
363 .ne 2
364 .na
365 \fB\fBIPV6_JOIN_GROUP\fR\fR
366 .ad
367 .RS 28n
368 Join a multicast group. Takes a \fBstruct\fR \fBipv6_mreq\fR as the parameter;
369 the structure contains a multicast address and an interface index.
370 .RE
372 .sp
373 .ne 2
374 .na
375 \fB\fBIPV6_LEAVE_GROUP\fR\fR
376 .ad
377 .RS 28n
378 Leave a multicast group. Takes a \fBstruct\fR \fBipv6_mreq\fR as the parameter;
379 the structure contains a multicast address and an interface index.
380 .RE
382 .sp
383 .ne 2
384 .na
385 \fB\fBMCAST_JOIN_GROUP\fR\fR
386 .ad
387 .RS 28n
388 Functionally equivalent to IPV6_JOIN_GROUP. Takes a \fBstruct\fR
389 \fBgroup_req\fR as the parameter. The structure contains a multicast address
390 and an interface index.
391 .RE
393 .sp
394 .ne 2
395 .na
396 \fB\fBMCAST_BLOCK_SOURCE\fR\fR
397 .ad
398 .RS 28n
399 Block multicast packets on a particular multicast group whose source address
400 matches the given source address. The specified group must be joined previously
401 using IPV6_JOIN_GROUP or MCAST_JOIN_GROUP. Takes a \fBstruct\fR
402 \fBgroup_source_req\fR as the parameter. The structure contains an interface
403 index, a multicast address, and a source address.
404 .RE
406 .sp
407 .ne 2
408 .na
409 \fB\fBMCAST_UNBLOCK_SOURCE\fR\fR
410 .ad
411 .RS 28n
412 Unblock multicast packets which were previously blocked using
413 MCAST_BLOCK_SOURCE. Takes a \fBstruct\fR \fBgroup_source_req\fR as the
414 parameter. The structure contains an interface index, a multicast address, and
415 a source address.
416 .RE
418 .sp
419 .ne 2
420 .na
421 \fB\fBMCAST_LEAVE_GROUP\fR\fR
422 .ad
423 .RS 28n
424 Functionally equivalent to IPV6_LEAVE_GROUP. Takes a \fBstruct\fR
425 \fBgroup_req\fR as the parameter. The structure contains a multicast address
426 and an interface index.
427 .RE
429 .sp
430 .ne 2
431 .na
432 \fB\fBMCAST_JOIN_SOURCE_GROUP\fR\fR
433 .ad
434 .RS 28n
435 Begin receiving packets for the given multicast group whose source address
436 matches the specified address. Takes a \fBstruct\fR \fBgroup_source_req\fR as
437 the parameter. The structure contains an interface index, a multicast address,
438 and a source address.
439 .RE
441 .sp
442 .ne 2
443 .na
444 \fB\fBMCAST_LEAVE_SOURCE_GROUP\fR\fR
445 .ad
446 .RS 28n
447 Stop receiving packets for the given multicast group whose source address
448 matches the specified address. Takes a \fBstruct\fR \fBgroup_source_req\fR as
449 the parameter. The structure contains an interface index, a multicast address,
450 and a source address.
451 .RE
453 .sp
454 .ne 2
455 .na
456 \fB\fBIPV6_MULTICAST_IF\fR\fR
457 .ad
458 .RS 28n
459 The outgoing interface for multicast packets. This option takes an integer as
460 an argument; the integer is the interface index of the selected interface.
461 .RE
463 .sp
464 .ne 2
465 .na
466 \fB\fBIPV6_MULTICAST_HOPS\fR\fR
467 .ad
468 .RS 28n
469 Default hop limit for multicast datagrams. This option takes an integer as an
470 argument. Its value becomes the new default value for \fBip6_hops\fR that
471 \fBIPv6\fR will use on outgoing multicast datagrams sent from that socket. The
472 initial default is \fB1\fR.
473 .RE
475 .sp
476 .ne 2
477 .na
478 \fB\fBIPV6_MULTICAST_LOOP\fR\fR
479 .ad
480 .RS 28n
481 Loopback for multicast datagrams. Normally multicast datagrams are delivered to
482 members on the sending host. Setting the unsigned character argument to 0 will
483 cause the opposite behavior.
484 .RE
486 .sp
487 .LP
488 The multicast socket options can be used with any datagram socket type in the
489 \fBIPv6\fR family.
490 .sp
491 .LP
492 At the socket level, the socket option \fBSO_DONTROUTE\fR may be applied. This
493 option forces datagrams being sent to bypass routing and forwarding by forcing
494 the \fBIPv6\fR hoplimit field to \fB1\fR, meaning that the packet will not be
495 forwarded by routers.
496 .sp
497 .LP
498 Raw \fBIPv6\fR datagrams can also be sent and received using the \fBTLI\fR
499 connectionless primitives.
500 .sp
501 .LP
502 Datagrams flow through the \fBIPv6\fR layer in two directions: from the network
503 \fIup\fR to user processes and from user processes \fIdown\fR to the network.
504 Using this orientation, \fBIPv6\fR is layered \fIabove\fR the network interface
505 drivers and \fIbelow\fR the transport protocols such as \fBUDP\fR and
506 \fBTCP\fR. The Internet Control Message Protocol (\fBICMPv6\fR) for the
507 Internet Protocol Version 6 (\fBIPv6\fR) is logically a part of \fBIPv6\fR. See
508 \fBicmp6\fR(7P).
509 .sp
510 .LP
511 Unlike \fBIP\fR, \fBIPv6\fR provides no checksum of the \fBIPv6\fR header. Also
512 unlike \fBIP\fR, upper level protocol checksums are required. \fBIPv6\fR will
513 compute the \fBULP\fR/data portion checksum if the checksum field contains a
514 zero (see \fBIPV6_CHECKSUM\fR option above).
515 .sp
516 .LP
517 \fBIPv6\fR extension headers in received datagrams are processed in the
518 \fBIPv6\fR layer according to the protocol specification. Currently recognized
519 \fBIPv6\fR extension headers include hop-by-hop options header, destination
520 options header, routing header (currently, only type 0 routing headers are
521 supported), and fragment header.
522 .sp
523 .LP
524 By default, the IPv6 layer will not forward IPv6 packets that are not addressed
525 to it. This behavior can be overridden by using \fBrouteadm\fR(1M) to enable
526 the ipv6-forwarding option. IPv6 forwarding is configured at boot time based on
527 the setting of \fBrouteadm\fR(1M)'s ipv6-forwarding option.
528 .sp
529 .LP
530 For backwards compatibility, IPv6 forwarding can be enabled or disabled using
531 \fBndd\fR(1M)'s ip_forwarding variable. It is set to 1 if IPv6 forwarding is
532 enabled, or 0 if it is disabled.
533 .sp
534 .LP
535 Additionally, finer-grained forwarding can be configured in IPv6. Each
536 interface can be configured to forward IPv6 packets by setting the IFF_ROUTER
537 interface flag. This flag can be set and cleared using \fBifconfig\fR(1M)'s
538 router and -router options. If an interface's IFF_ROUTER flag is set, packets
539 can be forwarded to or from the interface. If it is clear, packets will neither
540 be forwarded from this interface to others, nor forwarded to this interface.
541 Setting the ip6_forwarding variable sets all of the IPv6 interfaces' IFF_ROUTER
542 flags.
543 .sp
544 .LP
545 For backwards compatibility, each interface creates an
546 \fB<ifname>ip6_forwarding /dev/ip6\fR variable that can be modified using
547 \fBndd\fR(1M). An interface's \fB:ip6_forwarding ndd\fR variable is a boolean
548 variable that mirrors the status of its IFF_ROUTER interface flag. It is set to
549 1 if the flag is set, or 0 if it is clear. This interface specific
550 \fB<ifname>:ip6_forwarding ndd\fR variable is obsolete and may be removed in a
551 future release of Solaris. The \fBifconfig\fR(1M) router and -router interfaces
552 are preferred.
553 .sp
554 .LP
555 The \fBIPv6\fR layer will send an \fBICMP6\fR message back to the source host
556 in many cases when it receives a datagram that can not be handled. A
557 "\fBtime\fR \fBexceeded\fR" \fBICMP6\fR message will be sent if the
558 \fBip6_hops\fR field in the \fBIPv6\fR header drops to zero in the process of
559 forwarding a datagram. A "\fBdestination\fR \fBunreachable\fR" message will be
560 sent by a router or by the originating host if a datagram can not be sent on
561 because there is no route to the final destination; it will be sent by a router
562 when it encounters a firewall prohibition; it will be sent by a destination
563 node when the transport protocol (that is, \fBTCP\fR) has no listener. A
564 "\fBpacket\fR \fBtoo\fR \fBbig\fR" message will be sent by a router if the
565 packet is larger than the \fBMTU\fR of the outgoing link (this is used for Path
566 \fBMTU\fR Discovery). A "\fBparameter\fR \fBproblem\fR" message will be sent if
567 there is a problem with a field in the \fBIPv6\fR header or any of the
568 \fBIPv6\fR extension headers such that the packet cannot be fully processed.
569 .sp
570 .LP
571 The \fBIPv6\fR layer supports fragmentation and reassembly. Datagrams are
572 fragmented on output if the datagram is larger than the maximum transmission
573 unit (\fBMTU\fR) of the network interface. Fragments of received datagrams are
574 dropped from the reassembly queues if the complete datagram is not
575 reconstructed within a short time period.
576 .sp
577 .LP
578 Errors in sending discovered at the network interface driver layer are passed
579 by IPv6 back up to the user process.
580 .SH SEE ALSO
581 .sp
582 .LP
583 \fBsvcs\fR(1), \fBndd\fR(1M), \fBrouteadm\fR(1M), \fBsvcadm\fR(1M),
584 \fBread\fR(2), \fBwrite\fR(2), \fBbind\fR(3SOCKET), \fBconnect\fR(3SOCKET),
585 \fBgetsockopt\fR(3SOCKET), \fBrecv\fR(3SOCKET), \fBrecvmsg\fR(3SOCKET),
586 \fBsend\fR(3SOCKET), \fBsendmsg\fR(3SOCKET), \fBsetsockopt\fR(3SOCKET),
587 \fBdefaultrouter\fR(4), \fBsmf\fR(5), \fBicmp6\fR(7P), \fBif_tcp\fR(7P),
588 \fBipsec\fR(7P), \fBinet6\fR(7P), \fBrouting\fR(7P), \fBtcp\fR(7P),
589 \fBudp\fR(7P)
590 .sp
591 .LP
592 Deering, S. and Hinden, B. \fI RFC 2460, Internet Protocol, Version 6 (IPv6)
593 Specification\fR. The Internet Society. December, 1998.
594 .sp
595 .LP
596 Stevens, W., and Thomas, M. \fIRFC 2292, Advanced Sockets API for IPv6\fR.
597 Network Working Group. February 1998.
598 .SH DIAGNOSTICS
599 .sp
600 .LP
601 A socket operation may fail with one of the following errors returned:
602 .sp
603 .ne 2
604 .na
605 \fB\fBEPROTONOSUPPORT\fR\fR
606 .ad
607 .RS 19n
608 Unsupported protocol (for example, IPPROTO_RAW.)
609 .RE
611 .sp
612 .ne 2
613 .na
614 \fB\fBEACCES\fR\fR
615 .ad
616 .RS 19n
617 A \fBbind()\fR operation was attempted with a "reserved" port number and the
618 effective user ID of the process was not the privileged user.
619 .RE
621 .sp
622 .ne 2
623 .na
624 \fB\fBEADDRINUSE\fR\fR
625 .ad
626 .RS 19n
627 A \fBbind()\fR operation was attempted on a socket with a network address/port
628 pair that has already been bound to another socket.
629 .RE
631 .sp
632 .ne 2
633 .na
634 \fB\fBEADDRNOTAVAIL\fR\fR
635 .ad
636 .RS 19n
637 A \fBbind()\fR operation was attempted for an address that is not configured on
638 this machine.
639 .RE
641 .sp
642 .ne 2
643 .na
644 \fB\fBEINVAL\fR\fR
645 .ad
646 .RS 19n
647 A \fBsendmsg()\fR operation with a non-NULL \fBmsg_accrights\fR was attempted.
648 .RE
650 .sp
651 .ne 2
652 .na
653 \fB\fBEINVAL\fR\fR
654 .ad
655 .RS 19n
656 A \fBgetsockopt()\fR or \fBsetsockopt()\fR operation with an unknown socket
657 option name was given.
658 .RE
660 .sp
661 .ne 2
662 .na
663 \fB\fBEINVAL\fR\fR
664 .ad
665 .RS 19n
666 A \fBgetsockopt()\fR or \fBsetsockopt()\fR operation was attempted with the
667 \fBIPv6\fR option field improperly formed; an option field was shorter than the
668 minimum value or longer than the option buffer provided; the value in the
669 option field was invalid.
670 .RE
672 .sp
673 .ne 2
674 .na
675 \fB\fBEISCONN\fR\fR
676 .ad
677 .RS 19n
678 A \fBconnect()\fR operation was attempted on a socket on which a
679 \fBconnect()\fR operation had already been performed, and the socket could not
680 be successfully disconnected before making the new connection.
681 .RE
683 .sp
684 .ne 2
685 .na
686 \fB\fBEISCONN\fR\fR
687 .ad
688 .RS 19n
689 A \fBsendto()\fR or \fBsendmsg()\fR operation specifying an address to which
690 the message should be sent was attempted on a socket on which a \fBconnect()\fR
691 operation had already been performed.
692 .RE
694 .sp
695 .ne 2
696 .na
697 \fB\fBEMSGSIZE\fR\fR
698 .ad
699 .RS 19n
700 A \fBsend()\fR, \fBsendto()\fR, or \fBsendmsg()\fR operation was attempted to
701 send a datagram that was too large for an interface, but was not allowed to be
702 fragmented (such as broadcasts).
703 .RE
705 .sp
706 .ne 2
707 .na
708 \fB\fBENETUNREACH\fR\fR
709 .ad
710 .RS 19n
711 An attempt was made to establish a connection via \fBconnect()\fR, or to send a
712 datagram by means of \fBsendto()\fR or \fBsendmsg()\fR, where there was no
713 matching entry in the routing table; or if an \fBICMP\fR "\fBdestination
714 unreachable\fR" message was received.
715 .RE
717 .sp
718 .ne 2
719 .na
720 \fB\fBENOTCONN\fR\fR
721 .ad
722 .RS 19n
723 A \fBsend()\fR or \fBwrite()\fR operation, or a \fBsendto()\fR or
724 \fBsendmsg()\fR operation not specifying an address to which the message should
725 be sent, was attempted on a socket on which a \fBconnect()\fR operation had not
726 already been performed.
727 .RE
729 .sp
730 .ne 2
731 .na
732 \fB\fBENOBUFS\fR\fR
733 .ad
734 .RS 19n
735 The system ran out of memory for fragmentation buffers or other internal data
736 structures.
737 .RE
739 .sp
740 .ne 2
741 .na
742 \fB\fBENOMEM\fR\fR
743 .ad
744 .RS 19n
745 The system was unable to allocate memory for an \fBIPv6\fR socket option or
746 other internal data structures.
747 .RE
749 .sp
750 .ne 2
751 .na
752 \fB\fBENOPROTOOPT\fR\fR
753 .ad
754 .RS 19n
755 An \fBIP\fR socket option was attempted on an \fBIPv6\fR socket, or an
756 \fBIPv6\fR socket option was attempted on an \fBIP\fR socket.
757 .RE
759 .sp
760 .ne 2
761 .na
762 \fB\fBENOPROTOOPT\fR\fR
763 .ad
764 .RS 19n
765 Invalid socket type for the option.
766 .RE
768 .SH NOTES
769 .sp
770 .LP
771 Applications using the sockets \fBAPI\fR must use the Advanced Sockets
772 \fBAPI\fR for \fBIPv6\fR (\fIRFC 2292\fR) to see elements of the inbound
773 packet's \fBIPv6\fR header or extension headers.
774 .sp
775 .LP
776 The \fBip6\fR service is managed by the service management facility,
777 \fBsmf\fR(5), under the service identifier:
778 .sp
779 .in +2
780 .nf
781 svc:/network/initial:default
782 .fi
783 .in -2
784 .sp
786 .sp
787 .LP
788 Administrative actions on this service, such as enabling, disabling, or
789 requesting restart, can be performed using \fBsvcadm\fR(1M). The service's
790 status can be queried using the \fBsvcs\fR(1) command.