xref: /freebsd-14.2/lib/libc/sys/getsockopt.2 (revision 5f761d3c)
1.\" Copyright (c) 1983, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 4. Neither the name of the University nor the names of its contributors
13.\"    may be used to endorse or promote products derived from this software
14.\"    without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.\"     @(#)getsockopt.2	8.4 (Berkeley) 5/2/95
29.\" $FreeBSD$
30.\"
31.Dd April 5, 2013
32.Dt GETSOCKOPT 2
33.Os
34.Sh NAME
35.Nm getsockopt ,
36.Nm setsockopt
37.Nd get and set options on sockets
38.Sh LIBRARY
39.Lb libc
40.Sh SYNOPSIS
41.In sys/types.h
42.In sys/socket.h
43.Ft int
44.Fn getsockopt "int s" "int level" "int optname" "void * restrict optval" "socklen_t * restrict optlen"
45.Ft int
46.Fn setsockopt "int s" "int level" "int optname" "const void *optval" "socklen_t optlen"
47.Sh DESCRIPTION
48The
49.Fn getsockopt
50and
51.Fn setsockopt
52system calls
53manipulate the
54.Em options
55associated with a socket.
56Options may exist at multiple
57protocol levels; they are always present at the uppermost
58.Dq socket
59level.
60.Pp
61When manipulating socket options the level at which the
62option resides and the name of the option must be specified.
63To manipulate options at the socket level,
64.Fa level
65is specified as
66.Dv SOL_SOCKET .
67To manipulate options at any
68other level the protocol number of the appropriate protocol
69controlling the option is supplied.
70For example,
71to indicate that an option is to be interpreted by the
72.Tn TCP
73protocol,
74.Fa level
75should be set to the protocol number of
76.Tn TCP ;
77see
78.Xr getprotoent 3 .
79.Pp
80The
81.Fa optval
82and
83.Fa optlen
84arguments
85are used to access option values for
86.Fn setsockopt .
87For
88.Fn getsockopt
89they identify a buffer in which the value for the
90requested option(s) are to be returned.
91For
92.Fn getsockopt ,
93.Fa optlen
94is a value-result argument, initially containing the
95size of the buffer pointed to by
96.Fa optval ,
97and modified on return to indicate the actual size of
98the value returned.
99If no option value is
100to be supplied or returned,
101.Fa optval
102may be NULL.
103.Pp
104The
105.Fa optname
106argument
107and any specified options are passed uninterpreted to the appropriate
108protocol module for interpretation.
109The include file
110.In sys/socket.h
111contains definitions for
112socket level options, described below.
113Options at other protocol levels vary in format and
114name; consult the appropriate entries in
115section
1164 of the manual.
117.Pp
118Most socket-level options utilize an
119.Vt int
120argument for
121.Fa optval .
122For
123.Fn setsockopt ,
124the argument should be non-zero to enable a boolean option,
125or zero if the option is to be disabled.
126.Dv SO_LINGER
127uses a
128.Vt "struct linger"
129argument, defined in
130.In sys/socket.h ,
131which specifies the desired state of the option and the
132linger interval (see below).
133.Dv SO_SNDTIMEO
134and
135.Dv SO_RCVTIMEO
136use a
137.Vt "struct timeval"
138argument, defined in
139.In sys/time.h .
140.Pp
141The following options are recognized at the socket level.
142For protocol-specific options, see protocol manual pages,
143e.g.
144.Xr ip 4
145or
146.Xr tcp 4 .
147Except as noted, each may be examined with
148.Fn getsockopt
149and set with
150.Fn setsockopt .
151.Bl -column SO_ACCEPTFILTER -offset indent
152.It Dv SO_DEBUG Ta "enables recording of debugging information"
153.It Dv SO_REUSEADDR Ta "enables local address reuse"
154.It Dv SO_REUSEPORT Ta "enables duplicate address and port bindings"
155.It Dv SO_KEEPALIVE Ta "enables keep connections alive"
156.It Dv SO_DONTROUTE Ta "enables routing bypass for outgoing messages"
157.It Dv SO_LINGER  Ta "linger on close if data present"
158.It Dv SO_BROADCAST Ta "enables permission to transmit broadcast messages"
159.It Dv SO_OOBINLINE Ta "enables reception of out-of-band data in band"
160.It Dv SO_SNDBUF Ta "set buffer size for output"
161.It Dv SO_RCVBUF Ta "set buffer size for input"
162.It Dv SO_SNDLOWAT Ta "set minimum count for output"
163.It Dv SO_RCVLOWAT Ta "set minimum count for input"
164.It Dv SO_SNDTIMEO Ta "set timeout value for output"
165.It Dv SO_RCVTIMEO Ta "set timeout value for input"
166.It Dv SO_ACCEPTFILTER Ta "set accept filter on listening socket"
167.It Dv SO_NOSIGPIPE Ta
168controls generation of
169.Dv SIGPIPE
170for the socket
171.It Dv SO_TIMESTAMP Ta "enables reception of a timestamp with datagrams"
172.It Dv SO_BINTIME Ta "enables reception of a timestamp with datagrams"
173.It Dv SO_ACCEPTCONN Ta "get listening status of the socket (get only)"
174.It Dv SO_TYPE Ta "get the type of the socket (get only)"
175.It Dv SO_PROTOCOL Ta "get the protocol number for the socket (get only)"
176.It Dv SO_PROTOTYPE Ta "SunOS alias for the Linux SO_PROTOCOL (get only)"
177.It Dv SO_ERROR Ta "get and clear error on the socket (get only)"
178.It Dv SO_SETFIB Ta "set the associated FIB (routing table) for the socket (set only)"
179.El
180.Pp
181The following options are recognized in
182.Fx :
183.Bl -column SO_LISTENINCQLEN -offset indent
184.It Dv SO_LABEL Ta "get MAC label of the socket (get only)"
185.It Dv SO_PEERLABEL Ta "get socket's peer's MAC label (get only)"
186.It Dv SO_LISTENQLIMIT Ta "get backlog limit of the socket (get only)"
187.It Dv SO_LISTENQLEN Ta "get complete queue length of the socket (get only)"
188.It Dv SO_LISTENINCQLEN Ta "get incomplete queue length of the socket (get only)"
189.It Dv SO_USER_COOKIE Ta "set the 'so_user_cookie' value for the socket (uint32_t, set only)"
190.It Dv SO_TS_CLOCK Ta "set specific format of timestamp returned by SO_TIMESTAMP"
191.El
192.Pp
193.Dv SO_DEBUG
194enables debugging in the underlying protocol modules.
195.Pp
196.Dv SO_REUSEADDR
197indicates that the rules used in validating addresses supplied
198in a
199.Xr bind 2
200system call should allow reuse of local addresses.
201.Pp
202.Dv SO_REUSEPORT
203allows completely duplicate bindings by multiple processes
204if they all set
205.Dv SO_REUSEPORT
206before binding the port.
207This option permits multiple instances of a program to each
208receive UDP/IP multicast or broadcast datagrams destined for the bound port.
209.Pp
210.Dv SO_KEEPALIVE
211enables the
212periodic transmission of messages on a connected socket.
213Should the
214connected party fail to respond to these messages, the connection is
215considered broken and processes using the socket are notified via a
216.Dv SIGPIPE
217signal when attempting to send data.
218.Pp
219.Dv SO_DONTROUTE
220indicates that outgoing messages should
221bypass the standard routing facilities.
222Instead, messages are directed
223to the appropriate network interface according to the network portion
224of the destination address.
225.Pp
226.Dv SO_LINGER
227controls the action taken when unsent messages
228are queued on socket and a
229.Xr close 2
230is performed.
231If the socket promises reliable delivery of data and
232.Dv SO_LINGER
233is set,
234the system will block the process on the
235.Xr close 2
236attempt until it is able to transmit the data or until it decides it
237is unable to deliver the information (a timeout period, termed the
238linger interval, is specified in seconds in the
239.Fn setsockopt
240system call when
241.Dv SO_LINGER
242is requested).
243If
244.Dv SO_LINGER
245is disabled and a
246.Xr close 2
247is issued, the system will process the close in a manner that allows
248the process to continue as quickly as possible.
249.Pp
250The option
251.Dv SO_BROADCAST
252requests permission to send broadcast datagrams
253on the socket.
254Broadcast was a privileged operation in earlier versions of the system.
255.Pp
256With protocols that support out-of-band data, the
257.Dv SO_OOBINLINE
258option
259requests that out-of-band data be placed in the normal data input queue
260as received; it will then be accessible with
261.Xr recv 2
262or
263.Xr read 2
264calls without the
265.Dv MSG_OOB
266flag.
267Some protocols always behave as if this option is set.
268.Pp
269.Dv SO_SNDBUF
270and
271.Dv SO_RCVBUF
272are options to adjust the normal
273buffer sizes allocated for output and input buffers, respectively.
274The buffer size may be increased for high-volume connections,
275or may be decreased to limit the possible backlog of incoming data.
276The system places an absolute maximum on these values, which is accessible
277through the
278.Xr sysctl 3
279MIB variable
280.Dq Li kern.ipc.maxsockbuf .
281.Pp
282.Dv SO_SNDLOWAT
283is an option to set the minimum count for output operations.
284Most output operations process all of the data supplied
285by the call, delivering data to the protocol for transmission
286and blocking as necessary for flow control.
287Nonblocking output operations will process as much data as permitted
288subject to flow control without blocking, but will process no data
289if flow control does not allow the smaller of the low water mark value
290or the entire request to be processed.
291A
292.Xr select 2
293operation testing the ability to write to a socket will return true
294only if the low water mark amount could be processed.
295The default value for
296.Dv SO_SNDLOWAT
297is set to a convenient size for network efficiency, often 1024.
298.Pp
299.Dv SO_RCVLOWAT
300is an option to set the minimum count for input operations.
301In general, receive calls will block until any (non-zero) amount of data
302is received, then return with the smaller of the amount available or the amount
303requested.
304The default value for
305.Dv SO_RCVLOWAT
306is 1.
307If
308.Dv SO_RCVLOWAT
309is set to a larger value, blocking receive calls normally
310wait until they have received the smaller of the low water mark value
311or the requested amount.
312Receive calls may still return less than the low water mark if an error
313occurs, a signal is caught, or the type of data next in the receive queue
314is different from that which was returned.
315.Pp
316.Dv SO_SNDTIMEO
317is an option to set a timeout value for output operations.
318It accepts a
319.Vt "struct timeval"
320argument with the number of seconds and microseconds
321used to limit waits for output operations to complete.
322If a send operation has blocked for this much time,
323it returns with a partial count
324or with the error
325.Er EWOULDBLOCK
326if no data were sent.
327In the current implementation, this timer is restarted each time additional
328data are delivered to the protocol,
329implying that the limit applies to output portions ranging in size
330from the low water mark to the high water mark for output.
331.Pp
332.Dv SO_RCVTIMEO
333is an option to set a timeout value for input operations.
334It accepts a
335.Vt "struct timeval"
336argument with the number of seconds and microseconds
337used to limit waits for input operations to complete.
338In the current implementation, this timer is restarted each time additional
339data are received by the protocol,
340and thus the limit is in effect an inactivity timer.
341If a receive operation has been blocked for this much time without
342receiving additional data, it returns with a short count
343or with the error
344.Er EWOULDBLOCK
345if no data were received.
346.Pp
347.Dv SO_SETFIB
348can be used to over-ride the default FIB (routing table) for the given socket.
349The value must be from 0 to one less than the number returned from
350the sysctl
351.Em net.fibs .
352.Pp
353.Dv SO_USER_COOKIE
354can be used to set the uint32_t so_user_cookie field in the socket.
355The value is an uint32_t, and can be used in the kernel code that
356manipulates traffic related to the socket.
357The default value for the field is 0.
358As an example, the value can be used as the skipto target or
359pipe number in
360.Nm ipfw/dummynet .
361.Pp
362.Dv SO_ACCEPTFILTER
363places an
364.Xr accept_filter 9
365on the socket,
366which will filter incoming connections
367on a listening stream socket before being presented for
368.Xr accept 2 .
369Once more,
370.Xr listen 2
371must be called on the socket before
372trying to install the filter on it,
373or else the
374.Fn setsockopt
375system call will fail.
376.Bd -literal
377struct  accept_filter_arg {
378        char    af_name[16];
379        char    af_arg[256-16];
380};
381.Ed
382.Pp
383The
384.Fa optval
385argument
386should point to a
387.Fa struct accept_filter_arg
388that will select and configure the
389.Xr accept_filter 9 .
390The
391.Fa af_name
392argument
393should be filled with the name of the accept filter
394that the application wishes to place on the listening socket.
395The optional argument
396.Fa af_arg
397can be passed to the accept
398filter specified by
399.Fa af_name
400to provide additional configuration options at attach time.
401Passing in an
402.Fa optval
403of NULL will remove the filter.
404.Pp
405The
406.Dv SO_NOSIGPIPE
407option controls generation of the
408.Dv SIGPIPE
409signal normally sent
410when writing to a connected socket where the other end has been
411closed returns with the error
412.Er EPIPE .
413.Pp
414If the
415.Dv SO_TIMESTAMP
416or
417.Dv SO_BINTIME
418option is enabled on a
419.Dv SOCK_DGRAM
420socket, the
421.Xr recvmsg 2
422call will return a timestamp corresponding to when the datagram was received.
423The
424.Va msg_control
425field in the
426.Vt msghdr
427structure points to a buffer that contains a
428.Vt cmsghdr
429structure followed by a
430.Vt "struct timeval"
431for
432.Dv SO_TIMESTAMP
433and
434.Vt "struct bintime"
435for
436.Dv SO_BINTIME .
437The
438.Vt cmsghdr
439fields have the following values for TIMESTAMP by default:
440.Bd -literal
441     cmsg_len = CMSG_LEN(sizeof(struct timeval));
442     cmsg_level = SOL_SOCKET;
443     cmsg_type = SCM_TIMESTAMP;
444.Ed
445.Pp
446and for
447.Dv SO_BINTIME :
448.Bd -literal
449     cmsg_len = CMSG_LEN(sizeof(struct bintime));
450     cmsg_level = SOL_SOCKET;
451     cmsg_type = SCM_BINTIME;
452.Ed
453.Pp
454Additional timestamp types are available by following
455.Dv SO_TIMESTAMP
456with
457.Dv SO_TS_CLOCK ,
458which requests specific timestamp format to be returned instead of
459.Dv SCM_TIMESTAMP when
460.Dv SO_TIMESTAMP is enabled.
461The following
462.Dv SO_TS_CLOCK
463values are recognized in
464.Fx :
465.Bl -column SO_TS_CLOCK -offset indent
466.It Dv SO_TS_REALTIME_MICRO Ta "realtime (SCM_TIMESTAMP, struct timeval), default"
467.It Dv SO_TS_BINTIME Ta "realtime (SCM_BINTIME, struct bintime)"
468.It Dv SO_TS_REALTIME Ta "realtime (SCM_REALTIME, struct timespec)"
469.It Dv SO_TS_MONOTONIC Ta "monotonic time (SCM_MONOTONIC, struct timespec)"
470.El
471.Pp
472.Dv SO_ACCEPTCONN ,
473.Dv SO_TYPE ,
474.Dv SO_PROTOCOL
475(and its alias
476.Dv SO_PROTOTYPE )
477and
478.Dv SO_ERROR
479are options used only with
480.Fn getsockopt .
481.Dv SO_ACCEPTCONN
482returns whether the socket is currently accepting connections,
483that is, whether or not the
484.Xr listen 2
485system call was invoked on the socket.
486.Dv SO_TYPE
487returns the type of the socket, such as
488.Dv SOCK_STREAM ;
489it is useful for servers that inherit sockets on startup.
490.Dv SO_PROTOCOL
491returns the protocol number for the socket, for
492.Dv AF_INET
493and
494.Dv AF_INET6
495address families.
496.Dv SO_ERROR
497returns any pending error on the socket and clears
498the error status.
499It may be used to check for asynchronous errors on connected
500datagram sockets or for other asynchronous errors.
501.Pp
502Finally,
503.Dv SO_LABEL
504returns the MAC label of the socket.
505.Dv SO_PEERLABEL
506returns the MAC label of the socket's peer.
507Note that your kernel must be compiled with MAC support.
508See
509.Xr mac 3
510for more information.
511.Dv SO_LISTENQLIMIT
512returns the maximal number of queued connections, as set by
513.Xr listen 2 .
514.Dv SO_LISTENQLEN
515returns the number of unaccepted complete connections.
516.Dv SO_LISTENINCQLEN
517returns the number of unaccepted incomplete connections.
518.Sh RETURN VALUES
519.Rv -std
520.Sh ERRORS
521The call succeeds unless:
522.Bl -tag -width Er
523.It Bq Er EBADF
524The argument
525.Fa s
526is not a valid descriptor.
527.It Bq Er ENOTSOCK
528The argument
529.Fa s
530is a file, not a socket.
531.It Bq Er ENOPROTOOPT
532The option is unknown at the level indicated.
533.It Bq Er EFAULT
534The address pointed to by
535.Fa optval
536is not in a valid part of the process address space.
537For
538.Fn getsockopt ,
539this error may also be returned if
540.Fa optlen
541is not in a valid part of the process address space.
542.It Bq Er EINVAL
543Installing an
544.Xr accept_filter 9
545on a non-listening socket was attempted.
546.El
547.Sh SEE ALSO
548.Xr ioctl 2 ,
549.Xr listen 2 ,
550.Xr recvmsg 2 ,
551.Xr socket 2 ,
552.Xr getprotoent 3 ,
553.Xr mac 3 ,
554.Xr sysctl 3 ,
555.Xr ip 4 ,
556.Xr ip6 4 ,
557.Xr sctp 4 ,
558.Xr tcp 4 ,
559.Xr protocols 5 ,
560.Xr sysctl 8 ,
561.Xr accept_filter 9 ,
562.Xr bintime 9
563.Sh HISTORY
564The
565.Fn getsockopt
566and
567.Fn setsockopt
568system calls appeared in
569.Bx 4.2 .
570.Sh BUGS
571Several of the socket options should be handled at lower levels of the system.
572