nfs issue...

[Pete Nesbitt]

On July 2, 2004 01:03 pm, bruce wrote:
> pete...
>
> some of the information i've seen indicates that you somehow have to
> specify the port that some of the nfs processes use on the nfs server. if
> this has to occur during startup, where else could it occur, but in the nfs
> startup script... a preleminary test shows that you can actually add a
> couple of lines to the \etc\rc.d\init.d\nfs script and that it appears to
> "lock" the input/output ports..
>
> this would then allow you to create the iptables that would be solid,
> because the ports for the processes wouldn't be changing...
>
> thoughts/comments/criticisms/etc...
>
> -bruce


Bruce,
Well, I have not set up nfs thru a firewall, so...
(does it still fail with the established/related?)

Have a look at /etc/init.d/nfslock
You can specify the port for statd quite easily, i'm just not positive the 
best place, either in a /etc/sysconfig/nfs, or else near the top of 
/etc/init.d/nfslock I greped for the variable over init.d and only nfslock 
uses it.

Either way, the script checks for the variable, and impliments it if it 
exists.
just add the line:
STATD_PORT=nnnn
and optionally, STATD_OUTGOING_PORT=nnnn
where nnnn is the static port you want.

<snip..>
> >> The other daemons, statd, mountd, lockd, and rquotad, will normally move
> > around to the first available port they are informed of by the
> > portmapper.

hmmm, or do you just need to add portmapper? (111)


-- 
Pete Nesbitt, rhce