(09-21-2022, 11:52 PM)TheOldPresbyope Wrote: @Tim Curtis

An easier check of the active exports on an NFS server is sudo exportfs

For example, on my moOde 8.2.0 player with NFS server enabled and exporting a USB stick labeled RALLY8GB

Code:

pi@m82arm64:~ $ sudo exportfs
/media/RALLY8GB
        <world>

Note, this is with the "default" Access setting. If I set Access to just my entire LAN, then instead of <world> one sees what I set: 10.0.0.0/24.


@didier573

1) It's a very bad idea to open port 2049 at your firewall, e.g., your router. This leaves you open to attacks from the outside world. The Internet is under siege by bad guys running what are called "port knocker" programs.

2) if you have enabled NFS file-sharing in System Config on your host moodeNAS then it should have port 2049 open even if you do not have any exportable USB storage devices connected. There's something not right here since you report

Code:

Host: 192.168.1.17 (moodenas.home)      Ports: 2049/closed/tcp//nfs///

3) you do not have to enable NFS file-sharing on your host moodeEND. It's a server setting, not a client setting.
Regards,
Kent

(09-22-2022, 09:43 AM)Falco Wrote:

(09-21-2022, 06:20 AM)didier573 Wrote:

(09-20-2022, 06:25 PM)didier573 Wrote: I face exactly the same issue.
SMB is working fine in my configuration but I don't know how to proceed with NFS and I'd like to try it.

I use two Raspberries, one as an Endpoint (WiFi connected to my network) and another one as a NAS using moOde, a USB SDD and also WiFi connected.
I can see the directories from my mac Finder to upload new files. So, everything is ok using SMB.

Could someone explain step by step how to proceed with NFS ?

Hello,

Just to clarify what I did. On the NAS side I turned on SMB and NFS. I also specified the subnet allowed to access to ressources (192.168.1.0/24 in my case).
On the endpoint side, when I launch a scan for SMB path I get answers. Nothing when I do the same scan with NFS.

No one using NFS or interested in using it ?

I see further down the thread that you're already investigating a lot together with Tim and Kent.

However I just wanted to share that I have a similar setup with 2 MoOde RPi's. To one of them a USB SSD is connected with music. I also want to share that on the network. So at first I did not know that SMB and NFS server had to be activated. After activating SMB server it ran flawlessly.

Then I decided to try NFS as that should give a little bit less overhead traffic on Linux. Only thing I did was activating NFS, did not specify any subnet or anything and for me it worked instantly. With SCAN I got the server and could connect to it. With update library I saw all music files and they also play instantly over the network. Both players are on the same subnet, which is 192.168.1.x for me.

Maybe first try to only active NFS server and not specify a subnet etc?

(09-22-2022, 01:05 PM)Tim Curtis Wrote:

(09-21-2022, 11:52 PM)TheOldPresbyope Wrote: @Tim Curtis

An easier check of the active exports on an NFS server is sudo exportfs

For example, on my moOde 8.2.0 player with NFS server enabled and exporting a USB stick labeled RALLY8GB

Code:

pi@m82arm64:~ $ sudo exportfs
/media/RALLY8GB
        <world>

Note, this is with the "default" Access setting. If I set Access to just my entire LAN, then instead of <world> one sees what I set: 10.0.0.0/24.


@didier573

1) It's a very bad idea to open port 2049 at your firewall, e.g., your router. This leaves you open to attacks from the outside world. The Internet is under siege by bad guys running what are called "port knocker" programs.

2) if you have enabled NFS file-sharing in System Config on your host moodeNAS then it should have port 2049 open even if you do not have any exportable USB storage devices connected. There's something not right here since you report

Code:

Host: 192.168.1.17 (moodenas.home)      Ports: 2049/closed/tcp//nfs///

3) you do not have to enable NFS file-sharing on your host moodeEND. It's a server setting, not a client setting.
Regards,
Kent

@TheOldPresbyope, the showmount command is run on the client while exportfs would be run on the server.

To verify the server is working check its status via systemd.

Code:

systemctl status nfs-server

# Example
pi@trx:~ $ systemctl status nfs-server
● nfs-server.service - NFS server and services
     Loaded: loaded (/lib/systemd/system/nfs-server.service; disabled; vendor preset: enabled)
     Active: active (exited) since Tue 2022-09-20 15:54:44 EDT; 1 day 17h ago
    Process: 944 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
    Process: 945 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0/SUCCESS)
   Main PID: 945 (code=exited, status=0/SUCCESS)
        CPU: 476ms

pi@trx:~ $ sudo exportfs
/media/VFAT128  192.168.1.0/24

(09-22-2022, 06:30 PM)Tim Curtis Wrote: It looks like you turned on NFS on the client (moodeEND). It should be the NAS (moodeNAS) where NFS gets turned on.

(09-22-2022, 08:24 PM)Tim Curtis Wrote: Could be useful. What format is the file system on the attached USB drive?

(09-22-2022, 08:38 PM)didier573 Wrote:

(09-22-2022, 08:24 PM)Tim Curtis Wrote: Could be useful. What format is the file system on the attached USB drive?

ExFAT