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.\" $Whistle: ng_rfc1490.8,v 1.4 1999/01/25 23:46:27 archie Exp $ 354cf49a43SJulian Elischer.\" 364cf49a43SJulian Elischer.Dd January 19, 1999 37bec35b9aSArchie Cobbs.Dt NG_RFC1490 4 383d45e180SRuslan Ermilov.Os 394cf49a43SJulian Elischer.Sh NAME 404cf49a43SJulian Elischer.Nm ng_rfc1490 414cf49a43SJulian Elischer.Nd RFC 1490 netgraph node type 424cf49a43SJulian Elischer.Sh SYNOPSIS 4332eef9aeSRuslan Ermilov.In netgraph/ng_rfc1490.h 444cf49a43SJulian Elischer.Sh DESCRIPTION 454cf49a43SJulian ElischerThe 464cf49a43SJulian Elischer.Nm rfc1490 474cf49a43SJulian Elischernode type performs protocol encapsulation, de-encapsulation, and 484cf49a43SJulian Elischermultiplexing according to RFC 1490 (which has since been updated by RFC 2427). 494cf49a43SJulian ElischerThis particular type of encapsulation is often used on top of frame relay 504cf49a43SJulian ElischerDLCI channels. 514cf49a43SJulian Elischer.Pp 524cf49a43SJulian ElischerThe 534cf49a43SJulian Elischer.Dv downstream 54bf7f20c2SRuslan Ermilovhook is used to transmit and receive encapsulated frames. 55bf7f20c2SRuslan ErmilovOn the other side of the node, the 564cf49a43SJulian Elischer.Dv inet 574cf49a43SJulian Elischerand 584cf49a43SJulian Elischer.Dv ppp 594cf49a43SJulian Elischerhooks are used to transmit and receive raw IP frames and PPP frames, 60bf7f20c2SRuslan Ermilovrespectively. 61bf7f20c2SRuslan ErmilovPPP frames are transmitted and received according to 624cf49a43SJulian ElischerRFC 1973; in particular, frames appearing on the 634cf49a43SJulian Elischer.Dv ppp 64bf7f20c2SRuslan Ermilovhook begin with the PPP protocol number. 65bf7f20c2SRuslan ErmilovThe 667586b25cSBrian Feldman.Dv ethernet 677586b25cSBrian Feldmanhook can be used to transmit and receive Ethernet frames (without a 687586b25cSBrian Feldmanchecksum) in RFC 1490's bridging format. 694cf49a43SJulian Elischer.Pp 704cf49a43SJulian ElischerTypically the 714cf49a43SJulian Elischer.Dv inet 724cf49a43SJulian Elischerhook is connected to the 734cf49a43SJulian Elischer.Dv inet 744cf49a43SJulian Elischerhook of an 75bec35b9aSArchie Cobbs.Xr ng_iface 4 764cf49a43SJulian Elischernode. 774cf49a43SJulian Elischer.Sh HOOKS 784cf49a43SJulian ElischerThis node type supports the following hooks: 79c60bda17SJoel Dahl.Bl -tag -width ".Va downstream" 80c60bda17SJoel Dahl.It Va downstream 814cf49a43SJulian ElischerConnects to the RFC 1490 peer entity. 82c60bda17SJoel Dahl.It Va ethernet 837586b25cSBrian FeldmanTransmits and receives bridged raw Ethernet frames, without a checksum. 84c60bda17SJoel Dahl.It Va inet 854cf49a43SJulian ElischerTransmits and receives raw IP frames. 86c60bda17SJoel Dahl.It Va ppp 874cf49a43SJulian ElischerTransmits and receives PPP frames. 884cf49a43SJulian Elischer.El 894cf49a43SJulian Elischer.Sh CONTROL MESSAGES 90a974ba0bSJulian ElischerThis node type supports the generic control messages, plus the following: 91c60bda17SJoel Dahl.Bl -tag -width foo 92c60bda17SJoel Dahl.It Dv NGM_RFC1490_SET_ENCAP Pq Ic setencap 93a974ba0bSJulian ElischerThis command sets encapsulation method for the node. 94a974ba0bSJulian ElischerThe desired method must be passed as a string message argument, 95a974ba0bSJulian Elischerand must be one of the following supported encapsulation modes: 96bf7f20c2SRuslan Ermilov.Bl -tag -width ".Qq Li ietf-snap" 97bf7f20c2SRuslan Ermilov.It Qq Li ietf-ip 98a974ba0bSJulian ElischerIP packets are sent using simple RFC1490/2427 encapsulation. 99bf7f20c2SRuslan Ermilov.It Qq Li ietf-snap 100a974ba0bSJulian ElischerIP packets are sent inside SNAP frames. 101a974ba0bSJulian ElischerAlso conforms to RFC1490/2427. 102bf7f20c2SRuslan Ermilov.It Qq Li cisco 103a974ba0bSJulian ElischerIP packets are sent and received using proprietary Cisco encapsulation 104a974ba0bSJulian Elischermethod. 105a974ba0bSJulian Elischer.El 106c60bda17SJoel Dahl.It Dv NGM_RFC1490_GET_ENCAP Pq Ic getencap 107a974ba0bSJulian ElischerThis command returns current encapsulation method on the node. 108a974ba0bSJulian Elischer.El 1094cf49a43SJulian Elischer.Sh SHUTDOWN 1104cf49a43SJulian ElischerThis node shuts down upon receipt of a 1114cf49a43SJulian Elischer.Dv NGM_SHUTDOWN 1124cf49a43SJulian Elischercontrol message, or when all hooks have been disconnected. 1134cf49a43SJulian Elischer.Sh SEE ALSO 1144cf49a43SJulian Elischer.Xr netgraph 4 , 115bec35b9aSArchie Cobbs.Xr ng_frame_relay 4 , 116bec35b9aSArchie Cobbs.Xr ng_iface 4 , 117bec35b9aSArchie Cobbs.Xr ngctl 8 1184cf49a43SJulian Elischer.Rs 1190f5fcaa3SSheldon Hearn.%A C. Brown 1200f5fcaa3SSheldon Hearn.%A A. Malis 1214cf49a43SJulian Elischer.%T "Multiprotocol Interconnect over Frame Relay" 1224cf49a43SJulian Elischer.%O RFC 2427 1234cf49a43SJulian Elischer.Re 1244cf49a43SJulian Elischer.Rs 1254cf49a43SJulian Elischer.%A W. Simpson 1264cf49a43SJulian Elischer.%T "PPP in Frame Relay" 1274cf49a43SJulian Elischer.%O RFC 1973 1284cf49a43SJulian Elischer.Re 129bf7f20c2SRuslan Ermilov.Pp 130bf7f20c2SRuslan Ermilov.Pa http://www.cisco.com/warp/public/121/frf8modes.pdf 13151291597SJulian Elischer.Sh HISTORY 13251291597SJulian ElischerThe 13351291597SJulian Elischer.Nm 13451291597SJulian Elischernode type was implemented in 13551291597SJulian Elischer.Fx 4.0 . 13651291597SJulian Elischer.Sh AUTHORS 137*6c899950SBaptiste Daroussin.An Julian Elischer Aq Mt julian@FreeBSD.org 1389cbda590SRuslan Ermilov.Sh BUGS 1399cbda590SRuslan ErmilovNot all of RFC 1490 is implemented. 140