Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rice!sun-spots-request
From: nraoaoc@jupiter.nmt.edu (NRAO Array Operations Center)
Newsgroups: comp.sys.sun
Subject: Re: SUNOS 3.4 problem
Keywords: Networks
Message-ID: <5029@brazos.Rice.edu>
Date: 15 Feb 90 18:34:48 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 19
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n33
X-Sun-Spots-Digest: Volume 9, Issue 46, message 1

In article <4828@brazos.Rice.edu> iand@labtam.oz.au (Ian Donaldson) writes:
>X-Sun-Spots-Digest: Volume 9, Issue 33, message 6
>
>We had a network of Wellfleet routers and Suns set up at RMIT and found
>that the SunOS 3.5 ping command didn't obey normal routing rules.  

SunOS 3.5 had a buggy ping. There was a patch for the problem, but it
could only be used on servers and standalone systems, i.e. not diskless
clients running ND (at least, the patch we got).

Vastly improved subnet support was added in 4.0[.x]. If you (the original
poster running 3.4 and different subnets on the same wire) don't have any
software holding you back (e.g. drivers for non-Sun devices) it would be a
good idea to upgrade if you are running complex subnetting.

Ruth Milner                                       NRAO/VLA, Socorro NM

   I am posting from a shared guest account. Please send mail only to:
                 rmilner@cholla.aoc.nrao.edu  (Internet)