HP3000-L Archives

August 2001, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Wirt Atmar <[log in to unmask]>
Reply To:
Date:
Wed, 8 Aug 2001 16:39:45 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
Paul,

> Has anyone connected some DTCs over a VPN? I have a request to find out if
>  anyone is doing it successfully. They want to keep their several hundred
>  terminals a while longer before the cost of upgrading to PCs.

This is one of those things that should be perfectly well doable in theory.
It's just that you're never likely to have met anyone who's actually done it.
In my case, I've never met anyone who's ever even used routable DTCs.
Nonetheless, that's the core of the trick.

Once the DTCs can talk to one another over a TCP/IP connection, the VPN won't
make any difference. It should transfer the TCP/IP packets from one end to
the other completely transparently.

All in all, this becomes nothing more than a doubly wrapped package, where
the VPN supplies the outer wrapper to the TCP packets, doing whatever it
wants to do, while the routable DTCs earlier wrapped the Avesta packets in a
middle layer TCP packet.

The wrappings should all come apart perfectly cleanly at their respective
target ends, with the VPN taking off the first layer and the routable DTC
taking off the second, leaving the core Avesta packet to be interpreted by
the DTC.

Wirt

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2