jbn@wdl1.UUCP (09/04/85)
We have observed SUN 2.0 units using some strange Internet addresses not
their own. During booting, they generate protocol 77 packets with various
source IP addresses on network 0, sent as broadcasts to destination addresses
of [0,0,0,0]. They will also send out ARP information for these strange
net 0 source addresses. So, if there is a SUN on your Ethernet, it may
be a good idea to ignore all IP datagrams from net 0. Sites with gateways
to the ARPANET should be especially careful here.
SUNs also use the "rwho" protocol, which is useful in simple
environments but tends to be obnoxious on large ones with long-haul links.
Rwho tells all stations who is logged in on each station, by periodic
broadcast. This is generally undesirable on geographically distributed
networks. Just remove the invocation of the "rwho" daemon from the "rc" file
to turn this off.
Finally, Sun release 2.0 does NOT have the congestion fixes of 4.3BSD;
it clogs up gateways just like the older releases.
John Naglechris@umcp-cs.UUCP (Chris Torek) (09/06/85)
> We have observed SUN 2.0 units using some strange Internet > addresses not their own. During booting, they generate protocol > 77 packets with various source IP addresses on network 0, sent as > broadcasts to destination addresses of [0,0,0,0]. They will also > send out ARP information for these strange net 0 source addresses. Protocol 77 is the network disk. Sounds like you have a diskless node that is attempting to determine its Ethernet address so that it can boot. (My advice: get a local disk....) -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251) UUCP: seismo!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@maryland