Moode Forum
NAS discovery - Printable Version

+- Moode Forum (http://moodeaudio.org/forum)
+-- Forum: moOde audio player (http://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (http://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: NAS discovery (/showthread.php?tid=839)



NAS discovery - Hiroyuki - 12-27-2018

Hi all,

Running Moode 4.4 2018-12-19
Not any critical, but I like to hear from you about the NAS discovery.
I am running home NAS called ODROIDXU4 with OpenMediaVault.
When I try to discover the NAS using SCAN from web interface, it surely detects it but mount op fails.
I ended up with adding manually ".local" suffix to the name and Moode can mount successfully.
Am I missing any module for the Samba name discovery?
From the File Explorer of Windows 10, I can access this NAS without .local suffix.

https://gyazo.com/ed77ca72a647a150e2ae58e60251bbd2
The bottom two of pull down are for my NAS name

Thanks,
Hiroyuki


RE: NAS discovery - Tim Curtis - 12-27-2018

It looks like Samba discovery worked fine but name resolution for the host ODROIDXU4 failed. This is typically due to some sort of network or NAS configuration issue.

When you run the cmd below on the Pi does it return the IP address of the NAS?
Code:
ping ODROIDXU4



RE: NAS discovery - Hiroyuki - 12-27-2018

(12-27-2018, 01:56 PM)Tim Curtis Wrote: It looks like Samba discovery worked fine but name resolution for the host ODROIDXU4 failed. This is typically due to some sort of network or NAS configuration issue.

When you run the cmd below on the Pi does it return the IP address of the NAS?
Code:
ping ODROIDXU4

here's the PING results both with/without local
pi@moode:~ $ ping odroidxu4
ping: odroidxu4: Name or service not known
pi@moode:~ $
pi@moode:~ $ ping odroidxu4.local
PING odroidxu4.local (192.168.0.64) 56(84) bytes of data.
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=1 ttl=64 time=6.48 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=2 ttl=64 time=7.35 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=3 ttl=64 time=6.96 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=4 ttl=64 time=2.59 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=5 ttl=64 time=5.94 ms


RE: NAS discovery - TheOldPresbyope - 12-27-2018

(12-27-2018, 02:06 PM)Hiroyuki Wrote:
(12-27-2018, 01:56 PM)Tim Curtis Wrote: It looks like Samba discovery worked fine but name resolution for the host ODROIDXU4 failed. This is typically due to some sort of network or NAS configuration issue.

When you run the cmd below on the Pi does it return the IP address of the NAS?
Code:
ping ODROIDXU4

here's the PING results both with/without local
pi@moode:~ $ ping odroidxu4
ping: odroidxu4: Name or service not known
pi@moode:~ $
pi@moode:~ $ ping odroidxu4.local
PING odroidxu4.local (192.168.0.64) 56(84) bytes of data.
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=1 ttl=64 time=6.48 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=2 ttl=64 time=7.35 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=3 ttl=64 time=6.96 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=4 ttl=64 time=2.59 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=5 ttl=64 time=5.94 ms

This is a problem with your LAN's DNS service. It's not providing the IP address that corresponds to the hostname "odroidxu4". When you add ".local" to the hostname you are switching from DNS to mDNS which handles hostname resolution differently.

Regards,
Kent


RE: NAS discovery - Hiroyuki - 12-27-2018

(12-27-2018, 02:23 PM)TheOldPresbyope Wrote:
(12-27-2018, 02:06 PM)Hiroyuki Wrote:
(12-27-2018, 01:56 PM)Tim Curtis Wrote: It looks like Samba discovery worked fine but name resolution for the host ODROIDXU4 failed. This is typically due to some sort of network or NAS configuration issue.

When you run the cmd below on the Pi does it return the IP address of the NAS?
Code:
ping ODROIDXU4

here's the PING results both with/without local
pi@moode:~ $ ping odroidxu4
ping: odroidxu4: Name or service not known
pi@moode:~ $
pi@moode:~ $ ping odroidxu4.local
PING odroidxu4.local (192.168.0.64) 56(84) bytes of data.
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=1 ttl=64 time=6.48 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=2 ttl=64 time=7.35 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=3 ttl=64 time=6.96 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=4 ttl=64 time=2.59 ms
64 bytes from 192.168.0.64 (192.168.0.64): icmp_seq=5 ttl=64 time=5.94 ms

This is a problem with your LAN's DNS service. It's not providing the IP address that corresponds to the hostname "odroidxu4". When you add ".local" to the hostname you are switching from DNS to mDNS which handles hostname resolution differently.

Regards,
Kent

hi Kent, thanks
i like to make sure i am not going wrong direction, you meant my home router config is the place i should look in to?


RE: NAS discovery - TheOldPresbyope - 12-27-2018

(12-27-2018, 02:39 PM)Hiroyuki Wrote:
(12-27-2018, 02:23 PM)TheOldPresbyope Wrote: This is a problem with your LAN's DNS service. It's not providing the IP address that corresponds to the hostname "odroidxu4". When you add ".local" to the hostname you are switching from DNS to mDNS which handles hostname resolution differently.

Regards,
Kent

hi Kent, thanks
i like to make sure i am not going wrong direction, you meant my home router config is the place i should look in to?

Yes, but there's no rush since you can enter "odroidxu4.local" manually into the NAS Config panel.

In my case, the DNS service in the router provided by my ISP assumes that a bare hostname exists in the local domain (".fios-router.home" by default; but I can change it) and tries to resolve it using the local address table it generates dynamically as hosts are added to the LAN. If I ping "moode", for example, I get back both the IP address  and the fully qualified domain name "moode.fios-router.home".

If the DNS service in the router can't find an address in its local address table, for example because I mistyped the name ("mooode" instead of "moode", say), then it kicks the name resolution query up to the ISP's DNS service. This can lead to weird results such as returning an IP address on the external network.

Regards,
Kent


RE: NAS discovery - Hiroyuki - 01-02-2019

(12-27-2018, 03:23 PM)TheOldPresbyope Wrote:
(12-27-2018, 02:39 PM)Hiroyuki Wrote:
(12-27-2018, 02:23 PM)TheOldPresbyope Wrote: This is a problem with your LAN's DNS service. It's not providing the IP address that corresponds to the hostname "odroidxu4". When you add ".local" to the hostname you are switching from DNS to mDNS which handles hostname resolution differently.

Regards,
Kent

hi Kent, thanks
i like to make sure i am not going wrong direction, you meant my home router config is the place i should look in to?

Yes, but there's no rush since you can enter "odroidxu4.local" manually into the NAS Config panel.

In my case, the DNS service in the router provided by my ISP assumes that a bare hostname exists in the local domain (".fios-router.home" by default; but I can change it) and tries to resolve it using the local address table it generates dynamically as hosts are added to the LAN. If I ping "moode", for example, I get back both the IP address  and the fully qualified domain name "moode.fios-router.home".

If the DNS service in the router can't find an address in its local address table, for example because I mistyped the name ("mooode" instead of "moode", say), then it kicks the name resolution query up to the ISP's DNS service. This can lead to weird results such as returning an IP address on the external network.

Regards,
Kent
I looked into my home router settings, yet to find how i can live without .local suffix
Today i had a chance to run the latest ver of Volumio on another RPi, and don't know why but it can find my NAS name with/without .local suffix.
Confused
Something on my home router is not compatible with Moode...

Code:
volumio@volumio:~$ sudo ping odroidxu4
PING odroidxu4 (192.168.0.64) 56(84) bytes of data.
64 bytes from 192.168.0.64: icmp_seq=1 ttl=64 time=1.17 ms
64 bytes from 192.168.0.64: icmp_seq=2 ttl=64 time=0.914 ms
^C
volumio@volumio:~$ sudo ping odroidxu4.local
PING odroidxu4.local (192.168.0.64) 56(84) bytes of data.
64 bytes from 192.168.0.64: icmp_seq=1 ttl=64 time=1.36 ms
64 bytes from 192.168.0.64: icmp_seq=2 ttl=64 time=0.930 ms
^C



RE: NAS discovery - Onionhead - 01-02-2019

For the past 3 yrs. I have been using moOde primarily however, on occasion Volumio. I have never been able to detect Synology NAS with SAMBA with either moOde or Volumio. Not really sure if my wifi network (ORBI mesh router) or my NAS config are to blame. I can tell you that NFS has worked very nicely with manual setup using moOde or Volumio. I have not really pursued a SAMBA solution as my IT/Networking/Server skills are minimal. Let me know if you have questions about NFS.