I’m having problems with NFS on all machines.
Prior with the version 13.1, the network with NFS worked perfectly, but after updates no longer work.
I tried to get help in another tread, but got no answer to solve the problem.
So I formatted 2 machines and did a fresh install with a new download of LEAP version
The firewall is off, the files exports, hosts and fstab are perfect
But the problem remains. So I think OpenSuse no longer supports NFS, because it does not work in a new system and newly installed.
Do OpenSuse administrators do not care more for NFS?
Please, someone knows something about this problem?
It’s hard to know what’s the problem you are having, when you gave very little information.
I’m typing this on my Leap 42.1 desktop, which I have setup as an NFS server. I set it up pretty much the same way that I had setup 13.1 and 13.2 as servers when I was running those versions.
I have three other computer running 42.1 that are NFS clients. And NFS is working well for them.
On the server, I installed “nfs-kernel-server” and “yast2-nfs-server”. On the clients, I did not have to install anything special. The NFS client components were part of a standard install.
You need to tell us what you did, and how you decided that it wasn’t working.
On Wed, 06 Jan 2016 00:16:02 +0000, sergelli wrote:
> perfect But the problem remains. So I think OpenSuse no longer supports
> NFS, because it does not work in a new system and newly installed.
> Do OpenSuse administrators do not care more for NFS?
You would be incorrect that nobody cares about it - just based on the
fact that your setup isn’t working.
Instead of conjecture that the project doesn’t care about NFS, describe
exactly what you’re doing and what the output is when you try to (for
example) mount an exported filesystem. What do you see in the logs?
I use NFS on my Leap 42.1 systems every day, and it works fine - but
there are some tricks that you may need to use if you’re using a firewall
(for example).
It is your problem not ours. I have it working without issue, but perhaps something unique with the configuration of your Leap machine(s)? Can you describe the problem more explicitly. Preferably, use commands to show what is not working, and/or what is expected.
In fairness to the OP, there are some things you have had to do in the
past for the RPC portmapper if you’ve got the firewall enabled, since the
ports for statd and lockd (as I recall, I may not be remembering the
specific services correctly) use dynamically allocated ports. I’ve found
in my setups that just enabling NFS in the firewall isn’t sufficient, so
it may be that that’s what the OP is running into.
Since my systems run all the time, I simply shut the firewall off when
mounting the exported filesystems - once mounted, the ports don’t need to
be open - but I would like a better solution than what I’m currently
doing.
AFAIR, the general advice for those running behind firewalls is to configure static ports /etc/sysconfig/nfs for those RPC services, and configure the firewall accordingly, but maybe there’s more to it than that?
Since my systems run all the time, I simply shut the firewall off when
mounting the exported filesystems - once mounted, the ports don’t need to
be open - but I would like a better solution than what I’m currently
doing.
Yes, I guess that’s one pragmatic approach. I only infrequently use NFS (mostly to test or assist others), so usually just cheat by dropping the firewall temporarily when required.
On Wed, 06 Jan 2016 21:16:01 +0000, deano ferrari wrote:
> AFAIR, the general advice for those running behind firewalls is to
> configure static ports /etc/sysconfig/nfs for those RPC services, and
> configure the firewall accordingly, but maybe there’s more to it than
> that?
I think that’s all that’s needed, but I haven’t gone through the process
of setting that up. I probably need to do that anyways - hoping to get
more automation in general in my own setup.
I’ll take a closer look at it this weekend and see if there’s anything
else that needs to be done.
> Yes, I guess that’s one pragmatic approach. I only infrequently use NFS
> (mostly to test or assist others), so usually just cheat by dropping the
> firewall temporarily when required.
Yeah. The biggest problem is when applying updates - and getting my
startup sequence ordered properly, because I don’t auto-mount the volumes
(they’re encrypted) on the NFS server side.
Bringing the firewall down has the unintended side effect of messing up
Docker’s networking, too, so fixing that is kinda important for my
setup.
Actually this is strange because you need to at least enable rpcbind (socket or service - in the past there were some timing issues with socket activation). All services are disabled after new install.
I did not say you need to install something. I said you need to enable something after installation. It qualifies as “something special” in my vocabulary especially as enabling systemd units is not yet common knowledge and it was not necessary to explicitly enable rpcbind in the past.
I have found this thread, when trying to educate myself how to do things in SUSE.
Was useful - once I have disabled firewall, it took all of 10 sec to connect to my NAS using NFS.
I am impressed with SUSE so far
I am finding more serious problems with the Leap
I will try to resolve them before the problem I’m having with NFS
Later back here to solve the NFS
Thank you all for the help
