🚀 go-pugleaf

Frank-Christian Kruegel wrote:
> 
> kustner@emjay.com wrote on 06.08.96
> about "Should new server be 802.2 or Ethernet II?":
> 
> > We are currently running 802.3 on a NetWare 3.12 server.  We are
> > getting a new server and are thinking of changing frame types.  Would
> > you use 802.2 or Ethernet II on the new server?  Assuming that we want
> > the current server to have the same frame type, are there negative
> > ramifications of changing its frame type (besides changing NET.CFG
> > everywhere)?
> >
> >
> > I'm confused on another issue.  I have seen a number of people say
> > that frame type 802.2 is required for Packet Burst.  Others say that's
> > an absolute fable.  We currently use NETX and we need VLM's to use
> > packet burst.  But does 802.3 support packet burst?  Does Ethernet II?
> 
> Packet burst is always supported, frame signaturing not always (802.3
> is the exception).
> 
> You should choose Ethernet_II. It's the frame type TCP/IP uses, so there
> is no need to use two different types.
> 
> ... unless you have stupid boot roms or printer servers that require
> 802.3 or 802.2. Watch out for them!
> 
> Frank-Christian Kruegel
> 
> ----------------------------------------------------------------------
> fchk@gigabyte.ohz.north.de                 2:2426/3060.1 21:100/8211.1

-- 

Frame type ethernet_ii is required for IP binding.  You might also consider that 
if you are (somewhere) running a SNAP - type protocol as in FDDI_SNAP or 
TOKEN_SNAP and if you are wanting to bridge them to ethernet, they are 
translatable to Ethernet_802.2 frames but NOT to ethernet_802.3 frames.

In summary, ethernet_802.3 frames are pretty nearly useless for hetero 
internetworks, and hitching all your PCs to ethernet_802.3 frames is likely
to cause you a lot of work later when you have to change them all!

------ standard disclaimer --------
The above is mentioned purely as an opinion, and is not meant
to be construed as advice, procedure, or fact.   * WmP *