home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!USU.BITNET!JRD
- X-Envelope-to: NOVELL@SUVM.BITNET
- X-VMS-To: IN%"NOVELL@SUVM.BITNET"
- X-VMS-Cc: JRD
- MIME-version: 1.0
- Content-type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-transfer-encoding: 7BIT
- Message-ID: <01GT227PEUR6927KCY@CC.USU.EDU>
- Newsgroups: bit.listserv.novell
- Date: Sat, 2 Jan 1993 21:02:46 -0600
- Reply-To: Novell LAN Interest Group <NOVELL@SUVM.BITNET>
- Sender: NOVELERR@SUVM.SYR.EDU
- From: Joe Doupnik <JRD@USU.BITNET>
- Subject: Re: TCP access with Arcnet
- Lines: 72
-
- >I wish to use ODI drivers with MS-DOS Kermit for Arcnet. However, I assume I
- >would need to include the Protocol option for Link Driver in the NET.CFG
- >file. What are the hex ids for the protocols with Arcnet frame type listed
- >below?
- > Link Driver TRXNET
- > Frame NOVELL_RX-NET
- > Protocol IPX FA NOVELL_RX-NET
- > Protocol IP ?? NOVELL_RX-NET
- > Protocol ARP ?? NOVELL_RX-NET
- > Protocol RARP ?? NOVELL_RX-NET
- >
- >Where can I find the hex ids (??) and would the above be correct?
- >
- >Again, TIA....
- >
- >Charles
- --------------
-
- Charles,
- All persons in the same category should be aware of the RFCs on the
- topic, in particular RFC1201.TXT which applies with TCP/IP traffic over ODI
- Arcnet drivers. I quote two sections of this below. Note that the numbers
- going into NET.CFG must be in hexadecimal, not decimal. All RFC's are
- available by anonymous ftp to NIC.DDN.MIL.
- Joe D.
- --------
- Network Working Group D. Provan
- Request for Comments: 1201 Novell, Inc.
- Obsoletes: RFC 1051 February 1991
-
-
- Transmitting IP Traffic over ARCNET Networks
-
- Status of this Memo
-
- This memo defines a protocol for the transmission of IP and ARP
- packets over the ARCnet Local Area Network. This RFC specifies an
- IAB standards track protocol for the Internet community, and requests
- discussion and suggestions for improvements. Please refer to the
- current edition of the "IAB Official Protocol Standards" for the
- standardization state and status of this protocol. Distribution of
- this memo is unlimited.
-
- 1. Introduction
-
- This memo specifies a method of encapsulating Internet Protocol (IP)
- [1] and Address Resolution Protocol (ARP) [2] datagrams for
- transmission across ARCNET [3] using the "ARCNET Packet Header
- Definition Standard" [4]. This memo offers a replacement for RFC
- 1051. RFC 1051 uses an ARCNET framing protocol which limits
- unfragmented IP packets to 508 octets [5].
- <etc>
-
- 8. Assigned Numbers
-
- Datapoint Corporation assigns ARCNET protocol IDs to identify
- different protocols running on the same ARCNET medium. For
- implementations of this specification, Datapoint has assigned 212
- ^^^
- decimal to IP, 213 decimal to ARP, and 214 decimal to RARP. These
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
- are not the numbers assigned to the IP encapsulation defined by RFC
- 1051 [5]. Implementations of RFC 1051 can exist on the same ARCNET
- as implementations of this specification, although the two would not
- be able to communicate with each other.
-
- The Internet Assigned Numbers Authority (IANA) assigns ARP hardware
- type values. It has assigned ARCNET the ARP hardware type of 7 [9].
- <etc>
-
- (^^ added to the original to point out the numbers of interest. jrd)
- ------------
-