Running 'mountd' on a different port...

[Robert Adkins <radkins impelind com>]

Hello All,

	I am looking to create a secure NFS connection between our main server
and back-up server in order to facilitate a secure live back-up and also
have the /home directory of the main server mounted up on the back-up
server, in case the main system goes down.

	Anyway, I have read in the NFS-HOWTO about having NFS run through ssh.
One portion, in particular, mentions to use '-p 32767' to change the
port for mountd to be running on, prior to setting up the ssh tunnel to
the other server...

	Well, I want this to be something that can happen "automagically" upon
reboots, both planned and not-so-planned and have started to look into
the 'nfs' startup script. I am a little stuck as to how to configure
'mountd' within the script to use a particular port number.

 	Anyway, here is a section of the script that I believe I need to alter
and after that is the way I believe it should be altered. What I am
looking for is confirmation that this will work. If not, then I am
looking for the way to make it work...


       
if [ -n "$MOUNTD_PORT" ]; then
    RPCMOUNTDOPTS="$RPCMOUNTDOPTS --port $MOUNTD_PORT"
fi

	I am under the impression that if I change the portion shown below that
'mountd' will then be running on the new port number...

if [ -n "$MOUNTD_PORT" ]; then
    RPCMOUNTDOPTS="$RPCMOUNTDOPTS --port 32767"
fi

	Will this do the trick?

	At this time, I am unconcerned regarding NFS filelocking as the user's
won't be accessing the "home" and "share" directories from the "back-up"
server. This configuration is just a temporary stop-gap until I have
IPSEC properly configured to encrypt communication between the two
servers.

	Thanks for any assistance!

	Regards,
	Robert Adkins
	IT Manager/Buyer
	Impel Industries, Inc.
	586-254-5800