".local" required in SMB hosts on 64bit

[the_bertrum]

Just an observation in case it trips anyone else.

I've upgraded one of my players to the 64bit 8.1 image, and on restoring from a backup my NAS would no longer mount.  The log tells me it can't identify the host.  Having seen this before, I tried "<HOST>.local/<folder>" (that is, adding .local to the end of the hostname) and it worked.
The .local suffix isn't needed on 8.1 32bit however.

[hestehandler]

Where do I even select the 64-bit kernel? I can’t find it!

And a NB on the use of *.local domains:
For local network naming convention (RFC 8375) we (the world) should use *.home.arpa
https://www.rfc-editor.org/rfc/rfc8375.html

But alas, people (of the world) use *.local even though that is an informalism.
https://www.rfc-editor.org/rfc/rfc6762#appendix-G

[the_bertrum]

Where do I even select the 64-bit kernel? I can’t find it!

You need to download the 64bit image from the moOde homepage and do a fresh installation.

[TheOldPresbyope]

...
And a NB on the use of *.local domains:
For local network naming convention (RFC 8375) we (the world) should use *.home.arpa
https://www.rfc-editor.org/rfc/rfc8375.html

But alas, people (of the world) use *.local even though that is an informalism.
https://www.rfc-editor.org/rfc/rfc6762#appendix-G

I think you have the cart before the horse. With RFC8375 the IETF hoped to stop the common usage of .home as a top-level domain in residential networks. You can consult the historical documents to see how .home causes problems.

The use of .local as a pseudo-TLD for mDNS and its recognition by the IETF predates RFC8375 by years.

As we used to say at my long-time employer, NIST, the wonderful thing about standards is there's so many of them (insert obligatory XKCD cartoon here) 

Regards,
Kent

[hestehandler]

Where do I even select the 64-bit kernel? I can’t find it!

You need to download the 64bit image from the moOde homepage and do a fresh installation.

Ahh, so it is split up now. That explains it, thanks.

[TheOldPresbyope]

Just an observation in case it trips anyone else.

I've upgraded one of my players to the 64bit 8.1 image, and on restoring from a backup my NAS would no longer mount.  The log tells me it can't identify the host.  Having seen this before, I tried "<HOST>.local/<folder>" (that is, adding .local to the end of the hostname) and it worked.
The .local suffix isn't needed on 8.1 32bit however.

Interesting.

I don't run a local DNS server on my LAN (don't ask) and wouldn't have noticed this issue because I have to use mDNS for everything.

However, I now have 2 RPI3As set up side by side, one running 32-bit moOde 8.1 and the other 64-bit moOde 8.1.

Host OMV-HC1 runs my OpenMediaVault NAS. Here's what pinging from the two moOde players gets me

Code:

#32-bit#

pi@m81pi3a32:/etc $ ping -c 1 omv-hc1
PING omv-hc1 (10.0.0.2) 56(84) bytes of data.
64 bytes from omv-hc1.local (10.0.0.2): icmp_seq=1 ttl=64 time=4.64 ms
--- omv-hc1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 4.635/4.635/4.635/0.000 ms

#64-bit#

pi@m81pi3a64:/etc $ ping -c 1 omv-hc1

ping: omv-hc1: Name or service not known

Obviously the name services are behaving subtly differently on the two builds. Will investigate.

Regards,
Kent