What's happening with Bug 207

[lionelv]

Hi,

I've just installed Mageia 3 beta 3 and I have exactly the problem described at https://bugs.mageia.org/show_bug.cgi?id=207

I'm not sure exactly what the status of this is, last updated on 16th of January.

[oj]

Have you tried with the firewall disabled? Depending on how you're plugged into the internet, you probably don't need a firewall on individual machines.

[lionelv]

Yeah, I went to check the firewall after reading the bug description and it was already turned off.

[lionelv]

Hmmm, that was really weird. Just happened to come back to the firewall because mysql was not working and I discovered that it was back on. Now NFS is finding the servers no problems. However, the bug still mentions that there was going to be a change so that firewall exceptions were added, I'm wondering if this is still going to happen.

[oj]

IMHO NFS requires such a range of ports you may as well have no firewall. I've always wondered why the default NFS config doesn't restrict the random port range to a much narrower range. That would be a question for the upstream developers, but I suspect the answer would be "we've always done it this way."

[doktor5000]

IMHO NFS requires such a range of ports you may as well have no firewall.

Basically NFS only uses two ports, 111 for rpc and 2049 for nfs. Additionally rpc.mountd uses a dynamical port, but that can also be changed.

[oj]

except the client calls on a random high port negotiated with the portmapper. I've seen rpc.lockd etc set to specific ports, but if they aren't, random outgoing (client side) ports are used. An example of a locked down config:

Code: Select all

LOCKD_TCPPORT=32803
LOCKD_UDPPORT=32769
MOUNTD_PORT=892
RQUOTAD_PORT=875
STATD_PORT=662
STATD_OUTGOING_PORT=2020

the bottom line is for nfs to work, a lot of ports (or a range) must be open. Looking at nfs configs in sysconfig I see Mageia limits a few services to 4000-4002. But generally the default setup in most distros does not clamp down on this port use.

[lionelv]

Well I have a firewall on my router, only a very small number of ports get passed through so I think I'm safe?

Late last night I did get NFS working, but I had some big issues disabling the firewall in Mageia. I would click everything and exit and when I came back it would always be turned back on. When I went into the security section I discovered another firewall option and tried clicking everything there too, and once again if I would exit and come back it would be turned on. I don't seem to be able to disable my firewall!

[doktor5000]

Can you please open a separate thread for that firewall issue? Golden rule: one problem per thread

[lionelv]

I've actually opened a bug (9329) because the firewall isn't working for me at all. But is it a separate thread since the fire wall is what is blocking NFS!

But point taken, at this stage the bug is sufficient to submit the firewall issue.

[doktor5000]

Ahh sorry, i thought that was about the bug with NFS and name resolution. So no, this doesn't need a new thread.
But from the last comments on the bug report, should already be fixed in latest cauldron packages, or they should come in the next few days.

[lionelv]

My system is working because I changed the script as described in the bug . I just realised that I didn't say that I used the "Network installer + nonfree firmware CD". I don't know if it is important but I might add it.