Xref: utzoo comp.sys.novell:1055 comp.dcom.lans:7619
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!apple!salt.acc.com!opal!art
From: art@opal.acc.com (Art Berggreen)
Newsgroups: comp.sys.novell,comp.dcom.lans
Subject: Re: Novell on Ethernet protocol encapsulations
Message-ID: <1991Apr1.180819.8629@salt.acc.com>
Date: 1 Apr 91 18:08:19 GMT
References: <1991Mar24.005802.28012@tmsoft.uucp>
Sender: news@salt.acc.com
Reply-To: art@opalacc.com (Art Berggreen)
Organization: Advanced Computer Communications, Santa Barbara, California
Lines: 18

In article <1991Mar24.005802.28012@tmsoft.uucp> mshiels@tmsoft.uucp (Michael A. Shiels) writes:
>What are the different encapsulations for Novell over ethernet.
>
>I know about the standard Ethernet with type number 8137h.
>
>I know about the 802.3/802.2 with SAP number E0h.

This is for Token Ring.  For Ethernet they also can use 802.3/802.2/SNAP
with Ethertype 8137.

>But do they do a funny 802.3 with no 802.2?

SAD, but true.  Unfortuneately, this tends to be the default mode.

The first 16 bits (where DSAP AND SSAP should be) is set to 1's, but
the 802.2 Control field location is not defined.

Art