(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
pi@moodeNAS:~ $ cat /tmp/nmap.scan | grep "2049/open"
Host: 192.168.1.18 (moodeend.home) Ports: 2049/open/tcp//nfs///
pi@moodeNAS:~ $ cat /tmp/nmap.scan
# Nmap 7.80 scan initiated Wed Sep 21 18:47:00 2022 as: nmap -Pn -p 2049 -oG /tmp/nmap.scan 192.168.1.0/24
Host: 192.168.1.1 (livebox.home) Status: Up
Host: 192.168.1.1 (livebox.home) Ports: 2049/filtered/tcp//nfs///
Host: 192.168.1.14 (imac-de-didier.home) Status: Up
Host: 192.168.1.14 (imac-de-didier.home) Ports: 2049/closed/tcp//nfs///
Host: 192.168.1.18 (moodeend.home) Status: Up
Host: 192.168.1.18 (moodeend.home) Ports: 2049/open/tcp//nfs///
Host: 192.168.1.17 (moodenas.home) Status: Up
Host: 192.168.1.17 (moodenas.home) Ports: 2049/closed/tcp//nfs///
# Nmap done at Wed Sep 21 18:47:07 2022 -- 256 IP addresses (8 hosts up) scanned in 7.69 seconds
But it stil doesn't work...
What seems surprising for me : 2049 is open for moodeend (my endpoint) but not for moodenas (my NAS).