xref: /freebsd/share/man/man4/ng_async.4 (revision 1e413cf93298b5b97441a21d9a50fdcd0ee9945e)
1.\" Copyright (c) 1996-1999 Whistle Communications, Inc.
2.\" All rights reserved.
3.\"
4.\" Subject to the following obligations and disclaimer of warranty, use and
5.\" redistribution of this software, in source or object code forms, with or
6.\" without modifications are expressly permitted by Whistle Communications;
7.\" provided, however, that:
8.\" 1. Any and all reproductions of the source or object code must include the
9.\"    copyright notice above and the following disclaimer of warranties; and
10.\" 2. No rights are granted, in any manner or form, to use Whistle
11.\"    Communications, Inc. trademarks, including the mark "WHISTLE
12.\"    COMMUNICATIONS" on advertising, endorsements, or otherwise except as
13.\"    such appears in the above copyright notice or in the software.
14.\"
15.\" THIS SOFTWARE IS BEING PROVIDED BY WHISTLE COMMUNICATIONS "AS IS", AND
16.\" TO THE MAXIMUM EXTENT PERMITTED BY LAW, WHISTLE COMMUNICATIONS MAKES NO
17.\" REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS SOFTWARE,
18.\" INCLUDING WITHOUT LIMITATION, ANY AND ALL IMPLIED WARRANTIES OF
19.\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
20.\" WHISTLE COMMUNICATIONS DOES NOT WARRANT, GUARANTEE, OR MAKE ANY
21.\" REPRESENTATIONS REGARDING THE USE OF, OR THE RESULTS OF THE USE OF THIS
22.\" SOFTWARE IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY OR OTHERWISE.
23.\" IN NO EVENT SHALL WHISTLE COMMUNICATIONS BE LIABLE FOR ANY DAMAGES
24.\" RESULTING FROM OR ARISING OUT OF ANY USE OF THIS SOFTWARE, INCLUDING
25.\" WITHOUT LIMITATION, ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
26.\" PUNITIVE, OR CONSEQUENTIAL DAMAGES, PROCUREMENT OF SUBSTITUTE GOODS OR
27.\" SERVICES, LOSS OF USE, DATA OR PROFITS, HOWEVER CAUSED AND UNDER ANY
28.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
29.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
30.\" THIS SOFTWARE, EVEN IF WHISTLE COMMUNICATIONS IS ADVISED OF THE POSSIBILITY
31.\" OF SUCH DAMAGE.
32.\"
33.\" Author: Archie Cobbs <archie@FreeBSD.org>
34.\"
35.\" $FreeBSD$
36.\" $Whistle: ng_async.8,v 1.6 1999/01/25 23:46:25 archie Exp $
37.\"
38.Dd January 19, 1999
39.Dt NG_ASYNC 4
40.Os
41.Sh NAME
42.Nm ng_async
43.Nd asynchronous framing netgraph node type
44.Sh SYNOPSIS
45.In sys/types.h
46.In netgraph/ng_async.h
47.Sh DESCRIPTION
48The
49.Nm async
50node type performs conversion between synchronous frames and
51asynchronous frames, as defined for the PPP protocol in RFC 1662.
52Asynchronous framing uses flag bytes and octet-stuffing
53to simulate a frame oriented connection over an octet-oriented
54asynchronous serial line.
55.Pp
56The node transmits and receives asynchronous data on the
57.Dv async
58hook.
59Mbuf boundaries of incoming data are ignored.
60Once a complete packet has been received, it is decoded and
61stripped of all framing bytes, and transmitted out the
62.Dv sync
63hook as a single frame.
64.Pp
65Synchronous frames are transmitted and received on the
66.Dv sync
67hook.
68Packets received on this hook are encoded as asynchronous frames
69and sent out on
70.Dv async .
71Received packets should start with the address and control fields,
72or the PPP protocol field if address and control field compression
73is employed, and contain no checksum field.
74If the first four bytes are
75.Dv "0xff 0x03 0xc0 0x21"
76(an LCP protocol frame) then complete control character escaping
77is enabled for that frame (in PPP, LCP packets are always sent with
78no address and control field compression and all control characters
79escaped).
80.Pp
81This node supports
82.Dq flag sharing
83for packets transmitted on
84.Dv async .
85This is an optimization where the trailing flag byte
86of one frame is shared with the opening flag byte of the next.
87Flag sharing between frames is disabled after one second of transmit
88idle time.
89.Sh HOOKS
90This node type supports the following hooks:
91.Pp
92.Bl -tag -width foobar
93.It Dv async
94Asynchronous connection.
95Typically this hook would be connected to a
96.Xr ng_tty 4
97node, which handles transmission of serial data over a tty device.
98.It Dv sync
99Synchronous connection.
100This hook sends and receives synchronous frames.
101For PPP, these frames should contain address, control, and protocol fields,
102but no checksum field.
103Typically this hook would be connected to an individual link hook of a
104.Xr ng_ppp 4
105type node.
106.El
107.Sh CONTROL MESSAGES
108This node type supports the generic control messages, plus the following:
109.Bl -tag -width foo
110.It Dv NGM_ASYNC_CMD_GET_STATS
111This command returns a
112.Dv "struct ng_async_stat"
113containing node statistics for packet, octet, and error counts.
114.It Dv NGM_ASYNC_CMD_CLR_STATS
115Clears the node statistics.
116.It Dv NGM_ASYNC_CMD_SET_CONFIG
117Sets the node configuration, which is described by a
118.Dv "struct ng_async_cfg" :
119.Bd -literal -offset 4n
120struct ng_async_cfg {
121  u_char    enabled;  /* Turn encoding on/off */
122  u_int16_t amru;     /* Max receive async frame len */
123  u_int16_t smru;     /* Max receive sync frame len */
124  u_int32_t accm;     /* ACCM encoding */
125};
126.Ed
127.Pp
128The
129.Dv enabled
130field enables or disables all encoding/decoding functions (default disabled).
131When disabled, the node operates in simple
132.Dq pass through
133mode.
134The
135.Dv amru
136and
137.Dv smru
138fields are the asynchronous and synchronous MRU (maximum receive unit) values,
139respectively.
140These both default to 1600; note that the async MRU
141applies to the incoming frame length after asynchronous decoding.
142The
143.Dv accm
144field is the asynchronous character control map, which controls the escaping
145of characters 0x00 thorough 0x1f (default 0xffffffff).
146.It Dv NGM_ASYNC_CMD_GET_CONFIG
147This command returns the current configuration structure.
148.El
149.Sh SHUTDOWN
150This node shuts down upon receipt of a
151.Dv NGM_SHUTDOWN
152control message, or when all hooks have been disconnected.
153.Sh SEE ALSO
154.Xr netgraph 4 ,
155.Xr ng_ppp 4 ,
156.Xr ng_tty 4 ,
157.Xr ngctl 8
158.Rs
159.%A W. Simpson
160.%T "PPP in HDLC-link Framing"
161.%O RFC 1662
162.Re
163.Rs
164.%A W. Simpson
165.%T "The Point-to-Point Protocol (PPP)"
166.%O RFC 1661
167.Re
168.Sh HISTORY
169The
170.Nm
171node type was implemented in
172.Fx 4.0 .
173.Sh AUTHORS
174.An Archie Cobbs Aq archie@FreeBSD.org
175