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