Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!AERO4.LARC.NASA.GOV!blbates
From: blbates@AERO4.LARC.NASA.GOV ("Brent L. Bates TAD/TAB ms294 x42854")
Newsgroups: comp.sys.sgi
Subject: Re:  dog on IRIS 3130
Message-ID: <8907141444.AA08943@aero4.larc.nasa.gov>
Date: 14 Jul 89 11:44:13 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20


  I used to have that problem.  We run TCP/IP and the dog that comes
with the machine is XNS.  I got the TCP/IP dog source a while
back and compiled it, now I no longer get the "Ethernet init failed".
As far as I know, you only get an "Ethernet init failed" if you are
trying to run a version of dog that doesn't match the protocal your
machine is using.
  The only problem I have now is that it floods the network with too
many packets sent to broadcast, thus over loading the network.  I wish
dog had the ability to read in a file of machine names and only send
packets to those machines.  Has anyone done this?  Without this option
I can't try the network option of dog.
--

	Brent L. Bates
	NASA-Langley Research Center
	M.S. 294
	Hampton, Virginia  23665-5225
	(804) 864-2854
	E-mail: blbates@aero4.larc.nasa.gov or blbates@aero2.larc.nasa.gov