| /freebsd/share/man/man4/ |
| H A D | ng_ppp.4 | 1 .\" Copyright (c) 1996-1999 Whistle Communications, Inc.
19 .\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
41 .Nd PPP protocol netgraph node type
48 node type performs multiplexing for the PPP protocol.
49 It handles only packets that contain data, and forwards protocol negotiation
51 user-land daemon).
54 user-land implementations.
56 multi-link PPP, Van Jacobson compression, PPP compression, PPP
58 A single PPP node corresponds to one PPP multi-link bundle.
67 hook which is used to handle any protocol not directly supported
[all …]
|
| H A D | iicbus.4 | 41 system provides a uniform, modular and architecture-independent
49 easy way to connect a CPU to peripheral chips in a TV-set.
66 In the I2C protocol
71 As mentioned before, the IC bus is a Multi-MASTER BUS.
77 .Bl -column "Device drivers" -compact
84 The I2C protocol may be implemented by hardware or software.
89 8-bit characters they write to the bus according to the I2C protocol.
92 bidirectional communications, thanks to the multi-master capabilities of the
93 I2C protocol.
97 .Bl -column "Interface drivers" -compact
[all …]
|
| H A D | sctp.4 | 32 .Nd Internet Stream Control Transmission Protocol
47 protocol provides reliable, flow-controlled, two-way
49 It is a message oriented protocol and can
57 Internet address format and, in addition, provides a per-host
71 protocol are either
105 third leg of the four-way handshake.
116 protocol directly supports multi-homing.
129 transport protocol is also multi-streamed.
130 Multi-streaming refers to the ability to send sub-ordered flows of
142 transport protocol also provides a unordered service as well.
[all …]
|
| /freebsd/sys/contrib/device-tree/src/arm/aspeed/ |
| H A D | aspeed-bmc-facebook-yosemitev2.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 /dts-v1/;
4 #include "aspeed-g5.dtsi"
5 #include <dt-bindings/i2c/i2c.h>
9 compatible = "facebook,yosemitev2-bmc", "aspeed,ast2500";
14 stdout-path = &uart5;
21 iio-hwmon {
23 compatible = "iio-hwmon";
24 io-channels = <&adc 0> , <&adc 1> , <&adc 2> , <&adc 3> ,
35 m25p,fast-read;
[all …]
|
| H A D | aspeed-bmc-facebook-greatlakes.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later
4 /dts-v1/;
5 #include "aspeed-g6.dtsi"
6 #include <dt-bindings/gpio/aspeed-gpio.h>
7 #include <dt-bindings/leds/leds-pca955x.h>
8 #include <dt-bindings/i2c/i2c.h>
12 compatible = "facebook,greatlakes-bmc", "aspeed,ast2600";
23 iio-hwmon {
24 compatible = "iio-hwmon";
25 io-channels = <&adc0 0>, <&adc0 1>, <&adc0 2>, <&adc0 3>,
[all …]
|
| /freebsd/crypto/openssl/test/radix/ |
| H A D | README.md | 5 -------
7 This directory contains the RADIX test framework, which is a six-dimension
8 script-driven facility intended to facilitate execution of
10 - multi-stream
11 - multi-client
12 - multi-server
13 - multi-thread
14 - multi-process (in future)
15 - multi-node (in future)
17 test vignettes for network protocol testing applications. While it is currently
[all …]
|
| /freebsd/contrib/tcpdump/ |
| H A D | ppp.h | 2 * Point to Point Protocol (PPP) RFC1331
22 #define PPP_PPPD_IN 0x00 /* non-standard for DLT_PPP_PPPD */
23 #define PPP_PPPD_OUT 0x01 /* non-standard for DLT_PPP_PPPD */
25 /* Protocol numbers */
35 #define PPP_STII 0x0033 /* Stream Protocol (ST-II) */
37 #define PPP_ML 0x003d /* Multi-Link PPP */
47 #define PPP_IPCP 0x8021 /* IP Control Protocol */
48 #define PPP_OSICP 0x8023 /* OSI Network Layer Control Protocol */
49 #define PPP_NSCP 0x8025 /* Xerox NS IDP Control Protocol */
50 #define PPP_DECNETCP 0x8027 /* DECnet Control Protocol */
[all …]
|
| H A D | smb.h | 2 * Copyright (C) Andrew Tridgell 1995-1999
5 * BSD-style license that accompanies tcpdump or the GNU GPL version 2
35 #define SMBnegprot 0x72 /* negotiate protocol */
47 #define SMBsendstrt 0xD5 /* send start of multi-block message */
48 #define SMBsendend 0xD6 /* send end of multi-block message */
49 #define SMBsendtxt 0xD7 /* send text of multi-block message */
51 /* Core+ protocol */
59 /* dos extended protocol */
70 #define SMBtrans 0x25 /* transaction - name, bytes in/out */
86 /* Extended 2.0 protocol */
[all …]
|
| H A D | CONTRIBUTING.md | 7 code execution etc) please send an e-mail to security@tcpdump.org, do not use
10 To report a non-security problem (failure to compile, incorrect output in the
11 protocol printout, missing support for a particular protocol etc) please check
15 libpcap. If it does (and it is not a security-related problem, otherwise see
17 [bug tracker](https://github.com/the-tcpdump-group/tcpdump/issues)
21 * tcpdump and libpcap version (`tcpdump --version`)
23 (`uname -a`, compiler name and version, CPU type etc.)
33 [subscribe to the mailing list](https://www.tcpdump.org/#mailing-lists)
42 2) [Fork](https://help.github.com/articles/fork-a-repo/) the Tcpdump
43 [repository](https://github.com/the-tcpdump-group/tcpdump).
[all …]
|
| /freebsd/contrib/wpa/hostapd/ |
| H A D | README-MULTI-AP | 1 hostapd, wpa_supplicant and the Multi-AP Specification
5 support the Multi-AP Specification.
7 Introduction to Multi-AP
8 ------------------------
10 The Wi-Fi Alliance Multi-AP Specification is the technical specification for
11 Wi-Fi CERTIFIED EasyMesh(TM) [1], the Wi-Fi Alliance® certification program for
12 Multi-AP. It defines control protocols between Wi-Fi® access points (APs) to
17 Most of the Multi-AP specification falls outside of the scope of
19 summarized below. The rest of the protocol must be implemented by a separate
25 - the WPS onboarding process;
[all …]
|
| /freebsd/share/doc/smm/18.net/ |
| H A D | 7.t | 31 .\".ds RH "Socket/protocol interface
33 \s+2Socket/protocol interface\s0
37 protocol switch table. The following requests to a protocol
41 #define PRU_ATTACH 0 /* attach protocol */
42 #define PRU_DETACH 1 /* detach protocol */
52 #define PRU_CONTROL 11 /* control operations on protocol */
73 The address \fIaddr\fP is supplied for address-oriented requests
76 chain containing user-specified capabilities (see the \fIsendmsg\fP
77 and \fIrecvmsg\fP system calls). The protocol is responsible for
79 A non-zero return value gives a
[all …]
|
| /freebsd/sys/net/ |
| H A D | if_types.h | 1 /*-
2 * SPDX-License-Identifier: BSD-3-Clause
41 * http://www.iana.org/assignments/smi-numbers
46 IFT_1822 = 0x2, /* old-style arpanet imp */
63 IFT_CEPT = 0x13, /* E1 - european T1 */
78 IFT_PARA = 0x22, /* parallel-port */
111 IFT_G703AT2MB = 0x43, /* Obsolete see DS1-MIB */
121 IFT_LAPD = 0x4d, /* Link Access Protocol D */
127 IFT_BSC = 0x53, /* Bisynchronous Protocol */
128 IFT_ASYNC = 0x54, /* Asynchronous Protocol */
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | openssl-quic.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OPENSSL-QUIC 7ossl"
58 .TH OPENSSL-QUIC 7ossl 2025-09-30 3.5.4 OpenSSL
64 openssl\-quic \- OpenSSL QUIC
67 OpenSSL 3.2 and later features support for the QUIC transport protocol.
69 This man page describes how to let applications use the QUIC protocol using the
72 The QUIC protocol maps to the standard SSL API. A QUIC connection is represented
74 are needed to existing applications which use libssl API to bring QUIC protocol
82 Default stream mode versus multi-stream mode for clients;
84 The changes to existing libssl APIs which are driven by QUIC-related
[all …]
|
| H A D | ossl-guide-quic-multi-stream.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OSSL-GUIDE-QUIC-MULTI-STREAM 7ossl"
58 .TH OSSL-GUIDE-QUIC-MULTI-STREAM 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-quic\-multi\-stream
65 \&\- OpenSSL Guide: Writing a simple multi\-stream QUIC client
69 QUIC multi-stream application. It assumes a basic understanding of QUIC and how
70 it is used in OpenSSL. See \fBossl\-guide\-quic\-introduction\fR\|(7) and
71 \&\fBossl\-guide\-quic\-client\-block\fR\|(7).
74 In a QUIC multi-stream application we separate out the concepts of a QUIC
98 (see \fBossl\-guide\-libraries\-introduction\fR\|(7)). In particular most OpenSSL
[all …]
|
| /freebsd/crypto/openssh/ |
| H A D | PROTOCOL.mux | 1 This document describes the multiplexing protocol used by ssh(1)'s
2 ControlMaster connection-sharing.
7 simple packetised protocol, where each message is proceeded with
37 the multiplexing protocol and start proxying SSH connection protocol
39 speak a significant subset of the SSH protocol, but in return is able
40 to access basically the full suite of connection protocol features.
52 uint32 protocol version
57 The current version of the mux protocol is 4. A client should refuse
58 to connect to a master that speaks an unsupported protocol version.
109 non-multiplexed ssh(1) connection. Two additional cases that the
[all …]
|
| H A D | PROTOCOL.u2f | 4 ----------
6 U2F is an open standard for two-factor authentication hardware, widely
9 cheapest way for users to achieve hardware-backed credential storage.
11 The U2F protocol however cannot be trivially used as an SSH protocol key
26 which takes an application ID - a URL-like string, typically "ssh:"
30 the hardware-backed private key, some flags and signed attestation
35 in conjunction with a small per-device secret that is unique to the
36 hardware, thus requiring little on-device storage for an effectively
39 primarily use ECDSA signatures in the NIST-P256 field, though the FIDO2
42 Use of U2F security keys does not automatically imply multi-factor
[all …]
|
| /freebsd/contrib/file/magic/Magdir/ |
| H A D | epoc | 2 #------------------------------------------------------------------------------
8 #------------------------------------------------------------------------------
11 !:mime application/x-epoc-font
13 !:mime application/x-epoc-pdriver
15 !:mime application/x-epoc-clipboard
16 >4 lelong 0x10000042 multi-bitmap image
17 !:mime image/x-epoc-mbm
20 !:mime image/x-epoc-record
22 !:mime image/x-epoc-sketch
24 !:mime application/x-epoc-voice
[all …]
|
| /freebsd/sbin/routed/ |
| H A D | routed.8 | 58 It uses Routing Information Protocol, RIPv1 (RFC\ 1058),
60 and Internet Router Discovery Protocol (RFC 1256)
62 The RIPv1 protocol is based on the reference
72 for Routing Information Protocol packets.
91 deletes all pre-existing
92 non-static routes in kernel table.
94 included in RIP responses if they have a valid RIP -hopcount
134 .Em split-horizon .
174 .Em black-holes .
181 age of any relevant Router Discovery Protocol default routes.
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ossl-guide-quic-multi-stream.pod | 6 demos/guide/quic-multi-stream.c
12 ossl-guide-quic-multi-stream
13 - OpenSSL Guide: Writing a simple multi-stream QUIC client
18 QUIC multi-stream application. It assumes a basic understanding of QUIC and how
19 it is used in OpenSSL. See L<ossl-guide-quic-introduction(7)> and
20 L<ossl-guide-quic-client-block(7)>.
24 In a QUIC multi-stream application we separate out the concepts of a QUIC
48 (see L<ossl-guide-libraries-introduction(7)>). In particular most OpenSSL
64 (by default) the default stream will be a client-initiated bi-directional
67 stream (whether it is bi-directional or uni-directional).
[all …]
|
| H A D | openssl-quic.pod | 5 openssl-quic - OpenSSL QUIC
9 OpenSSL 3.2 and later features support for the QUIC transport protocol.
11 This man page describes how to let applications use the QUIC protocol using the
14 The QUIC protocol maps to the standard SSL API. A QUIC connection is represented
16 are needed to existing applications which use libssl API to bring QUIC protocol
28 Default stream mode versus multi-stream mode for clients;
32 The changes to existing libssl APIs which are driven by QUIC-related
46 New, QUIC-specific APIs.
53 stream mode, which is intended to provide compatibility with existing non-QUIC
57 client-initiated or server-initiated from a QUIC perspective depends on whether
[all …]
|
| /freebsd/usr.sbin/ppp/ |
| H A D | ppp.8 | 31 .Nd Point to Point Protocol (a.k.a. user-ppp)
99 .Bl -tag -width XXX -offset XXX
141 exits with a non-zero result.
161 .Dq force-scripts
176 As pipes are not bi-directional, ppp will redirect all writes to descriptor
186 .Dq force-scripts
195 This is a no-op, and gives the same behaviour as if none of the above
213 .Bl -diag
231 .It Supports on-demand dialup capability.
243 mode (direct-dial mode) also automatically dials and establishes the
[all …]
|
| /freebsd/usr.sbin/rpc.yppasswdd/ |
| H A D | rpc.yppasswdd.8 | 62 is an RPC-based server that accepts incoming password change requests,
120 also allows the super-user on the NIS master server to perform more
122 The super-user can modify
125 receives a request from the super-user, the password authentication
129 flag, the super-user can even add new entries to the maps using
131 Again, this only applies to the super-user on the NIS
140 .Bl -tag -width indent
180 The compiled-in default path is
188 The super-user on the
196 is started with this flag, it will also allow the super-user to add new
[all …]
|
| /freebsd/usr.sbin/inetd/ |
| H A D | inetd.8 | 34 .Dq super-server
70 .Bl -tag -width indent
87 .Em protocol
92 a TCP-based service would need two entries,
96 .Em protocol
101 .Em protocol
106 May be overridden on a per-service basis with the
107 "max-connections-per-ip-per-minute" parameter.
112 May be overridden on a per-service basis with the "max-child"
128 May be overridden on a per-service basis with the "max-child-per-ip"
[all …]
|
| /freebsd/sys/contrib/edk2/Include/Library/ |
| H A D | DevicePathLib.h | 7 Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
8 SPDX-License-Identifier: BSD-2-Clause-Patent
77 Returns the 16-bit Length field of a device path node.
79 Returns the 16-bit Length field of the device path node specified by Node.
80 Node is not required to be aligned on a 16-bit boundary, so it is recommended
88 @return The 16-bit Length field of the device path node specified by Node.
186 a 16-bit boundary, so it is recommended that a function such as WriteUnaligned16()
213 END_DEVICE_PATH_LENGTH. Node is not required to be aligned on a 16-bit boundary,
273 FirstDevicePath in a newly allocated buffer. Only the end-of-device-path device node from
277 If both FirstDevicePath and SecondDevicePath are NULL, then a copy of an end-of-device-path is
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | netisr.9 | 65 .Bd -ragged -offset indent
77 Protocol registration and work stream statistics may be monitored using
79 .Ss Protocol registration
98 for each protocol.
99 Disabling will also purge any outstanding packet from the protocol queue.
102 supports multi-processor execution of handlers, and relies on a combination
103 of source ordering and protocol-specific ordering and work-placement
107 .Bl -tag -width NETISR_POLICY_SOURCE
110 should maintain source ordering without advice from the protocol.
120 If the protocol implements
[all …]
|