Lines Matching full:sockets

32 .Nd Bluetooth sockets layer
48 .Ss Dv SOCK_RAW HCI sockets
52 Raw HCI sockets allow sending of raw HCI command datagrams
59 Raw HCI sockets can also be used to control HCI nodes.
63 /* Bluetooth version of struct sockaddr for raw HCI sockets */
71 Raw HCI sockets support a number of
117 .Va net.bluetooth.hci.sockets.raw.ioctl_timeout
120 controls the control request timeout (in seconds) for raw HCI sockets.
122 Raw HCI sockets support filters.
152 /* Bluetooth version of struct sockaddr for L2CAP sockets */
160 .Ss Dv SOCK_RAW L2CAP sockets
164 Raw L2CAP sockets do not provide access to raw L2CAP datagrams.
166 sockets used to control L2CAP nodes and to issue special L2CAP requests
173 Raw L2CAP sockets support number of
202 .Va net.bluetooth.l2cap.sockets.raw.ioctl_timeout
205 controls the control request timeout (in seconds) for raw L2CAP sockets.
206 .Ss Dv SOCK_SEQPACKET L2CAP sockets
210 L2CAP sockets are either
214 Active sockets initiate connections to passive sockets.
215 By default, L2CAP sockets are created active; to create a passive socket, the
220 Only passive sockets may use the
223 Only active sockets may use the
227 L2CAP sockets support
239 L2CAP sockets support number of options defined at
269 /* Bluetooth version of struct sockaddr for RFCOMM sockets */
277 .Ss Dv SOCK_STREAM RFCOMM sockets
278 Note that RFCOMM sockets do not have associated Netgraph node type.
279 RFCOMM sockets are implemented as additional layer on top of L2CAP sockets.
280 RFCOMM sockets are either
284 Active sockets initiate connections to passive sockets.
285 By default, RFCOMM sockets are created active; to create a passive socket, the
290 Only passive sockets may use the
293 Only active sockets may use the
297 RFCOMM sockets support
313 level for RFCOMM sockets:
324 .Va net.bluetooth.rfcomm.sockets.stream.timeout
327 controls the connection timeout (in seconds) for RFCOMM sockets.