Searched refs:datagram (Results 1 – 25 of 49) sorted by relevance
12
12 BIO_dgram_get_mtu_overhead - Network BIO with datagram semantics32 which provide datagram semantics, such as UDP sockets. It is suitable for use35 Because BIO_s_datagram() has datagram semantics, a single BIO_write() call sends36 a single datagram and a single BIO_read() call receives a single datagram. If37 the size of the buffer passed to BIO_read() is inadequate, the datagram is63 subsequent call to BIO_write() being set to the source address of the datagram116 The peer address of the datagram last received by a call to BIO_read().141 overhead which should typically be added to a datagram payload size in order to143 datagram. In most cases, the maximum datagram payload size which can be150 The value returned is not fully reliable because datagram overheads can be[all …]
35 If DTLS is used over UDP (or any datagram based protocol that does not validate70 datagram on an unconnected socket. If the socket is not connected, it can75 redirected to it by sending a datagram to the socket in question. This does not93 B<only> supports ClientHellos that fit inside a single datagram.
57 Receive UDP datagram from a client, then send it to the client61 Send UDP datagram to a server, then receive datagram from it92 Multicast UDP datagram receiver95 UDP datagram sender (not only unicast but also multicast)
1 # UDP/datagram sockets11 The `node:dgram` module provides an implementation of UDP datagram sockets.66 Encapsulates the datagram functionality.125 The `'message'` event is emitted when a new datagram is available on a socket.245 For UDP sockets, causes the `dgram.Socket` to listen for datagram257 A bound datagram socket keeps the Node.js process running to receive258 datagram messages.323 For UDP sockets, causes the `dgram.Socket` to listen for datagram348 A bound datagram socket keeps the Node.js process running to receive349 datagram messages.[all …]
94 | [UDP/datagram sockets](dgram.html) | (2) Stable |
65 …ent.c): a simple DTLS client program, which sends one datagram to the server and reads one datagra…67 …c): a simple DTLS server program, which expects one datagram from the client and writes one datagr…
1 Verify that the kernel is not crashed with receiving and sending UDP datagram
1 Verify that the kernel is not crashed with receiving and sending UDP datagram with the following co…
83 empty datagram was received (in this case `addr` is not NULL). < 0 if167 The only requirement of the `sock` argument is that it follows the datagram169 In other words, other datagram-type sockets like raw sockets or netlink176 it's required that it represents a valid datagram socket.
3529 datalen = ngtcp2_vec_len(vmsg->datagram.data, vmsg->datagram.datacnt); in conn_write_pkt()4105 nfrc->fr.datagram.type = NGTCP2_FRAME_DATAGRAM_LEN; in conn_write_pkt()4106 nfrc->fr.datagram.dgram_id = vmsg->datagram.dgram_id; in conn_write_pkt()4107 nfrc->fr.datagram.datacnt = vmsg->datagram.datacnt; in conn_write_pkt()4108 nfrc->fr.datagram.data = (ngtcp2_vec *)vmsg->datagram.data; in conn_write_pkt()4117 nfrc->fr.datagram.datacnt = 0; in conn_write_pkt()4118 nfrc->fr.datagram.data = NULL; in conn_write_pkt()4123 lfr.datagram.type = NGTCP2_FRAME_DATAGRAM_LEN; in conn_write_pkt()4124 lfr.datagram.datacnt = vmsg->datagram.datacnt; in conn_write_pkt()4125 lfr.datagram.data = (ngtcp2_vec *)vmsg->datagram.data; in conn_write_pkt()[all …]
732 ngtcp2_vmsg_datagram datagram; member
365 ngtcp2_datagram datagram; member
601 rv = conn->callbacks.lost_datagram(conn, frc->fr.datagram.dgram_id, in conn_process_lost_datagram()870 rv = conn->callbacks.ack_datagram(conn, frc->fr.datagram.dgram_id, in rtb_process_acked_pkt()1544 rv = conn->callbacks.lost_datagram(conn, frc->fr.datagram.dgram_id, in rtb_on_pkt_lost_resched_move()
535 log_fr_datagram(log, hd, &fr->datagram, dir); in log_fr()
29 size_t message_total_length; /**< total length for datagram protocols,
21 If necessary/implemented, any reliable stream or datagram based
131 A transport for datagram (UDP) connections.471 The base class for implementing datagram (UDP) protocols.655 Called when a datagram is received. *data* is a bytes object containing665 detects that a datagram could not be delivered to its recipient.672 for datagram protocols, because there is no reliable way to detect send
166 - Open a datagram (UDP) connection.462 - Called when a datagram is received.
150 class. The request handler class must be different for datagram or stream412 The type of :attr:`self.request` is different for datagram or stream414 datagram services, :attr:`self.request` is a pair of string and socket.
133 Type is 'coap' (using datagram), 'coap+tcp' (using stream), 'coaps'134 (DTLS using datagram) or 'coaps+tcp' (TLS using stream).
470 def datagram(self, name, **kwargs): member in StreamClient
142 not NULL, it indicates that an empty datagram was received from the host at
145 /* Adjust datagram length by adding header lengths. */