Skip to contentSkip to conversation

Must portmap listen on * in NFS clients?

DISCUSSION Chip Salzenberg 2 participants 2 messages Dec 15, 2003

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

I have a question that will soon be relevant for Debian NFS packaging.

As far as NFS is concerned, need portmap listen on all interfaces when the machine it's on is only an NFS *client*? I know that servers' portmaps must listen on * so clients can find mountd. But, AFAICT, clients need not have open portmaps. Am I right in this?

PS: I should already know this. But NFS protocol issues have always
given me the screaming heebie jeebies.

Signature · 13 lines
Chip Salzenberg               - a.k.a. -               <[email protected]>
"I wanted to play hopscotch with the impenetrable mystery of existence,
    but he stepped in a wormhole and had to go in early."  // MST3K


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
#1 lore raw
Quoted 7 lines · On Monday December 15, [email protected] wrote:

I have a question that will soon be relevant for Debian NFS packaging.

As far as NFS is concerned, need portmap listen on all interfaces when the machine it's on is only an NFS *client*? I know that servers' portmaps must listen on * so clients can find mountd. But, AFAICT, clients need not have open portmaps. Am I right in this?

Locking needs bi-directional RPC service.
In particular, the server needs to be able to communicate with statd on the client to ask it to inform the server if the client restarts, so the server can drop any locks the client had.

Quoted 2 lines

PS: I should already know this. But NFS protocol issues have always
given me the screaming heebie jeebies.

This is completely understandable :-) The simplicity of the core NFS protocol is both a strength (it is easy to implement) and a weakness (all sorts of horrible stuff had to back hacked on afterwards to make it actually work).

NeilBrown

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs