Searched refs:datagrams (Results 1 – 25 of 28) sorted by relevance
12
49 datagrams from the specified peer. Any other socket is an unconnected socket and50 can receive datagrams from any host.66 calls BIO_read(), any host on the network may cause future datagrams written to157 Fragment mode, in which datagrams will be set with the IP Don't Fragment (DF)178 supported by the applicable underlying network layer. Use of datagrams of this198 peek mode is enabled, calls to L<BIO_read(3)> read datagrams from the underlying
71 receive datagrams from any host on the network, which will cause subsequent72 outgoing datagrams transmitted by DTLS to be transmitted to that host. In other
73 <received-datagrams>0</received-datagrams>266 <received-datagrams>0</received-datagrams>
69 <received-datagrams>0</received-datagrams>
69 <received-datagrams>2</received-datagrams>
64 <received-datagrams>0</received-datagrams>
53 <received-datagrams>0</received-datagrams>
65 <received-datagrams>1</received-datagrams>
87 <received-datagrams>0</received-datagrams>
1542 int error, datagrams; in linux_sendmmsg() local1548 datagrams = 0; in linux_sendmmsg()1549 while (datagrams < args->vlen) { in linux_sendmmsg()1560 ++datagrams; in linux_sendmmsg()1563 td->td_retval[0] = datagrams; in linux_sendmmsg()1961 int error, datagrams; in linux_recvmmsg_common() local1966 datagrams = 0; in linux_recvmmsg_common()1967 while (datagrams < vlen) { in linux_recvmmsg_common()1978 ++datagrams; in linux_recvmmsg_common()2000 td->td_retval[0] = datagrams; in linux_recvmmsg_common()
120 datagrams
118 datagrams
472 configure network routers so that they discard datagrams from "outside"
1713 IP Multicast tunnel, you cannot filter out the datagrams using the