| /freebsd/lib/libc/rpc/ |
| H A D | netconfig.5 | 8 .Nd network configuration data base 26 .Bl -tag -width network_id 32 .Bl -tag -width tpi_cots_ord -offset indent 36 Connection-oriented transport 38 Connection-oriented, ordered transport. 44 .Dq Li - ) , 46 .Bl -tag -width b -offset indent 48 The network represented by this entry is broadcast capable. 59 .Bl -tag -width loopback -offset indent 89 network type. [all …]
|
| H A D | rpc_svc_create.3 | 2 .\" Copyright (c) 1988 Sun Microsystems, Inc. - All Rights Reserved. 43 calls on servers across the network. 53 .Bl -tag -width XXXXX 66 .Bl -tag -width SVCGET_XID 107 (indicating normal server behavior - an 191 since connectionless-based RPC 199 connection-oriented transport. 262 .Bd -literal 264 struct netbuf addr; /* network address, see rpc(3) */ 271 for connection-oriented transports. [all …]
|
| H A D | rpc.3 | 17 calls on other machines across a network. 31 Some of the high-level 47 .Bl -tag -width datagram_v 69 except that it chooses only the connection oriented transports 89 except that it chooses only the connection oriented datagram transports 119 .Bd -literal 131 .Bd -literal 158 .Bd -literal 176 char *cl_netid; /* network identifier */ 181 .Bd -literal [all …]
|
| H A D | rpc_clnt_create.3 | 2 .\" Copyright (c) 1988 Sun Microsystems, Inc. - All Rights Reserved. 61 calls on other machines across the network. 69 .Bl -tag -width YYYYYYY 79 For both connectionless and connection-oriented transports, 83 .Bl -column "CLSET_FD_NCLOSE" "struct timeval *" "set total timeout" 101 .Bl -column CLSET_FD_NCLOSE "struct timeval *" 113 .Bl -column CLSET_RETRY_TIMEOUT "struct timeval *" "set total timeout" 278 .Fn auth_destroy "clnt->cl_auth" 371 and it is connection-oriented, it is assumed that the file descriptor 407 Depending upon the type of the transport (connection-oriented [all …]
|
| /freebsd/include/ |
| H A D | netconfig.h | 3 /*- 4 * SPDX-License-Identifier: BSD-2-Clause 43 char *nc_netid; /* Network ID */ 48 char *nc_device; /* Network device pathname */ 63 #define NC_TPI_COTS 2 /* Connection oriented transport */ 64 #define NC_TPI_COTS_ORD 3 /* Connection oriented, ordered transport */ 77 #define NC_NOPROTOFMLY "-" 105 #define NC_NOPROTO "-"
|
| /freebsd/share/doc/smm/18.net/ |
| H A D | 6.t | 35 The internal structure of the network system is divided into 90 be described in detail later. A pointer to a protocol-specific 125 #define SS_NBIO 0x100 /* non-blocking ops */ 136 set with \fIfcntl\fP. ``Non-blocking'' I/O implies that 151 super-user. Only privileged sockets may 153 or use ``raw'' sockets to access lower levels of the network. 184 (assuming non-blocking I/O has not been specified).* 186 * The low-water mark is always presumed to be 0 205 Stream-oriented sockets queue data with no addresses, headers 210 Record-oriented sockets, including datagram sockets, [all …]
|
| H A D | b.t | 36 to a lower-level protocol. Raw sockets are intended for knowledgeable 46 (possibly) augmented by protocol-specific processing routines. 75 detail shortly. If any protocol-specific information is required, 78 Protocol-specific options for transmission in outgoing packets 81 A raw socket interface is datagram oriented. That is, each send 94 pattern matching scheme. Each network interface or protocol 117 If the protocol number in the socket is non-zero, then it agrees 128 control block and packet header (as constructed by the network 137 it is delivered to the appropriate network interface. The
|
| /freebsd/share/doc/smm/06.nfs/ |
| H A D | 1.t | 38 interfaces to the network using 42 oriented protocols and timeout/retransmit support for datagram sockets on 44 For connection oriented transport protocols, 50 will be improved by running nfsiod daemons that perform read-aheads 51 and write-behinds. 66 using connection oriented transport protocols and passes the new sockets down 74 mount, ranging from an unresponsive NFS server (crashed, network partitioned 80 require the \fB-n\fR option to enable non-root mount request servicing. 99 \fB-b\fR 105 \fBmount -a\fR [all …]
|
| /freebsd/share/doc/psd/05.sysman/ |
| H A D | 2.3.t | 42 using the Xerox Network Systems protocols. 62 #define SOCK_RDM 4 /* reliably-delivered message */ 65 The SOCK_DGRAM type models the semantics of datagrams in network communication: 66 messages may be lost or duplicated and may arrive out-of-order. 70 arrive unduplicated and in-order, the sender is notified if 74 The SOCK_STREAM type models connection-based virtual circuits: two-way 77 The SOCK_SEQPACKET type models a connection-based, 78 full-duplex, reliable, sequenced packet exchange; 80 duplicated or presented out-of-order. 82 out-of-band transmission to send out-of-band data. [all …]
|
| /freebsd/contrib/tcp_wrappers/ |
| H A D | clean_exit.c | 3 * instead of exit() when for some reason the real network daemon will not or 4 * cannot be run. Reason: in the case of a datagram-oriented service we must 5 * discard the not-yet received data from the client. Otherwise, inetd will 22 /* clean_exit - clean up and exit */ 28 * In case of unconnected protocols we must eat up the not-yet received in clean_exit() 32 if (request->sink) in clean_exit() 33 request->sink(request->fd); in clean_exit()
|
| H A D | tcpd.8 | 3 tcpd \- access control facility for internet services 9 that have a one-to-one mapping onto executable files. 11 The program supports both 4.3BSD-style sockets and System V.4-style 21 Optional features are: pattern-based access control, client username 24 that pretend to have someone elses network address. 39 matching. The access-control software provides hooks for the execution 49 verifies the client host name that is returned by the address->name DNS 51 name->address DNS server. If any discrepancy is detected, 56 If the sources are compiled with -DPARANOID, 64 disables source-routing socket options on every connection that it [all …]
|
| H A D | hosts_options.5 | 3 hosts_options \- host access control language extensions 8 PROCESS_OPTIONS compile-time option. 66 spawn (/some/where/safe_finger -l @%h | /usr/ucb/mail root) & 95 To run /some/other/in.telnetd without polluting its command-line 106 .SH NETWORK OPTIONS 114 Specifies how long the kernel will try to deliver not-yet delivered 121 RFC 931 (IDENT, etc.) -compliant daemon, and may cause noticeable 122 delays with connections from non-UNIX clients. The timeout period is 123 optional. If no timeout is specified a compile-time defined default 130 carriage-return newline, and %<letter> sequences are expanded (see [all …]
|
| H A D | hosts_access.5 | 3 hosts_access \- format of host access control files 13 program build time by building with -DPROCESS_OPTIONS. 16 network daemon process, and \fIclient\fR is the name and/or address of 17 a host requesting service. Network daemon process names are specified 31 A non-existing access control file is treated as if it were an empty 80 Eind\%hoven University network (131.155.x.x). 116 network address will be unavailable when the software cannot figure out 117 what type of network it is talking to. 122 network address will be unavailable when the software cannot figure out 123 what type of network it is talking to. [all …]
|
| /freebsd/share/man/man4/ |
| H A D | ntb_transport.4 | 2 .\" Copyright (c) 2016-2019 Alexander Motin <mav@FreeBSD.org> 31 .Nd Packet-oriented transport for Non-Transparent Bridges 35 .Bd -ragged -offset indent 42 .Bd -literal -offset indent 48 .Bl -ohang 55 while too big buffers makes no much sense for low latency network interface. 66 Non-zero value enables compact version of scratchpad protocol, using half 81 network interface, but other consumers may also be developed using KPI. 88 .Bl -bullet -compact 104 .An -nosplit
|
| H A D | capsicum.4 | 42 This approach achieves many of the benefits of least-privilege operation, while 44 with an adoption path for capability-oriented design. 59 .Bl -tag -width indent 74 can be used to query process-local information such as address space layout, 75 but also to monitor a system’s network connections. 117 .Bl -tag -width indent 133 .Bl -tag -width indent 144 .Bl -tag -width indent 150 on files specified on a command line or establishing network connections. 179 .An -nosplit
|
| /freebsd/share/doc/papers/sysperf/ |
| H A D | 7.t | 34 the distributed system spent 10-20% more time in the kernel than 73 The buffer cache read-ahead trace package was based 84 \s+2References\s-2 88 ``A User-Process Oriented Performance Study of Ethernet Networking Under 97 June 1985, pp. 507-517. 100 ``Toward an Internet Standard for Subnetting,'' RFC-940, 101 Network Information Center, SRI International, 116 pp 228-236, June 1984. 121 pp 237-252, June 1984. 126 pp 519-531, June 1985. [all …]
|
| /freebsd/lib/libc/posix1e/ |
| H A D | mac_get.3 | 5 .\" Costello at Safeport Network Services and NAI Labs, the Security 6 .\" Research Division of Network Associates, Inc. under DARPA/SPAWAR 7 .\" contract N66001-01-C-8035 ("CBOSS"), as part of the DARPA CHATS 75 on-disk node acting as a rendezvous for the socket. 81 be cached when a connection-oriented protocol instance is first set up, 99 .Bl -tag -width Er
|
| /freebsd/libexec/fingerd/ |
| H A D | fingerd.8 | 48 at several network sites. 50 human-oriented status report on either the system at the moment 103 .Bl -tag -width indent 108 will not attempt any network-related operations on
|
| /freebsd/share/doc/psd/26.rpcrfc/ |
| H A D | rpc.rfc.ms | 2 .\" Must use -- tbl -- with this one 21 It has been designated RFC1050 by the ARPA Network 40 clients, and versions. A server is a piece of software where network 41 services are implemented. A network service is a collection of one 45 \fIPort Mapper Program Protocol\fP\, below, for an example). Network 50 For example, a network file service may be composed of two programs. 51 One program may deal with high-level applications such as file system 52 access control and locking. The other may deal with low-level file 54 the network file service would call the procedures associated with 62 procedure in some well-specified location (such as a result [all …]
|
| /freebsd/contrib/libarchive/ |
| H A D | README.md | 6 command-line tools that use the libarchive library. 23 * **tar**: the 'bsdtar' program is a full-featured 'tar' implementation built on libarchive 26 * **unzip**: the 'bsdunzip' program is a simple replacement tool for Info-ZIP's unzip 31 The top-level directory contains the following information files: 33 * **NEWS** - highlights of recent changes 34 * **COPYING** - what you can do with this 35 * **INSTALL** - installation instructions 36 * **README** - this file 37 * **CMakeLists.txt** - input for "cmake" build tool, see INSTALL 38 * **configure** - configuration script, see INSTALL for details. If your copy of the source lacks … [all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/misc/ |
| H A D | fsl,qoriq-mc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/misc/fsl,qoriq-mc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Frank Li <Frank.Li@nxp.com> 13 The Freescale Management Complex (fsl-mc) is a hardware resource 15 network-oriented packet processing applications. After the fsl-mc 19 such as network interfaces, crypto accelerator instances, L2 switches, 22 For an overview of the DPAA2 architecture and fsl-mc bus see: 26 same hardware "isolation context" and a 10-bit value called an ICID [all …]
|
| H A D | fsl,qoriq-mc.txt | 3 The Freescale Management Complex (fsl-mc) is a hardware resource 5 network-oriented packet processing applications. After the fsl-mc 9 such as network interfaces, crypto accelerator instances, L2 switches, 12 For an overview of the DPAA2 architecture and fsl-mc bus see: 16 same hardware "isolation context" and a 10-bit value called an ICID 21 between ICIDs and IOMMUs, so an iommu-map property is used to define 28 For arm-smmu binding, see: 32 The msi-map property is used to associate the devices with both the ITS 36 Documentation/devicetree/bindings/interrupt-controller/msi.txt. 39 Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml. [all …]
|
| /freebsd/share/doc/papers/fsinterface/ |
| H A D | fsinterface.ms | 32 \s-1UNIX\s0\\$1\(dg 34 \(dg \s-1UNIX\s0 is a registered trademark of AT&T. 52 As network or remote filesystems have been implemented for 66 Each design attempts to isolate filesystem-dependent details 92 As network communications and workstation environments 97 systems have designed and built network file systems 101 Examples include Sun's Network File System, NFS [Sandberg85], 102 AT&T's recently-announced Remote File Sharing, RFS [Rifkin86], 106 for internal use, notably the network filesystem in the Eighth Edition 108 system [Weinberger84] and two different filesystems used at Carnegie-Mellon [all …]
|
| /freebsd/share/doc/psd/21.ipc/ |
| H A D | 2.t | 61 the UNIX domain, for on-system communication; 118 These sockets are normally datagram oriented, though their 130 Sequenced-packet sockets allow the user to manipulate the 180 create a datagram socket for on-machine use the call might 315 binds a socket to a well-known address associated with the service 364 the network resulted in transmissions being lost. 378 These operational errors can occur either because the network 379 or host is unknown (no route to the network or host is present), 382 is not sufficient to distinguish a network being down from a 384 indicates the entire network is unreachable. [all …]
|
| /freebsd/share/doc/smm/01.setup/ |
| H A D | 5.t | 33 .Sh 1 "Network setup" 38 serial lines to local area network controllers 39 for the Ethernet. Network services are split between the 43 \*(4B also supports the Xerox Network Systems (NS) protocols. 55 In either case, include the pseudo-devices 58 The ``pty'' pseudo-device forces the pseudo terminal device driver 61 while the ``loop'' pseudo-device forces inclusion of the software loopback 63 The loop driver is used in network testing 66 If you are planning to use the Internet network facilities on a 10Mb/s 67 Ethernet, the pseudo-device ``ether'' should also be included [all …]
|