🚀 go-pugleaf

At the moment, netstat reports udp listeners on numbered ports 663,
664, 707, 1023, 1349, 2657, and 2935.  Not to mention TCP listeners
on 665, 666, and 2453.

From RFC1340, I can figure out that 1349 must be where Simson
Garfinkel's SBook program is checking for license violations.  (At
least one person is willing to do things right.)  That leaves 2
unprivileged UDP, 1 unpriviledged TCP, 4 privileged UDP, and 2
privileged TCP ports, all unaccounted for.  The unprivileged ports I
don't mind so much--any random program might have bound to them.  In
fact, my guess is that 2453 might be the Mach netmessage server.

It's the 6 renegade ports in the IANA-controlled range that bother
me.  Does anyone know who's binding to them, what they're doing, and
why they're usurping "well-known" port numbers to do it?  If it's
because IANA only recently started managing 256-1023, is this fixed
in 3.0?  If not, is NeXT at least in the process of registering them?

-- 
Derek_Beatty@cmu.edu  grad student    (No NeXTMail; MIME Ok.)   1 412 268 7898
Computer Science, Carnegie Mellon Univ., 5000 Forbes Ave, Pgh., PA 15213  USA