Thread View: comp.dcom.sys.cisco
2 messages
2 total messages
Started by WilliamChops Westfield
Fri, 07 Sep 1990 02:45
Re: LAT-Telnet Translation over Ethernet Media
Author: WilliamChops Westfield
Date: Fri, 07 Sep 1990 02:45
Date: Fri, 07 Sep 1990 02:45
41 lines
1899 bytes
1899 bytes
I need bidirectional translation between LAT and Telnet over LAN
(Ethernet) media. cisco has announced LAT support in the CPT (cisco
Protocol Translator) device. Therefore:
1. Will the CPT support Ethernet-Ethernet configurations?
Yes. You can buy it with a single ethernet interface now (or, when 8.2
comes out, anyway.) It isn't designed to have LAT and TCP on separate
ethernets - do you think that would be a useful addition? It doesn't
seem like a common configuration for people to have their LAT network
completely distinct from their IP network.
2. If so, what mappings are available at the CPT to effect the
LAT-Telnet translations? Any translation gotchas?
LAT is a pretty trivial protocol. There isn't much to map. Since the
new CPT is just about to start Beta test, we haven't found any gotchas
yet. I'd be surprised if the code were already perfect though. :-)
The command looks something like:
TRANSLATE LAT <servicename> TCP <hostname> [PORT <port>] [QUIET]
[LOGIN] [MAX-USERS <n>]
or
TRANSLATE TCP <hostname> [PORT <port>] LAT <servicename> [QUIET]
[LOGIN] [MAX-USERS <n>]
3. The CSC/3 processor seems a win for this application. Is the
CSC/3 board available in the CPT configuration?
It is (or will be). Everyone should buy csc/3 processors with everything
they get nowdays. The price difference is so much lower than the upgrade
cost that it's almost embarrassing.
Bill Westfield
cisco Systems.
-------
LAT-Telnet / Telnet-LAT in a router
Author: Juha Heinanen
Date: Sat, 08 Sep 1990 08:22
Date: Sat, 08 Sep 1990 08:22
15 lines
1329 bytes
1329 bytes
In article <25806@boulder.Colorado.EDU> BILLW@mathom.cisco.com (WilliamChops Westfield) writes: It isn't designed to have LAT and TCP on separate ethernets - do you think that would be a useful addition? It doesn't seem like a common configuration for people to have their LAT network completely distinct from their IP network. What we would need is a TELNET/LAT translator integrated in a router so that one could run LAT over any part of the Internet, ie. LAT-TELNET in the source router and TELNET-LAT at the destination. This would solve the problem of running LAT over long distance when bridging is for some reason or other out of question. -- -- Juha Heinanen, Tampere Univ. of Technology, Finland jh@tut.fi (Internet), tut!jh (UUCP), jh@tut (Bitnet)
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads