Path: utzoo!mnetor!uunet!husc6!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!purdue!decwrl!ucbvax!XEROX.COM!RMRichardson.PA
From: RMRichardson.PA@XEROX.COM (Rich)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Many things on ethernet together???
Message-ID: <880503-224006-1394@Xerox>
Date: 4 May 88 05:40:04 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: RMRichardson.PA@Xerox.COM
Organization: The Internet
Lines: 22

In article <51442@sun.uucp> limes@sun.com (Greg Limes) writes:

> In article <218@turbo.RAY.COM> Robin@turbo.RAY.COM (Robin Alston) writes:

> >Can XNS and TCP-IP share the same coax cable with no possible problems?

> ... It is even possible (gag) to run both TCP/IP and XNS through the same 
> physical interface, but the bottom layer does need to know where to send 
> each packet type. ... 

My workstation can talk PUP, XNS and TCP/IP simultaneously, i.e., three 
connections at once, all on the same wire.  I make no claims about speed, 
etc., just that it can be done, so you should be able to do the same.  

> >Can we have our own domain (we really have no interest at this time in
> >talking to our vaxes), while decnet has its own on the same cable?

This should be ok; the fun part comes when you do want to talk to each 
other.  Then you need an XNS package on the vaxes, or TCP-IP on your other 
machines.  

Rich