Fairly simple question, I should think, but I'm running out of patience this morning. I'm trying to do an NFS mount. Everything works fine except one little annoyance. The mount command seems to take a random port to send its requests on. And as soon as I specify a port in the mount options, I get an error that the server is down. Here're some examples.
With the firewall down:
# mount -t nfs -o rsize=32768,wsize=32768,soft host:/path/to/dir /mnt/d
works just fine.
This, however, seems to send traffic on port 111 (which I would like to disable) and some other random port. Mount seems to completely ignore -o port=XXXX I pass it.
# mount -t nfs -o port=2049 host:/path/to/dir /mnt/d
for example, still sends traffic on port 111 and another random port. I need to not only have my box firewalled - but I would also like to set up an occasional NFS mount to my office box, which is firewalled and NATed and is only accessible via port forwarding. And I definitely don't want to open the fire wall for ALL traffic from my box - which has dynamic IP address, anyway. Any thoughts?
With the firewall down:
# mount -t nfs -o rsize=32768,wsize=32768,soft host:/path/to/dir /mnt/d
works just fine.
This, however, seems to send traffic on port 111 (which I would like to disable) and some other random port. Mount seems to completely ignore -o port=XXXX I pass it.
# mount -t nfs -o port=2049 host:/path/to/dir /mnt/d
for example, still sends traffic on port 111 and another random port. I need to not only have my box firewalled - but I would also like to set up an occasional NFS mount to my office box, which is firewalled and NATed and is only accessible via port forwarding. And I definitely don't want to open the fire wall for ALL traffic from my box - which has dynamic IP address, anyway. Any thoughts?
