[daip] aips tcp socket numbers

[Patrick P Murphy]

On Wed, 5 Feb 2003 11:24:12 -0700, Eric Greisen <egreisen at nrao.edu> said:

> We have traditionally used

> 5000/tcp   for sssin
> 5002/tcp   for ssslock
> 5008/tcp   for msgsrv
> 5009/tcp   for teksrv
> 5010/tcp   for TPMON1 (aipsmt0)
> 5011/tcp   for TPMON2 (aipsmt1)
> 5012/tcp   for TPMON3 (aipsmt2)

> In the usual /etc/services file, the only conflict has been with
> "radio free ethernet" at 5002.

> In the MacIntosh

> 5000 is commplex-main (w 5001)
> 5002 is commplex-link (w 5003)
> 5010 is telelpathstart
> 5011 is telelpathattack

http://ntsec.inet-one.com/dir.1999-03/msg00178.html says

  "I have found that many games servers such as the Quake type games and
   MUD's use port 5000+ for listening for connections,..."

You might ask Stephan or James or Allan or K. Scott to try a nmap scan on
the mac to see if it's really listening on those sockets.  I suspect it
isn't and that you can ignore at leat the 5000/5002 ones.

> I am currently lost as to how these work.  But if I use different
> numbers on this Mac, can it talk to a aipsmt0 at 5010 on another
> computer?

As I understand sockets (which is not saying much), nope.  The sequence of
events will be that, e.g. FITTP on the mac will try to open the inet
socket aipsmt1 on a remote host.  To do that it'll call getservbyname()
*locally* on the mac to map the service name to a port number, and get,
say 25011 (if you just added 20,000 to the port numbers).  Then it tries
to connect to the TPMON daemon on the remote host on port 25011, but said
TPMON daemon is listening on port 5011.

> Should we try to migrate all aips's to another set of numbers.

There is a procedure (Don Wells might know more about this) for formally
reserving new port numbers for an app.  It's probably lengthy, full of red
tape and annoying to boot.  But it might be worth the pain.  Then again,
new numbers would orphan all the old AIPS installations from
interoperating with remote TVs and tapes.  

				- Pat