Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ucla-cs!zen!ucbvax!TAUNIVM.BITNET!HANK
From: HANK@TAUNIVM.BITNET (Hank Nussbacher)
Newsgroups: comp.protocols.tcp-ip
Subject: VMS and X.25
Message-ID: <8708101644.AA04454@ucbvax.Berkeley.EDU>
Date: Mon, 10-Aug-87 13:17:55 EDT
Article-I.D.: ucbvax.8708101644.AA04454
Posted: Mon Aug 10 13:17:55 1987
Date-Received: Tue, 11-Aug-87 04:39:07 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Hank Nussbacher <HANK%TAUNIVM.BITNET@wiscvm.wisc.edu>
Distribution: world
Organization: The ARPA Internet
Lines: 15

I have been looking at various VMS and microVMS solutions for Tcp/Ip
(Excelan, Interlan-Micom, Wollongong, SRI, Hyperlink, etc.) and all
of them assume an Ethernet.  How do sites connect lone VMS systems that
are geographically scattered over many kilometers?  The expensive solution
is to build a 1 meter Ethernet, buy a bridge and connect that way.  Do any
of these systems handle X.25?  What h/w do you need to buy?  Will the
Excelan and Interlan solutions work with an X.25 card or can an X.25
solution only be handled by a strictly software implementation (like
Wollongong or Hyperlink)?  Is there a way to do it with a leased line
without Ethernet or a bridge?

Thanks,
Hank

P.S. Plz send all replies directly to me.