D. Allen [CGL]" <idallen@watcgl.waterloo.edu> (07/13/90)
Is there some way I can use "lcp -h" to point a LAT terminal in /dev/ at another LAT terminal in /dev/ on another machine, instead of pointing it at a LAT terminal server port? I'm not sure why I'd want to do this, but I can't think why it shouldn't work. -- -IAN! (Ian! D. Allen) idallen@watcgl.uwaterloo.ca idallen@watcgl.waterloo.edu [129.97.128.64] Computer Graphics Lab/University of Waterloo/Ontario/Canada
thomas@mipsbx.nac.dec.com (Matt Thomas) (07/15/90)
> Is there some way I can use "lcp -h" to point a LAT terminal in /dev/ > at another LAT terminal in /dev/ on another machine, instead of pointing > it at a LAT terminal server port? I'm not sure why I'd want to do this, > but I can't think why it shouldn't work. I can. ULTRIX is only a slave implementation of LAT. A LAT system that responds to host initiated connections is a master implementation. In summary, you can't do it. -- Matt Thomas Internet: thomas@wrl.dec.com DECnet-ULTRIX Development UUCP: ...!decwrl!thomas Digital Equipment Corporation Disclaimer: This message reflects my own Littleton, MA warped views, etc.
kph@dustbin.cisco.com (Kevin Paul Herbert) (07/16/90)
Well, it wasn't this sort of application that I was thinking of when I designed this mechanism, but generality has its bonuses... For the next release of cisco Protocol Translators (V8.2), if you have LAT support, you could create LAT services which automatically issued a LAT command to connect you to another host. You would set up the LAT terminal in lcp just as if it was a printer service, and set up the cisco to speak the master side of the connection to both Ultrix systems. This feature was designed to allow one to set up LAT services which will connect to other systems via TELNET or X.25, but you could do LAT to LAT as well. Kevin