Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site rlgvax.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!dcdwest!ittvax!decvax!genrad!panda!talcott!harvard!seismo!rlgvax!guy
From: guy@rlgvax.UUCP (Guy Harris)
Newsgroups: net.lan
Subject: Re: mixing 3com and Interlan boards?
Message-ID: <455@rlgvax.UUCP>
Date: Sat, 9-Feb-85 14:51:14 EST
Article-I.D.: rlgvax.455
Posted: Sat Feb  9 14:51:14 1985
Date-Received: Mon, 11-Feb-85 04:48:41 EST
References: <356@spp2.UUCP> <231@log-hb.UUCP> <412@mcvax.UUCP> <235@log-hb.UUCP> <720@dlinj.UUCP> <241@log-hb.UUCP>
Distribution: net
Organization: CCI Office Systems Group, Reston, VA
Lines: 19

> We recently got the stuff installed, that is we had a SUN 2/120 with 3com,
> and bought a NI1010A + NT100 xcvr + all the cabling from the local Interlan
> reps. ...

> I installed it all myself, and turned the stuff on, rebooted, and voila, no
> problems at all. Rcp and rlogin worked right away. Rwho will NEVER work, it
> seems, ...

"rwho" is frequently a pain in the fundament, because it relies on 1)
broadcasting working and 2) a machine receiving its own broadcast packets.
3Com's UNIBUS ethernet controllers don't receive their own packets; the
driver kludges around this by shoving broadcast packets into the loopback
driver.  We had to do the same on our Power 6/32 with ACC Ethernet
controllers.  We also have an Integrated Solutions machine on our Ethernet
and it doesn't seem to be successfully broadcasting "rwho" packets; it seems
to be receiving our VAXes and Power 6's "rwho" packets OK.

	Guy Harris
	{seismo,ihnp4,allegra}!rlgvax!guy