Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!think!snorkelwacker!apple!mrspoc!itkin
From: itkin@mrspoc.Transact.COM (Steven M. List)
Newsgroups: comp.unix.xenix
Subject: Re: Two TCP/IP Links
Message-ID: <1990Mar25.191205.16959@mrspoc.Transact.COM>
Date: 25 Mar 90 19:12:05 GMT
References: <[1282]unix@oldcolo.UUCP>
Reply-To: itkin@guinan.Transact.COM
Organization: Transact Software, Inc., Los Altos, CA
Lines: 27

dave@oldcolo.UUCP (Dave Hughes) writes:

>What is the best solution to the following: A Xenix 2.2.2 386 box
>sitting next to a Unix 3.2 386, which they desire to link together
>with an Ethernet thin wire board and TCP/IP. But a desire to
>*also* link the Unix 3.2 box to a Vax with Ethernet thin wire
>and TCP/IP. 

>What would this entail? Two ethernet boards in the Unix 386, one
>connected to the other 386 and one to the Vax? Will the TCP/IP
>software handle that? Or wil ethernet boards for 386s permit
>multiple thin wire connections?

GACK!  Sorry, Dave, didn't mean to be insulting.

Ethernet is Ethernet is Ethernet.  If you have your 386 connected with
thin Ethernet, then anything else on that network is connected.  No need
for other boards or special setups.  You need to idenify the VAX just like
you would identify any other system on the network, but once done it is
just another node.  No multiple connections, please!  This is NETWORKING,
not serial ports!
-- 
 +----------------------------------------------------------------------------+
 :                Steven List @ Transact Software, Inc. :^>~                  :
 :           Chairman, Unify User Group of Northern California                :
 :     {apple,coherent,limbo,mips,pyramid,ubvax}!itkin@guinan.Transact.COM    :