Home
last modified time | relevance | path

Searched refs:datagram (Results 1 – 25 of 49) sorted by relevance

12

/src/crypto/openssl/doc/man3/
H A DBIO_s_dgram_pair.pod8 BIO_dgram_set0_local_addr - datagram pair BIO
29 BIO_s_dgram_pair() returns the method for a BIO datagram pair. A BIO datagram
30 pair is similar to a BIO pair (see L<BIO_s_bio(3)>) but has datagram semantics.
33 short, the datagram is truncated or the read fails, depending on how the BIO is
36 The BIO datagram pair attaches certain metadata to each write, such as source
39 A typical application of a BIO datagram pair is to allow an application to keep
40 all datagram network I/O requested by libssl under application control.
42 The BIO datagram pair is designed to support multithreaded use where certain
45 The BIO datagram pair allows each half of a pair to signal to the other half
53 L<BIO_make_bio_pair(3)> may be used to join two datagram pair BIOs into a pair.
[all …]
H A DBIO_s_datagram.pod13 BIO_dgram_get_mtu_overhead - Network BIO with datagram semantics
34 which provide datagram semantics, such as UDP sockets. It is suitable for use
37 Because BIO_s_datagram() has datagram semantics, a single BIO_write() call sends
38 a single datagram and a single BIO_read() call receives a single datagram. If
39 the size of the buffer passed to BIO_read() is inadequate, the datagram is
42 For a memory-based BIO which provides datagram semantics identical to those of
70 subsequent call to BIO_write() being set to the source address of the datagram
134 The peer address of the datagram last received by a call to BIO_read().
171 overhead which should typically be added to a datagram payload size in order to
173 datagram. In most cases, the maximum datagram payload size which can be
[all …]
H A DSSL_inject_net_dgram.pod5 SSL_inject_net_dgram - inject a datagram as though received from the network
18 This function can be used to inject a datagram payload to a QUIC connection SSL
23 I<buf> is required and must point to a datagram payload to inject. I<buf_len> is
30 OpenSSL, the packet will be processed as though the received datagram had the
H A DBIO_s_mem.pod35 BIO_s_dgram_mem() is a memory BIO that respects datagram semantics. A single
36 call to L<BIO_write(3)> will write a single datagram to the memory BIO. A
37 subsequent call to L<BIO_read(3)> will read the data in that datagram. The
41 datagram. If a L<BIO_read(3)> call supplies a read buffer that is smaller than
42 the size of the datagram, then the read buffer will be completely filled and the
43 remaining data from the datagram will be discarded.
45 It is not possible to write a zero length datagram. Calling L<BIO_write(3)> in
49 true). A datagram mem BIO will never return true from L<BIO_eof(3)>.
80 Calling this macro will fail for datagram mem BIOs.
H A DDTLSv1_listen.pod35 If DTLS is used over UDP (or any datagram based protocol that does not validate
70 datagram on an unconnected socket. If the socket is not connected, it can
75 redirected to it by sending a datagram to the socket in question. This does not
93 B<only> supports ClientHellos that fit inside a single datagram.
H A DSSL_set_fd.pod26 When used on a QUIC connection SSL object, a B<datagram BIO> is automatically
H A DBIO_sendmmsg.pod65 on a per-datagram basis, and the source address of received datagrams to be
72 datagrams to be specified on a per-datagram basis, and the destination address
/src/tools/test/stress2/misc/
H A Ddatagram.sh39 cat > datagram.c <<EOF
87 mycc -o datagram -Wall -Wextra -O2 -g datagram.c || exit 1
88 rm datagram.c
90 ./datagram &
95 rm -f datagram /tmp/datagram.socket
/src/crypto/openssl/doc/designs/quic-design/
H A Dglossary.md33 serialize another QUIC packet into the same datagram as one or more previous
35 already serialized into to the same datagram.
40 datagram. Essentially, this is the room we have left for another packet payload.
50 **DGRAM:** (UDP) datagram.
105 a datagram. The MDPL may vary based on both local source IP and destination IP
109 datagram has a minimum size of a certain number of bytes. This does not need to
111 the final packet added to a datagram in this case.
116 already encoded into the datagram.
248 **RTT:** Round trip time. Time for a datagram to reach a given peer and a reply
307 decide how to spend the space available in a datagram.
H A Dtx-packetiser.md214 packet in a datagram. The MDPL may vary based on both local source IP and
227 another QUIC packet into the same datagram as one or more previous
229 packets already serialized into to the same datagram.
233 more previous QUIC packets and placed into the same datagram. Essentially,
240 - Minimum Datagram Length (MinDPL): In some cases we must ensure a datagram
243 to the final packet added to a datagram in this case.
248 we have already encoded into the datagram.
580 A datagram must always be padded to at least 1200 bytes if it contains an
581 Initial packet. (If there are multiple packets in the datagram, the padding
615 The TX packetiser is requested to generate a datagram via the following call:
[all …]
H A Dquic-fault-injector.md89 Multiple packets may be held within a single datagram, and each packet may
136 packet in a single datagram. Fault Injector based tests may need to inject
151 requires a modification to be made, that will occur prior to the datagram being
382 * To be called from a datagram_listener callback. The datagram buffer is over
H A Dquic-io-arch.md46 passed to the QUIC implementation be configured to support datagram semantics
50 datagram semantics. These changes are not minor, but there is no way around this
102 - The fact that a socket is writeable does not necessarily mean that a datagram
199 need to change to using network BIOs with datagram semantics. For applications
272 substantially reworked to switch from bytestream semantics to datagram
342 memory buffer with datagram semantics, is to be supported as part of MVP. This
H A Dquic-ackm.md194 This must be called whenever a datagram is received. A datagram may contain
212 `ossl_ackm_on_rx_datagram` was called for the datagram containing the packet.
H A Ddgram-api.md300 one datagram where BIO_dgram uses `readmmsg` internally and queues the returned
382 - Application can generate one datagram at a time and still get the advantages
432 of any internal BIO state other than maybe the last datagram source/destination
435 initialised and filled using `recvmmsg`, then one datagram is popped from it.
/src/crypto/openssl/test/
H A Ddefault-recordpadding.cnf15 # always pad during datagram encryption
/src/lib/libc/net/
H A Dprotocols11 st2 5 ST2 # ST2 datagram mode (RFC 1819) (officially ``ST'')
23 udp 17 UDP # user datagram protocol
33 rdp 27 RDP # "reliable datagram" protocol
/src/tools/regression/sockets/unix_cmsg/
H A DREADME7 sockets). There are tests for stream and datagram sockets.
125 Server creates datagram socket and sets the LOCAL_CREDS socket option
132 Server creates datagram socket and sets the LOCAL_CREDS socket option
/src/crypto/openssl/doc/man7/
H A Dopenssl-quic.pod135 L<SSL_set0_wbio(3)> function as before, but must now receive a BIO with datagram
148 L<BIO_s_dgram_pair(3)> provides BIO pair-like functionality but with datagram
155 datagram semantics. Unlike L<BIO_s_dgram_pair(3)>, it is unidirectional.
362 datagram socket is created instead of a normal TCP socket.
370 of such a buffer is incompatible with QUIC as QUIC requires datagram semantics
380 L<BIO_s_dgram_pair(3)> instead, which has the necessary datagram semantics. You
382 and to use datagram semantics when interacting with the L<BIO_s_dgram_pair(3)>
390 Changes needed: The custom BIO must be re-architected to have datagram
723 provides datagram semantics.
733 This is a new BIO API which can be implemented by BIOs which implement datagram
[all …]
H A Dossl-guide-quic-introduction.pod61 Future versions of OpenSSL will offer support for the QUIC datagram extension,
149 (usually achieved by using TCP). However QUIC assumes "datagram" type semantics
/src/share/doc/smm/18.net/
H A Dspell.ok164 datagram
/src/share/doc/psd/05.sysman/
H A Dspell.ok117 datagram
/src/share/doc/psd/21.ipc/
H A Dspell.ok142 datagram
/src/crypto/openssh/
H A Dchannels.h198 int datagram; member
/src/share/examples/ppp/
H A Dppp.conf.sample271 set filter alive 5 deny udp src eq 138 # NetBIOS datagram service
274 set filter alive 8 deny udp dst eq 138 # NetBIOS datagram service
284 set filter dial 3 deny udp src eq 138 # NetBIOS datagram service
287 set filter dial 6 deny udp dst eq 138 # NetBIOS datagram service
/src/crypto/openssl/doc/designs/ddd/
H A DREPORT.md241 since datagram semantics on the network channel need to be maintained.
248 provides a bidirectional memory buffer BIO with datagram semantics.

12