Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ncar!zaphod.mps.ohio-state.edu!ub!clarkson!grape.ecs.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.dcom.lans Subject: Re: TCP/IP on same wire as Ethernet Message-ID: Date: 23 Feb 91 22:59:33 GMT References: <6JcNX1w163w@ersys.uucp> Sender: @grape.ecs.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Lines: 27 In-Reply-To: ersys!wmah@nro.cs.athabascau.ca's message of 20 Feb 91 02:53:40 GMT In article <6JcNX1w163w@ersys.uucp> ersys!wmah@nro.cs.athabascau.ca (Wayne Mah) writes: 1) Can I use the same wire for Novell packets and ethernet packets. Yes. Ethernet packets have a from address (6 bytes), a to address (6 bytes), followed by [IEEE802.3: a length word] [DIX: a type word]. All DIX type codes are larger than any legal Ethernet packet, which is how software can distinguish between them. Novell uses a format that is similar to IEEE802.3's in that it uses a length word. But rather than follow IEEE802.3's type specifications, they follow the length word by a word of all ones. I have read several solutions including using a packet driver from Clarkson and reconfiguring Novells packet using ECONFIG. How do I get these Clarkson drivers (what is their phone number)? 2) How do I get the NCSA or BYU telnet drivers? What is their phone number? Our BBS is (315)268-6667. We have physically moved it, and until we can transfer the calls or move the phone line, it is at x3791. Call x6667 first, and if it doesn't answer, then call x3791. -- --russ I'm proud to be a humble Quaker. It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.