NFS, Portmap, Port Numbers, Firewalls
I'm trying to get NFS to work through my firewall without much luck. Portmap and NFS stay on dedicated ports but all those RPC processes (statd, mountd, etc.) keep changing port numbers. Is there any way to make these stick to a specific port? Thanks, Jason Joines ===========
* Jason Joines (joines@bus.okstate.edu) [030226 14:09]:
I'm trying to get NFS to work through my firewall without much luck. Portmap and NFS stay on dedicated ports but all those RPC processes (statd, mountd, etc.) keep changing port numbers. Is there any way to make these stick to a specific port?
Not that I know of. It's fairly easy to get the SuSEfirewall to work (see, e.g., http://lists.suse.com/archive/suse-security/2003-Feb/0106.html) but it's ugly. A better solution is to tunnel nfs either through ssh (http://www.math.ualberta.ca/imaging/snfs/) or use a VPN. -- -ckm
On Wednesday 26 February 2003 23:12, Jason Joines wrote:
I'm trying to get NFS to work through my firewall without much luck. Portmap and NFS stay on dedicated ports but all those RPC processes (statd, mountd, etc.) keep changing port numbers. Is there any way to make these stick to a specific port?
Edit /etc/init.d/nfsserver and change the call to start rpc.mountd to startproc /usr/sbin/rpc.mountd -p <port number>
* Anders Johansson (andjoh@rydsbo.net) [030226 14:25]:
startproc /usr/sbin/rpc.mountd -p <port number>
And statd and lockd. Sorry OP, I thought you were trying to go in the opposite direction. -- -ckm "Anders Johansson is as always faultless"
participants (3)
-
Anders Johansson -
Christopher Mahmood -
Jason Joines