Newsgroups: comp.protocols.tcp-ip
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!ukma!widener!iggy.GW.Vitalink.COM!riscit.NOC.Vitalink.COM!ejm
From: ejm@riscit.NOC.Vitalink.COM (Erik J. Murrey)
Subject: Re: Wanted : ethernet protocol list...
Message-ID: <1991May29.170106.1454@iggy.GW.Vitalink.COM>
Sender: usenet@iggy.GW.Vitalink.COM (USENET News Admin)
Nntp-Posting-Host: riscit.noc.vitalink.com
Organization: Vitalink Communications, Fremont, California
References:  <1991May29.181433.1@vmsa.technion.ac.il>
Date: Wed, 29 May 1991 17:01:06 GMT

In article <1991May29.181433.1@vmsa.technion.ac.il>, politis@VMSA.TECHNION.AC.IL writes:
|> 
|> 	Hello ,
|> 
|> Could anyone give me the translation of these ethernet protocols or give  a
|> pointer to a site I could FTP an extensive list of protocols along with their
|> translation ,as I might discover new protocols on our network and I wouldn't 
|> like to send such a request every week or so ...
|> 
|> 				Thank you all,
|> 					Joseph.
|>               


Some of these packet types may be misleading.  For instance, if your ethernet
is incurring errors, you may see funny packet types go by on your equipment.
Most network analyzers still capture what they can from a bad packet.  Just
keep in mind that the packet type could be reported incorrectly in these cases.

Be sure to check the FCS (CRC), Overrun, Collision and runt packet error counts
to see if this is the cause of these packets....

---
Erik J. Murrey
Vitalink Communications NOC
ejm@NOC.Vitalink.COM	...!uunet!NOC.Vitalink.COM!ejm
