Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uwm.edu!linac!att!pacbell.com!lll-winken!ptavv.llnl.gov!oberman
From: oberman@ptavv.llnl.gov
Newsgroups: comp.protocols.tcp-ip
Subject: Re: LAT vs telnet
Message-ID: <1991May8.085509.1@ptavv.llnl.gov>
Date: 8 May 91 15:55:09 GMT
References: <9105072303.AA00610@WLV.IMSD.CONTEL.COM>
Sender: usenet@lll-winken.LLNL.GOV
Lines: 23
Nntp-Posting-Host: ptavv.llnl.gov

In article <9105072303.AA00610@WLV.IMSD.CONTEL.COM>, mcc@WLV.IMSD.CONTEL.COM (Merton Campbell Crockett) writes:
> ->Andrew McRae (andrew@megadata.mega.oz.au) writes:
> ->[summarized]
> 
> ->2. LAT doesn't work through routers, but so what.
> 
>       Works here!  Must be something wrong with your router.
 
I suspect you have one of the new generation of brouters (bridge/routers).
That's what we use here. (cisco) It is configured to route selected, routable
protocols like IP and DECnet and bridge any others with filters to control
things in finer detail.

I can state absolutely that LAT is NOT routable, but that doesn't mean that it
won't work through a brouter. cisco even has special compression software just
for LAT over low-speed links.

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. Especially
anything gnu.