Searched refs:datagram (Results 1 – 25 of 27) sorted by relevance
12
39 cat > datagram.c <<EOF87 mycc -o datagram -Wall -Wextra -O2 -g datagram.c || exit 188 rm datagram.c90 ./datagram &95 rm -f datagram /tmp/datagram.socket
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.
11 st2 5 ST2 # ST2 datagram mode (RFC 1819) (officially ``ST'')23 udp 17 UDP # user datagram protocol33 rdp 27 RDP # "reliable datagram" protocol
7 sockets). There are tests for stream and datagram sockets.125 Server creates datagram socket and sets the LOCAL_CREDS socket option132 Server creates datagram socket and sets the LOCAL_CREDS socket option
164 datagram
117 datagram
142 datagram
198 int datagram; member
2129 if (!pty_zeroread && c->input_filter == NULL && !c->datagram) { in channel_handle_rfd()2180 } else if (c->datagram) { in channel_handle_rfd()2213 } else if (c->datagram) { in channel_handle_wfd()2222 if (c->datagram) { in channel_handle_wfd()2976 if (c->datagram) { in channel_output_poll_input_open()3424 if (c->datagram) in channel_input_data()3459 if (c->datagram) { in channel_input_data()
526 c->datagram = 1; in server_request_tun()
259 with datagram boundaries intact between endpoints equipped with305 The "packet data" field consists of the IPv4/IPv6 datagram itself
1864 c->datagram = 1; in client_request_tun_fwd()
271 set filter alive 5 deny udp src eq 138 # NetBIOS datagram service274 set filter alive 8 deny udp dst eq 138 # NetBIOS datagram service284 set filter dial 3 deny udp src eq 138 # NetBIOS datagram service287 set filter dial 6 deny udp dst eq 138 # NetBIOS datagram service
215 packets when using datagram based transports.626 * kdc/kdc.8: document max-kdc-datagram-reply-length639 a datagram reply or not642 a datagram reply and the datagram reply length limit is reached.647 * kdc/config.c: check for [kdc]max-kdc-datagram-reply-length
502 * lib/krb5/changepw.c: use a datagram socket and remove the
854 * lib/kadm5/log.c (kadm5_log_flush): send a unix domain datagram
439 Enhancements over the previous release are: support for datagram (UDP
366 do not work for datagram (UDP) services. More seriously, client user1005 get the client IP address in case of datagram-oriented services, and
1053 # UNIX Specification, so that we can check whether a datagram
867 # UNIX Specification, so that we can check whether a datagram
657 Don't build support for datagram based BIOs.
1209 /* only applies to datagram connections */
1708 - print-ip.c: Print the inner ip datagram of ip-in-ip encapsulated packets.
819 corresponding (datagram) socket.