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