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