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