Xref: utzoo comp.dcom.lans:2288 comp.protocols.misc:461 comp.sys.dec:971 comp.unix.wizards:14274 comp.org.decus:324
Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!pyramid!prls!philabs!nbc1!stone
From: stone@nbc1.UUCP (Anthony Stone)
Newsgroups: comp.dcom.lans,comp.protocols.misc,comp.sys.dec,comp.unix.wizards,comp.org.decus
Subject: LAT Protocol: Request for Specification
Keywords: simulate LAT terminal servers, talking LAT host-to-host
Message-ID: <570@nbc1.UUCP>
Date: 20 Jan 89 00:21:02 GMT
Organization: NBC Computer Imaging, New York, NY
Lines: 21

Greetings. I've been assigned the challenging task of simulating 150+ users
connected via terminal servers to a crucial application running on a VMS system
here at NBC. To do this I must read and write packets on the ethernet that look
like those going to/from a DECserver 100 or 200.

Yes, I know LAT is proprietary to DEC, but management doesn't like it here
when we tell them that something can't be done. I know there are LAT-compatible
terminal servers available, so someone besides DEC has the specification.
I envision using the nit(4) facility in SunOS to generate, filter and read
the packets -- but I'm open to other ideas.

I've explored other ways of doing this, but it always comes back to simulating
LAT. There are no programming tools on the VMS system. I've also tried DECnet,
but there's too much overhead and the CTERM protocol that dlogind uses is
proprietary too.

And so I turn to the collective mind of the net. 'Anyone cracked LAT?
If you have a program or documentation, I'd appreciate your help. Thanks.
-- 
Anthony Stone			NBC Computer Imaging, New York, NY
stone@nbc1.ge.com		212-664-2206