14cf49a43SJulian Elischer.\" Copyright (c) 1996-1999 Whistle Communications, Inc. 24cf49a43SJulian Elischer.\" All rights reserved. 34cf49a43SJulian Elischer.\" 44cf49a43SJulian Elischer.\" Subject to the following obligations and disclaimer of warranty, use and 54cf49a43SJulian Elischer.\" redistribution of this software, in source or object code forms, with or 64cf49a43SJulian Elischer.\" without modifications are expressly permitted by Whistle Communications; 74cf49a43SJulian Elischer.\" provided, however, that: 84cf49a43SJulian Elischer.\" 1. Any and all reproductions of the source or object code must include the 94cf49a43SJulian Elischer.\" copyright notice above and the following disclaimer of warranties; and 104cf49a43SJulian Elischer.\" 2. No rights are granted, in any manner or form, to use Whistle 114cf49a43SJulian Elischer.\" Communications, Inc. trademarks, including the mark "WHISTLE 124cf49a43SJulian Elischer.\" COMMUNICATIONS" on advertising, endorsements, or otherwise except as 134cf49a43SJulian Elischer.\" such appears in the above copyright notice or in the software. 144cf49a43SJulian Elischer.\" 154cf49a43SJulian Elischer.\" THIS SOFTWARE IS BEING PROVIDED BY WHISTLE COMMUNICATIONS "AS IS", AND 164cf49a43SJulian Elischer.\" TO THE MAXIMUM EXTENT PERMITTED BY LAW, WHISTLE COMMUNICATIONS MAKES NO 174cf49a43SJulian Elischer.\" REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS SOFTWARE, 184cf49a43SJulian Elischer.\" INCLUDING WITHOUT LIMITATION, ANY AND ALL IMPLIED WARRANTIES OF 194cf49a43SJulian Elischer.\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. 204cf49a43SJulian Elischer.\" WHISTLE COMMUNICATIONS DOES NOT WARRANT, GUARANTEE, OR MAKE ANY 214cf49a43SJulian Elischer.\" REPRESENTATIONS REGARDING THE USE OF, OR THE RESULTS OF THE USE OF THIS 224cf49a43SJulian Elischer.\" SOFTWARE IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY OR OTHERWISE. 234cf49a43SJulian Elischer.\" IN NO EVENT SHALL WHISTLE COMMUNICATIONS BE LIABLE FOR ANY DAMAGES 244cf49a43SJulian Elischer.\" RESULTING FROM OR ARISING OUT OF ANY USE OF THIS SOFTWARE, INCLUDING 254cf49a43SJulian Elischer.\" WITHOUT LIMITATION, ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, 264cf49a43SJulian Elischer.\" PUNITIVE, OR CONSEQUENTIAL DAMAGES, PROCUREMENT OF SUBSTITUTE GOODS OR 274cf49a43SJulian Elischer.\" SERVICES, LOSS OF USE, DATA OR PROFITS, HOWEVER CAUSED AND UNDER ANY 284cf49a43SJulian Elischer.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 294cf49a43SJulian Elischer.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 304cf49a43SJulian Elischer.\" THIS SOFTWARE, EVEN IF WHISTLE COMMUNICATIONS IS ADVISED OF THE POSSIBILITY 314cf49a43SJulian Elischer.\" OF SUCH DAMAGE. 324cf49a43SJulian Elischer.\" 33eddc45e7SJeroen Ruigrok van der Werven.\" Author: Archie Cobbs <archie@FreeBSD.org> 344cf49a43SJulian Elischer.\" 354cf49a43SJulian Elischer.\" $FreeBSD$ 364cf49a43SJulian Elischer.\" $Whistle: ng_frame_relay.8,v 1.4 1999/01/25 23:46:26 archie Exp $ 374cf49a43SJulian Elischer.\" 384cf49a43SJulian Elischer.Dd January 19, 1999 39bec35b9aSArchie Cobbs.Dt NG_FRAME_RELAY 4 403d45e180SRuslan Ermilov.Os 414cf49a43SJulian Elischer.Sh NAME 424cf49a43SJulian Elischer.Nm ng_frame_relay 4351291597SJulian Elischer.Nd frame relay netgraph node type 444cf49a43SJulian Elischer.Sh SYNOPSIS 4532eef9aeSRuslan Ermilov.In netgraph/ng_frame_relay.h 464cf49a43SJulian Elischer.Sh DESCRIPTION 474cf49a43SJulian ElischerThe 484cf49a43SJulian Elischer.Nm frame_relay 494cf49a43SJulian Elischernode type performs encapsulation, de-encapsulation, and multiplexing 504cf49a43SJulian Elischerof packets using the frame relay protocol. It supports up to 1024 DLCI's. 514cf49a43SJulian ElischerThe LMI protocol is handled by a separate node type (see 52bec35b9aSArchie Cobbs.Xr ng_lmi 4 ) . 534cf49a43SJulian Elischer.Pp 544cf49a43SJulian ElischerThe 554cf49a43SJulian Elischer.Dv downstream 564cf49a43SJulian Elischerhook should be connected to the synchronous line, i.e., the switch. 574cf49a43SJulian ElischerThen hooks 584cf49a43SJulian Elischer.Dv dlci0 , 594cf49a43SJulian Elischer.Dv dlci1 , 604cf49a43SJulian Elischerthrough 614cf49a43SJulian Elischer.Dv dlci1023 624cf49a43SJulian Elischerare available to connect to each of the DLCI channels. 634cf49a43SJulian Elischer.Sh HOOKS 644cf49a43SJulian ElischerThis node type supports the following hooks: 654cf49a43SJulian Elischer.Pp 664cf49a43SJulian Elischer.Bl -tag -width foobar 674cf49a43SJulian Elischer.It Dv downstream 684cf49a43SJulian ElischerThe connection to the synchronous line. 694cf49a43SJulian Elischer.It Dv dlciX 704cf49a43SJulian ElischerHere X is a decimal number from 0 to 1023. This hook corresponds 714cf49a43SJulian Elischerto the DLCI X frame relay virtual channel. 724cf49a43SJulian Elischer.El 734cf49a43SJulian Elischer.Sh CONTROL MESSAGES 744cf49a43SJulian ElischerThis node type supports only the generic control messages. 754cf49a43SJulian Elischer.Sh SHUTDOWN 764cf49a43SJulian ElischerThis node shuts down upon receipt of a 774cf49a43SJulian Elischer.Dv NGM_SHUTDOWN 784cf49a43SJulian Elischercontrol message, or when all hooks have been disconnected. 794cf49a43SJulian Elischer.Sh BUGS 804cf49a43SJulian ElischerTechnically, frames on DLCI X should not be transmitted to the switch 814cf49a43SJulian Elischeruntil the LMI protocol entity on both ends has configured DLCI X as active. 824cf49a43SJulian ElischerThe 8351291597SJulian Elischer.Nm 844cf49a43SJulian Elischernode type ignores this restriction, and will always pass data received 854cf49a43SJulian Elischeron a DLCI hook to 864cf49a43SJulian Elischer.Dv downstream . 874cf49a43SJulian ElischerInstead, it should query the LMI node first. 884cf49a43SJulian Elischer.Sh SEE ALSO 894cf49a43SJulian Elischer.Xr netgraph 4 , 90bec35b9aSArchie Cobbs.Xr ng_lmi 4 , 91bec35b9aSArchie Cobbs.Xr ngctl 8 9251291597SJulian Elischer.Sh HISTORY 9351291597SJulian ElischerThe 9451291597SJulian Elischer.Nm 9551291597SJulian Elischernode type was implemented in 9651291597SJulian Elischer.Fx 4.0 . 9751291597SJulian Elischer.Sh AUTHORS 98eddc45e7SJeroen Ruigrok van der Werven.An Julian Elischer Aq julian@FreeBSD.org 99