Is there a reason why NFS can't be set to use fixed ports by default? I
don't see a security issue because rpcinfo gives you the ports anyway,
so if you can connect to RPC you can find the ports; obviously you'd
need to ensure that they didn't conflict with anything else, but
hopefully that's
Ok, after playing around with this, I'm getting there. I want to
document this here, so at least others and even myself can benefit from
this in the future. I added this line: options lockd nlm_udpport=4045
nlm_tcpport=4045to /etc/modprobe.d/options.conf the port number
can really be
Ok, after playing around with this, I'm getting there. I want to
document this here, so at least others and even myself can benefit from
this in the future. I added this line: options lockd nlm_udpport=4045
nlm_tcpport=4045to /etc/modprobe.d/options.conf the port number
can really be
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
ok got it. I put up a small how-to here:
http://ubuntuforums.org/showpost.php?p=7959294postcount=17
Hope this helps.
Shane
--
need way to specify the lockd port
https://bugs.launchpad.net/bugs/28706
You received this bug notification because you are a member of Ubuntu
Server Team, which is a
Excellent post! Thanks for making the how-to, Shane. You may want to
consider posting this to the Ubuntu wiki, with a title something like,
Making NFS work with Ubuntu-CE-Firewall. That would make it a little
easier to find.
--
need way to specify the lockd port
This is still a very relevant problem. I'm working on Ubuntu Jaunty,
and cannot get NFS to connect through an iptables firewall because the
ports keep changing. The changing ports are: nlockmgr and mountd, I
don't know if status has to do with this or not, but this is a problem.
All the links I
Oh, one thing: modules.conf is the wrong file. I meant modprobe.conf.
--
need way to specify the lockd port
https://bugs.launchpad.net/bugs/28706
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
--
Ubuntu-server-bugs mailing list
@DaneM - Thanks for the info, I didn't realize the old info was still
good to go by.
It would be good to have something up on the Ubuntu docs page, that is
usually where I look for info. If someone could write up a short how
to, that would be great, at least the info would be out there and
ack...AleksanderAdamowski already posted on this. modprobe.conf
*should* work, but /etc/modprobe.d/options is probably a better choice.
Anyway, I agree that there should be something done about this as per
Shane Rice's suggestion. Perhaps edit the config files by default when
installing the nfs
My first attempt gave me this:
sudo modprobe lockd
WARNING: /etc/modprobe.conf line 1: ignoring bad line starting with
'lockd.nlm_udpport=4001'
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
into /etc/modprobe.d/.
So instead of using modprobe.conf, I used
** Changed in: nfs-utils (Ubuntu)
Status: New = Confirmed
--
need way to specify the lockd port
https://bugs.launchpad.net/bugs/28706
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
--
Ubuntu-server-bugs mailing list
12 matches
Mail list logo
