Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!cmcl2!seismo!brl-adm!brl-smoke!brl-sem!ron From: ron@brl-sem.ARPA (Ron Natalie ) Newsgroups: net.lan Subject: Re: Ethernet connections for mainframes Message-ID: <169@brl-sem.ARPA> Date: Mon, 21-Apr-86 00:18:18 EST Article-I.D.: brl-sem.169 Posted: Mon Apr 21 00:18:18 1986 Date-Received: Thu, 24-Apr-86 07:19:55 EST References: <1104@uwmcsd1.UUCP> Distribution: net Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 19 > We would like to hear from other sites that have such a configuration [mainframe > (of any sort) to Ethernet], preferable by means of an IO channel connection, > since our application requires the bandwidth of an IO channel. The guys down at the University of Maryland who I believe were the first one to do TCP/IP for the UNIVAC were recently talking about using the IBM DACU to connect the Sperry channel to a UNIBUS Ethernet board (Sperry channels are pretty much interchangable with IBM channels). These guys arealso did the software at NOSC.The FUZZBALL plays internet gateway to a serial line to the UNIVAC. Frankly, I believe this is much preferable than kludging a ethernet to the Sperry in any of the methods I've seen so far (DACU's are kind of silly devices). > one commercial solution that we know of; INTERnet Systems Corporation uses a > micro-VAX II to drive an IO channel interface. (These channels, by the way, > are "IBM"-type byte channels.) We are in the middle of having INTERNET systems hook up our Sperry, I'll let you know how it turns out.