Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ulysses.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!smb
From: smb@ulysses.UUCP (Steven Bellovin)
Newsgroups: net.lan
Subject: Re: Summary #1 of ethernet information
Message-ID: <852@ulysses.UUCP>
Date: Fri, 18-May-84 11:19:30 EDT
Article-I.D.: ulysses.852
Posted: Fri May 18 11:19:30 1984
Date-Received: Sat, 19-May-84 00:16:35 EDT
References: <238@oddjob.UChicago.UUCP>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 24


	From: matt@oddjob.UChicago.UUCP (Matt Crawford)
	Newsgroups: net.lan
	Subject: Summary #1 of ethernet information
	Message-ID: <238@oddjob.UChicago.UUCP>
	Date: Thu, 17-May-84 11:27:00 EDT


		John Quarterman says that according to rumor, DEC's DEUNA
		won't talk to 3COM.  Also that DEUNA tranceivers won't
		connect to standard Belden cable.  He suggests getting
		Xerox tranceivers.
	
Not quite accurate.  The 3Com *board* and the DEUNA *board* will talk just
fine (I'm typing this in via an rlogin connection between exactly those two
boards); however, the DEUNA *board* won't work with the 3Com *transceiver.
The reason:  the DEUNA meets the Ethernet 2.0 spec, while the 3Com transceiver
is a 1.0 version -- and the DEUNA is so "smart" that it detects the difference
and thinks there's a failure.  In brief tests, I found that the 3Com board would
work with a DEC transceiver, but there is some potential for trouble when
mixing 1.0 stuff with 2.0 (my thanks to Rob Warnock for a long explanation
on this point).


		--Steve Bellovin