npc.statd: random ports, by default?

[Brian McKee]

On Monday 21 August 2006 13:46, Daniel Allen wrote:
> I've got NFS running on a batch of ubuntu hosts, and I've noticed that
> by default, statd and mountd will choose a random TCP port.
Yep

> I'm trying to diagnose a problem where another host thought this
> machine was running a "swat" service, on port 901; apparently because
> statd was using it.  Is this more or less acceptable  behaviour?
I'm not sure.   At one point, I did have one of them start up on port
631 on me - which caused some confusion :-( - but I had only half
completed some configuration work, so it might have been self inflicted.

>
> I'm curious why these services use random ports, instead of having
> them assigned (if there's a good online resource that would explain
> this, I'd be happy to know about it too.  I was browsing the linux-NFS
> howto, http://nfs.sourceforge.net/nfs-howto/, but it seems a bit
> out-of-date).

I don't have the docs I found in front of me, but I recently
'pinned' all the NFS services to specific ports so I could implement
firewalling on the servers.  Unfortunately it was all on Mandrake boxes,
so what I found won't directly apply, but it is possible.

Maybe this and link at the bottom will help?
http://sourceforge.net/mailarchive/forum.php?thread_id=8972145&forum_id=2270
I never did see a good reason 'why' I might add, just the fact that
it does.

Brian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20060822/0720e819/attachment.sig>