Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!news.cs.indiana.edu!msi.umn.edu!noc.MR.NET!jhereg!andrew
From: andrew@jhereg.osa.com (Andrew C. Esh)
Newsgroups: comp.dcom.lans
Subject: Re: Wanted: Ethernet packet tech. specs.
Message-ID: <1991Apr10.000558.14760@jhereg.osa.com>
Date: 10 Apr 91 00:05:58 GMT
References: <1991Apr4.190911.14948@ingres.Ingres.COM> <1991Apr5.162615.17234@zoo.toronto.edu>
Organization: Open Systems Architects, Inc., Mpls, MN
Lines: 33

In article <1991Apr5.162615.17234@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes:
>In article <1991Apr4.190911.14948@ingres.Ingres.COM> eandrews@ingres.com (edward e andrews) writes:
>>Finding out the format of IP, TCP, UDP, and ICMP is easy.  Everything else
>>is difficult.  I'd like to find out the technical specs for the following
>>protocols:
>>		DECNET
>>		LAVC
>>		DECLAT
>>		NetBIOS
>>		NETBEUI
>
>I don't know about the rest, but the situation for LAT is simple:  you can't.
>It's proprietary.  Use Telnet.
>-- 
>"The stories one hears about putting up | Henry Spencer @ U of Toronto Zoology
>SunOS 4.1.1 are all true."  -D. Harrison|  henry@zoo.toronto.edu  utzoo!henry

LAT seems to have gotten into HP's hands, since they were able to write a
decode package for their HP-4972A Lan Analyzer that can decode LAT Packets,
as well as just about every other DEC packet type.

Maybe it's proprietary so that another company can't make boxes that use
the same packets, but anyone who has to fix a DEC net needs to know what
the fields are, or the DEC portion of the problem will be almost impossible
to solve. Not something DEC would like to have happen.

I'd call up DEC and ask them. If they're no help, call HP and ask them how
they did it.
-- 
Andrew C. Esh			andrew@osa.com
Open Systems Architects, Inc.
Mpls, MN 55416-1528		Punch down, turn around, do a little crimpin'
(612) 525-0000			Punch down, turn around, plug it in and go ...