(09-21-2022, 04:10 PM)didier573 Wrote:

(09-21-2022, 03:57 PM)Tim Curtis Wrote: Correct, thats how the config should look.

Could be some sort of network issue. The command below performs the equivalent of a SCAN.

Code:

moodeutl -N

Also, since NFS mounts are by IP address the NFS server pi has to have a persistent IP address. If the address changes the NFS mounts will break. Typically you would assign a DHCP address reservation in your Router for that pi.

Here is the result :

pi@moodeNAS:~ $ moodeutl -N
Scanning network for NFSv4 hosts...                                                                                                                                                                  
pi@moodeNAS:~ $

Same result on the endpoint side : 

pi@moodeEND:~ $ moodeutl -N
Scanning network for NFSv4 hosts...                                                                                                                                                                  
pi@moodeEND:~ $

I've already assigned static IP for the both pi on my router  
And I've also opened the 2049 port (not sure that it helps, but...)

(09-21-2022, 04:30 PM)Tim Curtis Wrote:

(09-21-2022, 04:10 PM)didier573 Wrote:

(09-21-2022, 03:57 PM)Tim Curtis Wrote: Correct, thats how the config should look.

Could be some sort of network issue. The command below performs the equivalent of a SCAN.

Code:

moodeutl -N

Also, since NFS mounts are by IP address the NFS server pi has to have a persistent IP address. If the address changes the NFS mounts will break. Typically you would assign a DHCP address reservation in your Router for that pi.

Here is the result :

pi@moodeNAS:~ $ moodeutl -N
Scanning network for NFSv4 hosts...                                                                                                                                                                  
pi@moodeNAS:~ $

Same result on the endpoint side : 

pi@moodeEND:~ $ moodeutl -N
Scanning network for NFSv4 hosts...                                                                                                                                                                  
pi@moodeEND:~ $

I've already assigned static IP for the both pi on my router  
And I've also opened the 2049 port (not sure that it helps, but...)

Below are the commands behind moodeutl -N. I'm assuming your subnet is 192.168.1.0/24

Code:

sudo nmap -Pn -p 2049 192.168.1.0/24 -oG /tmp/nmap.scan >/dev/null

cat /tmp/nmap.scan | grep "2049/open"

# The full list
cat /tmp/nmap.scan

(09-21-2022, 06:31 PM)Tim Curtis Wrote: Are u clicking the dropdown list after the SCAN completes?

(09-21-2022, 06:31 PM)Tim Curtis Wrote: Are u clicking the dropdown list after the SCAN completes?

(09-21-2022, 08:29 PM)didier573 Wrote:

(09-21-2022, 06:31 PM)Tim Curtis Wrote: Are u clicking the dropdown list after the SCAN completes?

What do you think about that : 
 




?

(09-21-2022, 09:29 PM)Tim Curtis Wrote:

(09-21-2022, 08:29 PM)didier573 Wrote:

(09-21-2022, 06:31 PM)Tim Curtis Wrote: Are u clicking the dropdown list after the SCAN completes?

What do you think about that : 
 




?

That service is not needed for NFS server.

Try the command below on the IP address of the pi running NFS server 192.168.1.18

Code:

sudo showmount --exports --no-headers 192.168.1.18

# Example
pi@moode:~ $ sudo showmount --exports --no-headers 192.168.1.199
/media/VFAT128 192.168.1.0/24

(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-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 ?