Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!rogue.llnl.gov!oberman
From: oberman@rogue.llnl.gov
Newsgroups: comp.dcom.lans
Subject: Re: 802.3 for NetWare for VMS
Message-ID: <1991Feb28.075008.1@rogue.llnl.gov>
Date: 28 Feb 91 14:50:08 GMT
References: <755@hwsw.gedas.de> <604.27c8f10d@inland.com> <771@hwsw.gedas.de>
Sender: usenet@lll-winken.LLNL.GOV
Lines: 26
Nntp-Posting-Host: rogue.llnl.gov

In article <771@hwsw.gedas.de>, rainer@hwsw.gedas.de (Rainer Raupach) writes:
> Ok, I know this utility and already used it to configure our Novell-gateway
> to have access to both groups. But I thought it might be easier to change
> 4 VAXen rather than econfig 250 PCs.
> 
> Ok, let`s assume, I econfig all the workstations and servers. Will the
> change do anything to the EtherTalk / IPX - gateway?
> What kind of packets are EtherTalk packets?

EtherTalk packets are Ethernet if Phase 1 is used. EtherTalk under Phase 2 uses
802.3.

There has been a great deal of nonsense posted on this topic, but the bottom
line is correct. Novell does not transmit valid 802.3 packets because the 802.2
LLC information is not there. It does do correct Ethernet V2, so it is best to
use this format. Impact on the EtherTalk/IPX gateway is not related to this
issue as EtherTalk packets will continue in whatever format they are now
running, 802.3 for Phase 2 or Ethernet for Phase 1.

					R. Kevin Oberman
					Lawrence Livermore National Laboratory
					Internet: oberman@icdc.llnl.gov
   					(415) 422-6955

Disclaimer: Don't take this too seriously. I just like to improve my typing
and probably don't really know anything useful about anything.