1999-10-21 09:06:11 +00:00
|
|
|
.\" Copyright (c) 1996-1999 Whistle Communications, Inc.
|
|
|
|
.\" All rights reserved.
|
2001-07-14 19:41:16 +00:00
|
|
|
.\"
|
1999-10-21 09:06:11 +00:00
|
|
|
.\" Subject to the following obligations and disclaimer of warranty, use and
|
|
|
|
.\" redistribution of this software, in source or object code forms, with or
|
|
|
|
.\" without modifications are expressly permitted by Whistle Communications;
|
|
|
|
.\" provided, however, that:
|
|
|
|
.\" 1. Any and all reproductions of the source or object code must include the
|
|
|
|
.\" copyright notice above and the following disclaimer of warranties; and
|
|
|
|
.\" 2. No rights are granted, in any manner or form, to use Whistle
|
|
|
|
.\" Communications, Inc. trademarks, including the mark "WHISTLE
|
|
|
|
.\" COMMUNICATIONS" on advertising, endorsements, or otherwise except as
|
|
|
|
.\" such appears in the above copyright notice or in the software.
|
2001-07-14 19:41:16 +00:00
|
|
|
.\"
|
1999-10-21 09:06:11 +00:00
|
|
|
.\" THIS SOFTWARE IS BEING PROVIDED BY WHISTLE COMMUNICATIONS "AS IS", AND
|
|
|
|
.\" TO THE MAXIMUM EXTENT PERMITTED BY LAW, WHISTLE COMMUNICATIONS MAKES NO
|
|
|
|
.\" REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS SOFTWARE,
|
|
|
|
.\" INCLUDING WITHOUT LIMITATION, ANY AND ALL IMPLIED WARRANTIES OF
|
|
|
|
.\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
|
|
|
|
.\" WHISTLE COMMUNICATIONS DOES NOT WARRANT, GUARANTEE, OR MAKE ANY
|
|
|
|
.\" REPRESENTATIONS REGARDING THE USE OF, OR THE RESULTS OF THE USE OF THIS
|
|
|
|
.\" SOFTWARE IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY OR OTHERWISE.
|
|
|
|
.\" IN NO EVENT SHALL WHISTLE COMMUNICATIONS BE LIABLE FOR ANY DAMAGES
|
|
|
|
.\" RESULTING FROM OR ARISING OUT OF ANY USE OF THIS SOFTWARE, INCLUDING
|
|
|
|
.\" WITHOUT LIMITATION, ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
|
|
|
|
.\" PUNITIVE, OR CONSEQUENTIAL DAMAGES, PROCUREMENT OF SUBSTITUTE GOODS OR
|
|
|
|
.\" SERVICES, LOSS OF USE, DATA OR PROFITS, HOWEVER CAUSED AND UNDER ANY
|
|
|
|
.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
|
|
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
|
|
|
.\" THIS SOFTWARE, EVEN IF WHISTLE COMMUNICATIONS IS ADVISED OF THE POSSIBILITY
|
|
|
|
.\" OF SUCH DAMAGE.
|
2001-07-14 19:41:16 +00:00
|
|
|
.\"
|
2000-10-26 15:30:44 +00:00
|
|
|
.\" Author: Archie Cobbs <archie@FreeBSD.org>
|
1999-10-21 09:06:11 +00:00
|
|
|
.\"
|
|
|
|
.\" $FreeBSD$
|
|
|
|
.\" $Whistle: ng_rfc1490.8,v 1.4 1999/01/25 23:46:27 archie Exp $
|
|
|
|
.\"
|
|
|
|
.Dd January 19, 1999
|
2000-05-04 17:54:37 +00:00
|
|
|
.Dt NG_RFC1490 4
|
2001-07-10 15:31:11 +00:00
|
|
|
.Os
|
1999-10-21 09:06:11 +00:00
|
|
|
.Sh NAME
|
|
|
|
.Nm ng_rfc1490
|
|
|
|
.Nd RFC 1490 netgraph node type
|
|
|
|
.Sh SYNOPSIS
|
2001-10-01 16:09:29 +00:00
|
|
|
.In netgraph/ng_rfc1490.h
|
1999-10-21 09:06:11 +00:00
|
|
|
.Sh DESCRIPTION
|
|
|
|
The
|
|
|
|
.Nm rfc1490
|
|
|
|
node type performs protocol encapsulation, de-encapsulation, and
|
|
|
|
multiplexing according to RFC 1490 (which has since been updated by RFC 2427).
|
|
|
|
This particular type of encapsulation is often used on top of frame relay
|
|
|
|
DLCI channels.
|
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Dv downstream
|
2004-06-16 08:33:57 +00:00
|
|
|
hook is used to transmit and receive encapsulated frames.
|
|
|
|
On the other side of the node, the
|
1999-10-21 09:06:11 +00:00
|
|
|
.Dv inet
|
|
|
|
and
|
|
|
|
.Dv ppp
|
|
|
|
hooks are used to transmit and receive raw IP frames and PPP frames,
|
2004-06-16 08:33:57 +00:00
|
|
|
respectively.
|
|
|
|
PPP frames are transmitted and received according to
|
1999-10-21 09:06:11 +00:00
|
|
|
RFC 1973; in particular, frames appearing on the
|
|
|
|
.Dv ppp
|
2004-06-16 08:33:57 +00:00
|
|
|
hook begin with the PPP protocol number.
|
|
|
|
The
|
2004-01-14 00:39:28 +00:00
|
|
|
.Dv ethernet
|
|
|
|
hook can be used to transmit and receive Ethernet frames (without a
|
|
|
|
checksum) in RFC 1490's bridging format.
|
1999-10-21 09:06:11 +00:00
|
|
|
.Pp
|
|
|
|
Typically the
|
|
|
|
.Dv inet
|
|
|
|
hook is connected to the
|
|
|
|
.Dv inet
|
|
|
|
hook of an
|
2000-05-04 17:54:37 +00:00
|
|
|
.Xr ng_iface 4
|
1999-10-21 09:06:11 +00:00
|
|
|
node.
|
|
|
|
.Sh HOOKS
|
|
|
|
This node type supports the following hooks:
|
|
|
|
.Bl -tag -width foobarbazum
|
|
|
|
.It Dv downstream
|
|
|
|
Connects to the RFC 1490 peer entity.
|
2004-01-14 00:39:28 +00:00
|
|
|
.It Dv ethernet
|
|
|
|
Transmits and receives bridged raw Ethernet frames, without a checksum.
|
1999-10-21 09:06:11 +00:00
|
|
|
.It Dv inet
|
|
|
|
Transmits and receives raw IP frames.
|
|
|
|
.It Dv ppp
|
|
|
|
Transmits and receives PPP frames.
|
|
|
|
.El
|
|
|
|
.Sh CONTROL MESSAGES
|
2004-06-13 15:44:00 +00:00
|
|
|
This node type supports the generic control messages, plus the following:
|
2004-06-16 08:33:57 +00:00
|
|
|
.Bl -tag -width indent
|
2004-06-13 15:44:00 +00:00
|
|
|
.It Dv NGM_RFC1490_SETENCAP
|
|
|
|
This command sets encapsulation method for the node.
|
|
|
|
The desired method must be passed as a string message argument,
|
|
|
|
and must be one of the following supported encapsulation modes:
|
2004-06-16 08:33:57 +00:00
|
|
|
.Bl -tag -width ".Qq Li ietf-snap"
|
|
|
|
.It Qq Li ietf-ip
|
2004-06-13 15:44:00 +00:00
|
|
|
IP packets are sent using simple RFC1490/2427 encapsulation.
|
2004-06-16 08:33:57 +00:00
|
|
|
.It Qq Li ietf-snap
|
2004-06-13 15:44:00 +00:00
|
|
|
IP packets are sent inside SNAP frames.
|
|
|
|
Also conforms to RFC1490/2427.
|
2004-06-16 08:33:57 +00:00
|
|
|
.It Qq Li cisco
|
2004-06-13 15:44:00 +00:00
|
|
|
IP packets are sent and received using proprietary Cisco encapsulation
|
|
|
|
method.
|
|
|
|
.El
|
|
|
|
.It Dv NGM_RFC1490_GETENCAP
|
|
|
|
This command returns current encapsulation method on the node.
|
|
|
|
.El
|
1999-10-21 09:06:11 +00:00
|
|
|
.Sh SHUTDOWN
|
|
|
|
This node shuts down upon receipt of a
|
|
|
|
.Dv NGM_SHUTDOWN
|
|
|
|
control message, or when all hooks have been disconnected.
|
|
|
|
.Sh SEE ALSO
|
|
|
|
.Xr netgraph 4 ,
|
2000-05-04 17:54:37 +00:00
|
|
|
.Xr ng_frame_relay 4 ,
|
|
|
|
.Xr ng_iface 4 ,
|
|
|
|
.Xr ngctl 8
|
1999-10-21 09:06:11 +00:00
|
|
|
.Rs
|
2000-05-10 09:49:04 +00:00
|
|
|
.%A C. Brown
|
|
|
|
.%A A. Malis
|
1999-10-21 09:06:11 +00:00
|
|
|
.%T "Multiprotocol Interconnect over Frame Relay"
|
|
|
|
.%O RFC 2427
|
|
|
|
.Re
|
|
|
|
.Rs
|
|
|
|
.%A W. Simpson
|
|
|
|
.%T "PPP in Frame Relay"
|
|
|
|
.%O RFC 1973
|
|
|
|
.Re
|
2004-06-16 08:33:57 +00:00
|
|
|
.Pp
|
|
|
|
.Pa http://www.cisco.com/warp/public/121/frf8modes.pdf
|
1999-12-21 01:25:21 +00:00
|
|
|
.Sh HISTORY
|
|
|
|
The
|
|
|
|
.Nm
|
|
|
|
node type was implemented in
|
|
|
|
.Fx 4.0 .
|
|
|
|
.Sh AUTHORS
|
2000-10-26 15:30:44 +00:00
|
|
|
.An Julian Elischer Aq julian@FreeBSD.org
|
2005-01-21 08:36:40 +00:00
|
|
|
.Sh BUGS
|
|
|
|
Not all of RFC 1490 is implemented.
|