🚀 go-pugleaf

I'm running an Intel '486 box with SCO UNIX V/3.2.2 and TCP/IP 1.1.1b
runtime system installed.  I've got two other systems on the ethernet.
One is a DECstation 3100, the other is a VAXstation II/GPX - both are
running Ultrix.  Anyhow, I recently set all the machines up to start
rwhod when they boot.  From both Ultrix machines, ``rwho'' shows all
users logged in and active on all three systems.  The SCO system is
oblivious to the two DEC boxes, however - users logged into those
machines do not appear in the output of the rwho command.
Additionally, there are no /usr/spool/rwho/whod.* files for the remote
machines.

This means that either (1) rwhod is never seeing the broadcasts, or
(2) it is invalidating the broadcasts from the Ultrix machines.  I
think that (1) is pretty remote given that the other machines are
picking up the SCO machine's broadcasts.  The supporting evidence I
have for (2) is that in the Ultrix machines' /usr/spool/rwho
directories, I see these files:

-rw-r--r--   1 root     rsrv3         108 Aug 19 16:50 whod.bugs
-rw-r--r--   1 root     rsrv3          84 Aug 19 16:52 whod.comton.airs.com
-rw-r--r--   1 root     rsrv3          60 Aug 19 16:52 whod.elmer.airs.com

Notice that our domain (airs.com) is present on the files for the
Ultrix machines (comton and elmer), while no domain name is given for
the SCO machine (bugs).  Since the SCO rwhod manpage states that
incoming broadcasts are validated, and that only broadcasts from
within a local network are permitted, I believe that the ``airs.com''
domain in the broadcasts from the Ultrix machines is being interpreted
as a broadcast from another network, and hence the packets are
discarded.  Anyone able to confirm/refute this?

I looked for a way to tell rwhod the local domain name, so that it
will accept broadcasts from *.airs.com, but there doesn't seem to be
any way to do that.  Any secrets I should know?
--
Andrew Evans (andrew@airs.com) - Infinity Development Systems - Waltham, MA