I found this while searching the mountd man pages:
-P portnum or --port portnum Makes mountd listen on port portnum instead of some random port.
By default, mountd will listen on the mount/udp port specified
in /etc/services, or, if that is undefined, on some arbitrary
port number below 1024.
(note the CAPITAL "P")
I looked in /etc/services (on jaunty) and saw this:
Do you think it would wok if you were to open those ports in the firewall (assuming you haven't already)? I think that once the connection is established, the random port number becomes an established/related connection. I could be wrong. It's been a long time since I've messed with all this.
I found this while searching the mountd man pages:
-P portnum or --port portnum
Makes mountd listen on port portnum instead of some random port.
By default, mountd will listen on the mount/udp port specified
in /etc/services, or, if that is undefined, on some arbitrary
port number below 1024.
(note the CAPITAL "P")
I looked in /etc/services (on jaunty) and saw this:
sunrpc 111/tcp portmapper # RPC 4.0 portmapper
sunrpc 111/udp portmapper
...
nfs 2049/tcp # Network File System
nfs 2049/udp # Network File System
Do you think it would wok if you were to open those ports in the firewall (assuming you haven't already)? I think that once the connection is established, the random port number becomes an established/related connection. I could be wrong. It's been a long time since I've messed with all this.