xref: /freebsd-14.2/lib/libc/sys/getsockopt.2 (revision d8aaf097)
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.\" 3. 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.\"
30.Dd February 8, 2021
31.Dt GETSOCKOPT 2
32.Os
33.Sh NAME
34.Nm getsockopt ,
35.Nm setsockopt
36.Nd get and set options on sockets
37.Sh LIBRARY
38.Lb libc
39.Sh SYNOPSIS
40.In sys/types.h
41.In sys/socket.h
42.Ft int
43.Fn getsockopt "int s" "int level" "int optname" "void * restrict optval" "socklen_t * restrict optlen"
44.Ft int
45.Fn setsockopt "int s" "int level" "int optname" "const void *optval" "socklen_t optlen"
46.Sh DESCRIPTION
47The
48.Fn getsockopt
49and
50.Fn setsockopt
51system calls
52manipulate the
53.Em options
54associated with a socket.
55Options may exist at multiple
56protocol levels; they are always present at the uppermost
57.Dq socket
58level.
59.Pp
60When manipulating socket options the level at which the
61option resides and the name of the option must be specified.
62To manipulate options at the socket level,
63.Fa level
64is specified as
65.Dv SOL_SOCKET .
66To manipulate options at any
67other level the protocol number of the appropriate protocol
68controlling the option is supplied.
69For example,
70to indicate that an option is to be interpreted by the
71.Tn TCP
72protocol,
73.Fa level
74should be set to the protocol number of
75.Tn TCP ;
76see
77.Xr getprotoent 3 .
78.Pp
79The
80.Fa optval
81and
82.Fa optlen
83arguments
84are used to access option values for
85.Fn setsockopt .
86For
87.Fn getsockopt
88they identify a buffer in which the value for the
89requested option(s) are to be returned.
90For
91.Fn getsockopt ,
92.Fa optlen
93is a value-result argument, initially containing the
94size of the buffer pointed to by
95.Fa optval ,
96and modified on return to indicate the actual size of
97the value returned.
98If no option value is
99to be supplied or returned,
100.Fa optval
101may be NULL.
102.Pp
103The
104.Fa optname
105argument
106and any specified options are passed uninterpreted to the appropriate
107protocol module for interpretation.
108The include file
109.In sys/socket.h
110contains definitions for
111socket level options, described below.
112Options at other protocol levels vary in format and
113name; consult the appropriate entries in
114section
1154 of the manual.
116.Pp
117Most socket-level options utilize an
118.Vt int
119argument for
120.Fa optval .
121For
122.Fn setsockopt ,
123the argument should be non-zero to enable a boolean option,
124or zero if the option is to be disabled.
125.Dv SO_LINGER
126uses a
127.Vt "struct linger"
128argument, defined in
129.In sys/socket.h ,
130which specifies the desired state of the option and the
131linger interval (see below).
132.Dv SO_SNDTIMEO
133and
134.Dv SO_RCVTIMEO
135use a
136.Vt "struct timeval"
137argument, defined in
138.In sys/time.h .
139.Pp
140The following options are recognized at the socket level.
141For protocol-specific options, see protocol manual pages,
142e.g.
143.Xr ip 4
144or
145.Xr tcp 4 .
146Except as noted, each may be examined with
147.Fn getsockopt
148and set with
149.Fn setsockopt .
150.Bl -column SO_ACCEPTFILTER -offset indent
151.It Dv SO_DEBUG Ta "enables recording of debugging information"
152.It Dv SO_REUSEADDR Ta "enables local address reuse"
153.It Dv SO_REUSEPORT Ta "enables duplicate address and port bindings"
154.It Dv SO_REUSEPORT_LB Ta "enables duplicate address and port bindings with load balancing"
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_DOMAIN Ta "get the domain of the socket (get only)"
175.It Dv SO_TYPE Ta "get the type of the socket (get only)"
176.It Dv SO_PROTOCOL Ta "get the protocol number for the socket (get only)"
177.It Dv SO_PROTOTYPE Ta "SunOS alias for the Linux SO_PROTOCOL (get only)"
178.It Dv SO_ERROR Ta "get and clear error on the socket (get only)"
179.It Dv SO_RERROR Ta "enables receive error reporting"
180.It Dv SO_SETFIB Ta "set the associated FIB (routing table) for the socket (set only)"
181.El
182.Pp
183The following options are recognized in
184.Fx :
185.Bl -column SO_LISTENINCQLEN -offset indent
186.It Dv SO_LABEL Ta "get MAC label of the socket (get only)"
187.It Dv SO_PEERLABEL Ta "get socket's peer's MAC label (get only)"
188.It Dv SO_LISTENQLIMIT Ta "get backlog limit of the socket (get only)"
189.It Dv SO_LISTENQLEN Ta "get complete queue length of the socket (get only)"
190.It Dv SO_LISTENINCQLEN Ta "get incomplete queue length of the socket (get only)"
191.It Dv SO_USER_COOKIE Ta "set the 'so_user_cookie' value for the socket (uint32_t, set only)"
192.It Dv SO_TS_CLOCK Ta "set specific format of timestamp returned by SO_TIMESTAMP"
193.It Dv SO_MAX_PACING_RATE Ta "set the maximum transmit rate in bytes per second for the socket"
194.It Dv SO_NO_OFFLOAD Ta "disables protocol offloads"
195.It Dv SO_NO_DDP Ta "disables direct data placement offload"
196.El
197.Pp
198.Dv SO_DEBUG
199enables debugging in the underlying protocol modules.
200.Pp
201.Dv SO_REUSEADDR
202indicates that the rules used in validating addresses supplied
203in a
204.Xr bind 2
205system call should allow reuse of local addresses.
206.Pp
207.Dv SO_REUSEPORT
208allows completely duplicate bindings by multiple processes
209if they all set
210.Dv SO_REUSEPORT
211before binding the port.
212This option permits multiple instances of a program to each
213receive UDP/IP multicast or broadcast datagrams destined for the bound port.
214.Pp
215.Dv SO_REUSEPORT_LB
216allows completely duplicate bindings by multiple sockets
217if they all set
218.Dv SO_REUSEPORT_LB
219before binding the port.
220Incoming TCP and UDP connections are distributed among the participating
221listening sockets based on a hash function of local port number, and foreign IP
222address and port number.
223A maximum of 256 sockets can be bound to the same load-balancing group.
224.Pp
225.Dv SO_KEEPALIVE
226enables the
227periodic transmission of messages on a connected socket.
228Should the
229connected party fail to respond to these messages, the connection is
230considered broken and processes using the socket are notified via a
231.Dv SIGPIPE
232signal when attempting to send data.
233.Pp
234.Dv SO_DONTROUTE
235indicates that outgoing messages should
236bypass the standard routing facilities.
237Instead, messages are directed
238to the appropriate network interface according to the network portion
239of the destination address.
240.Pp
241.Dv SO_LINGER
242controls the action taken when unsent messages
243are queued on socket and a
244.Xr close 2
245is performed.
246If the socket promises reliable delivery of data and
247.Dv SO_LINGER
248is set,
249the system will block the process on the
250.Xr close 2
251attempt until it is able to transmit the data or until it decides it
252is unable to deliver the information (a timeout period, termed the
253linger interval, is specified in seconds in the
254.Fn setsockopt
255system call when
256.Dv SO_LINGER
257is requested).
258If
259.Dv SO_LINGER
260is disabled and a
261.Xr close 2
262is issued, the system will process the close in a manner that allows
263the process to continue as quickly as possible.
264.Pp
265The option
266.Dv SO_BROADCAST
267requests permission to send broadcast datagrams
268on the socket.
269Broadcast was a privileged operation in earlier versions of the system.
270.Pp
271With protocols that support out-of-band data, the
272.Dv SO_OOBINLINE
273option
274requests that out-of-band data be placed in the normal data input queue
275as received; it will then be accessible with
276.Xr recv 2
277or
278.Xr read 2
279calls without the
280.Dv MSG_OOB
281flag.
282Some protocols always behave as if this option is set.
283.Pp
284.Dv SO_SNDBUF
285and
286.Dv SO_RCVBUF
287are options to adjust the normal
288buffer sizes allocated for output and input buffers, respectively.
289The buffer size may be increased for high-volume connections,
290or may be decreased to limit the possible backlog of incoming data.
291The system places an absolute maximum on these values, which is accessible
292through the
293.Xr sysctl 3
294MIB variable
295.Dq Li kern.ipc.maxsockbuf .
296.Pp
297.Dv SO_SNDLOWAT
298is an option to set the minimum count for output operations.
299Most output operations process all of the data supplied
300by the call, delivering data to the protocol for transmission
301and blocking as necessary for flow control.
302Nonblocking output operations will process as much data as permitted
303subject to flow control without blocking, but will process no data
304if flow control does not allow the smaller of the low water mark value
305or the entire request to be processed.
306A
307.Xr select 2
308operation testing the ability to write to a socket will return true
309only if the low water mark amount could be processed.
310The default value for
311.Dv SO_SNDLOWAT
312is set to a convenient size for network efficiency, often 1024.
313.Pp
314.Dv SO_RCVLOWAT
315is an option to set the minimum count for input operations.
316In general, receive calls will block until any (non-zero) amount of data
317is received, then return with the smaller of the amount available or the amount
318requested.
319The default value for
320.Dv SO_RCVLOWAT
321is 1.
322If
323.Dv SO_RCVLOWAT
324is set to a larger value, blocking receive calls normally
325wait until they have received the smaller of the low water mark value
326or the requested amount.
327Receive calls may still return less than the low water mark if an error
328occurs, a signal is caught, or the type of data next in the receive queue
329is different from that which was returned.
330.Pp
331.Dv SO_SNDTIMEO
332is an option to set a timeout value for output operations.
333It accepts a
334.Vt "struct timeval"
335argument with the number of seconds and microseconds
336used to limit waits for output operations to complete.
337If a send operation has blocked for this much time,
338it returns with a partial count
339or with the error
340.Er EWOULDBLOCK
341if no data were sent.
342In the current implementation, this timer is restarted each time additional
343data are delivered to the protocol,
344implying that the limit applies to output portions ranging in size
345from the low water mark to the high water mark for output.
346.Pp
347.Dv SO_RCVTIMEO
348is an option to set a timeout value for input operations.
349It accepts a
350.Vt "struct timeval"
351argument with the number of seconds and microseconds
352used to limit waits for input operations to complete.
353In the current implementation, this timer is restarted each time additional
354data are received by the protocol,
355and thus the limit is in effect an inactivity timer.
356If a receive operation has been blocked for this much time without
357receiving additional data, it returns with a short count
358or with the error
359.Er EWOULDBLOCK
360if no data were received.
361.Pp
362.Dv SO_SETFIB
363can be used to over-ride the default FIB (routing table) for the given socket.
364The value must be from 0 to one less than the number returned from
365the sysctl
366.Em net.fibs .
367.Pp
368.Dv SO_USER_COOKIE
369can be used to set the uint32_t so_user_cookie field in the socket.
370The value is an uint32_t, and can be used in the kernel code that
371manipulates traffic related to the socket.
372The default value for the field is 0.
373As an example, the value can be used as the skipto target or
374pipe number in
375.Nm ipfw/dummynet .
376.Pp
377.Dv SO_ACCEPTFILTER
378places an
379.Xr accept_filter 9
380on the socket,
381which will filter incoming connections
382on a listening stream socket before being presented for
383.Xr accept 2 .
384Once more,
385.Xr listen 2
386must be called on the socket before
387trying to install the filter on it,
388or else the
389.Fn setsockopt
390system call will fail.
391.Bd -literal
392struct  accept_filter_arg {
393        char    af_name[16];
394        char    af_arg[256-16];
395};
396.Ed
397.Pp
398The
399.Fa optval
400argument
401should point to a
402.Fa struct accept_filter_arg
403that will select and configure the
404.Xr accept_filter 9 .
405The
406.Fa af_name
407argument
408should be filled with the name of the accept filter
409that the application wishes to place on the listening socket.
410The optional argument
411.Fa af_arg
412can be passed to the accept
413filter specified by
414.Fa af_name
415to provide additional configuration options at attach time.
416Passing in an
417.Fa optval
418of NULL will remove the filter.
419.Pp
420The
421.Dv SO_NOSIGPIPE
422option controls generation of the
423.Dv SIGPIPE
424signal normally sent
425when writing to a connected socket where the other end has been
426closed returns with the error
427.Er EPIPE .
428.Pp
429If the
430.Dv SO_TIMESTAMP
431or
432.Dv SO_BINTIME
433option is enabled on a
434.Dv SOCK_DGRAM
435socket, the
436.Xr recvmsg 2
437call may return a timestamp corresponding to when the datagram was received.
438However, it may not, for example due to a resource shortage.
439The
440.Va msg_control
441field in the
442.Vt msghdr
443structure points to a buffer that contains a
444.Vt cmsghdr
445structure followed by a
446.Vt "struct timeval"
447for
448.Dv SO_TIMESTAMP
449and
450.Vt "struct bintime"
451for
452.Dv SO_BINTIME .
453The
454.Vt cmsghdr
455fields have the following values for TIMESTAMP by default:
456.Bd -literal
457     cmsg_len = CMSG_LEN(sizeof(struct timeval));
458     cmsg_level = SOL_SOCKET;
459     cmsg_type = SCM_TIMESTAMP;
460.Ed
461.Pp
462and for
463.Dv SO_BINTIME :
464.Bd -literal
465     cmsg_len = CMSG_LEN(sizeof(struct bintime));
466     cmsg_level = SOL_SOCKET;
467     cmsg_type = SCM_BINTIME;
468.Ed
469.Pp
470Additional timestamp types are available by following
471.Dv SO_TIMESTAMP
472with
473.Dv SO_TS_CLOCK ,
474which requests a specific timestamp format to be returned instead of
475.Dv SCM_TIMESTAMP when
476.Dv SO_TIMESTAMP is enabled.
477These
478.Dv SO_TS_CLOCK
479values are recognized in
480.Fx :
481.Bl -column SO_TS_CLOCK -offset indent
482.It Dv SO_TS_REALTIME_MICRO Ta "realtime (SCM_TIMESTAMP, struct timeval), default"
483.It Dv SO_TS_BINTIME Ta "realtime (SCM_BINTIME, struct bintime)"
484.It Dv SO_TS_REALTIME Ta "realtime (SCM_REALTIME, struct timespec)"
485.It Dv SO_TS_MONOTONIC Ta "monotonic time (SCM_MONOTONIC, struct timespec)"
486.El
487.Pp
488.Dv SO_ACCEPTCONN ,
489.Dv SO_TYPE ,
490.Dv SO_PROTOCOL
491(and its alias
492.Dv SO_PROTOTYPE )
493and
494.Dv SO_ERROR
495are options used only with
496.Fn getsockopt .
497.Dv SO_ACCEPTCONN
498returns whether the socket is currently accepting connections,
499that is, whether or not the
500.Xr listen 2
501system call was invoked on the socket.
502.Dv SO_TYPE
503returns the type of the socket, such as
504.Dv SOCK_STREAM ;
505it is useful for servers that inherit sockets on startup.
506.Dv SO_PROTOCOL
507returns the protocol number for the socket, for
508.Dv AF_INET
509and
510.Dv AF_INET6
511address families.
512.Dv SO_ERROR
513returns any pending error on the socket and clears
514the error status.
515It may be used to check for asynchronous errors on connected
516datagram sockets or for other asynchronous errors.
517.Dv SO_RERROR
518indicates that receive buffer overflows should be handled as errors.
519Historically receive buffer overflows have been ignored and programs
520could not tell if they missed messages or messages had been truncated
521because of overflows.
522Since programs historically do not expect to get receive overflow errors,
523this behavior is not the default.
524.Pp
525.Dv SO_LABEL
526returns the MAC label of the socket.
527.Dv SO_PEERLABEL
528returns the MAC label of the socket's peer.
529Note that your kernel must be compiled with MAC support.
530See
531.Xr mac 3
532for more information.
533.Pp
534.Dv SO_LISTENQLIMIT
535returns the maximal number of queued connections, as set by
536.Xr listen 2 .
537.Dv SO_LISTENQLEN
538returns the number of unaccepted complete connections.
539.Dv SO_LISTENINCQLEN
540returns the number of unaccepted incomplete connections.
541.Pp
542.Dv SO_MAX_PACING_RATE
543instruct the socket and underlying network adapter layers to limit the
544transfer rate to the given unsigned 32-bit value in bytes per second.
545.Pp
546.Dv SO_NO_OFFLOAD
547disables support for protocol offloads.
548At present, this prevents TCP sockets from using TCP offload engines.
549.Dv SO_NO_DDP
550disables support for a specific TCP offload known as direct data
551placement (DDP).
552DDP is an offload supported by Chelsio network adapters that permits
553reassembled TCP data streams to be received via zero-copy in
554user-supplied buffers using
555.Xr aio_read 2 .
556.Sh RETURN VALUES
557.Rv -std
558.Sh ERRORS
559The
560.Fn getsockopt
561and
562.Fn setsockopt
563system calls succeed unless:
564.Bl -tag -width Er
565.It Bq Er EBADF
566The argument
567.Fa s
568is not a valid descriptor.
569.It Bq Er ENOTSOCK
570The argument
571.Fa s
572is a file, not a socket.
573.It Bq Er ENOPROTOOPT
574The option is unknown at the level indicated.
575.It Bq Er EFAULT
576The address pointed to by
577.Fa optval
578is not in a valid part of the process address space.
579For
580.Fn getsockopt ,
581this error may also be returned if
582.Fa optlen
583is not in a valid part of the process address space.
584.It Bq Er EINVAL
585Installing an
586.Xr accept_filter 9
587on a non-listening socket was attempted.
588.It Bq Er ENOMEM
589A memory allocation failed that was required to service the request.
590.El
591.Pp
592The
593.Fn setsockopt
594system call may also return the following error:
595.Bl -tag -width Er
596.It Bq Er ENOBUFS
597Insufficient resources were available in the system
598to perform the operation.
599.El
600.Sh SEE ALSO
601.Xr ioctl 2 ,
602.Xr listen 2 ,
603.Xr recvmsg 2 ,
604.Xr socket 2 ,
605.Xr getprotoent 3 ,
606.Xr mac 3 ,
607.Xr sysctl 3 ,
608.Xr ip 4 ,
609.Xr ip6 4 ,
610.Xr sctp 4 ,
611.Xr tcp 4 ,
612.Xr protocols 5 ,
613.Xr sysctl 8 ,
614.Xr accept_filter 9 ,
615.Xr bintime 9
616.Sh HISTORY
617The
618.Fn getsockopt
619and
620.Fn setsockopt
621system calls appeared in
622.Bx 4.2 .
623.Sh BUGS
624Several of the socket options should be handled at lower levels of the system.
625