Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site wnuxb.UUCP
Path: utzoo!decvax!bellcore!petrus!sabre!zeta!epsilon!gamma!ulysses!mhuxr!mhuxn!ihnp4!wnuxb!netnews
From: netnews@wnuxb.UUCP (Heiby)
Newsgroups: mod.unix
Subject: Unix Technical Digest V2 #18
Message-ID: <640@wnuxb.UUCP>
Date: Tue, 1-Oct-85 10:48:12 EDT
Article-I.D.: wnuxb.640
Posted: Tue Oct  1 10:48:12 1985
Date-Received: Thu, 3-Oct-85 02:28:25 EDT
Reply-To: unix@cbosgd.UUCP
Organization: AT&T - Warrenville Data Center, IL
Lines: 36
Keywords: rwhod
Approved: netnews@wnuxb.UUCP
Really-From: Ron Heiby (The Moderator) 


Unix Technical Digest       Tue,  1 Oct 85       Volume  2 : Issue  18

Today's Topics:
                          rwhod not working
----------------------------------------------------------------------

Date: 17 Sep 85 11:37:10 PDT (Tue)
From: 
Subject: rwhod not working

>   Date:  Tue, 3 Sep 85 22:14:20 edt
>   From:  Chris Torek 
>   To:  hakanson%oregon-state.csnet@CSNET-RELAY
>
>   The next step is probably to try to trace the rwho packets.  If
>   they are getting onto the cable, the problem is in the receiving
>   code, otherwise it's in the sending code.

We don't have any Ethernetted PC's, but we do have a couple of
Tektronix 4.2bsd machines on the ethernet, and lo and behold rwho
on those machines reports info about both vaxes (and each other),
which indicates that the sending code is working on all machines.
Both vaxes still seem to be deaf, though.  Does anyone know how
one goes about kicking a packet (rhetoric == TRUE)?

Marion Hakanson         CSnet:  hakanson%oregon-state@csnet-relay
                        UUCP :  {hp-pcd,tektronix}!orstcs!hakanson

------------------------------

End of Unix Technical Digest
******************************
-- 
Ronald W. Heiby / netnews@wnuxb.UUCP
AT&T Information Systems, Inc., Lisle, IL  (CU-D21)