Official moOde 8 support thread

[TheOldPresbyope]

...

@carmol

A log message like

Code:

CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers

is informational and not a statment of error.

From the IP address it appears you are using a file-sharing function on your router as your NAS. What is the router? How have you made sure the share name is "CD"? How have you inferred that "ntlm" is in play and the protocol level version is "1.0"?

As Phil has said, you can force these parameters in the Advanced flags settings in the Music Source screen but they have to be correct for the source.

ETA - and as Tim has said, the SCAN function does a good job of figuring out the protocol level version in play.

Regards,
Kent

router is Zyxel 8825

share name is correct,
the same configuration worked flawlessy in moode 7;
no luck with the scan function.

It seems that ntlm is not supported anymore

So moOde is just building a mount command string to pass to the Raspberry Pi OS command interpreter. Here's the relevant option descriptions taken from the man page for mount.cifs on the moOde 8 image

Code:

      vers=arg
             SMB protocol version. Allowed values are:

             • 1.0 - The classic CIFS/SMBv1 protocol.

             • 2.0 - The SMBv2.002 protocol. This was initially introduced in Windows Vista Service Pack 1, and Windows Server 2008. Note that the ini‐
               tial release version of Windows Vista spoke a slightly different dialect (2.000) that is not supported.

             • 2.1 - The SMBv2.1 protocol that was introduced in Microsoft Windows 7 and Windows Server 2008R2.

             • 3.0 - The SMBv3.0 protocol that was introduced in Microsoft Windows 8 and Windows Server 2012.

             • 3.02 or 3.0.2 - The SMBv3.0.2 protocol that was introduced in Microsoft Windows 8.1 and Windows Server 2012R2.

             • 3.1.1 or 3.11 - The SMBv3.1.1 protocol that was introduced in Microsoft Windows 10 and Windows Server 2016.

             • 3 - The SMBv3.0 protocol version and above.

             • default - Tries to negotiate the highest SMB2+ version supported by both the client and server.

             If no dialect is specified on mount vers=default is used.  To check Dialect refer to /proc/fs/cifs/DebugData

             Note too that while this option governs the protocol version used, not all features of each version are available.

             The  default since v4.13.5 is for the client and server to negotiate the highest possible version greater than or equal to 2.1. In kernels
             prior to v4.13, the default was 1.0. For kernels between v4.13 and v4.13.5 the default is 3.0.

       sec=arg
              Security mode. Allowed values are:

              • none - attempt to connection as a null user (no name)

              • krb5 - Use Kerberos version 5 authentication

              • krb5i - Use Kerberos authentication and forcibly enable packet signing

              • ntlm - Use NTLM password hashing

              • ntlmi - Use NTLM password hashing and force packet signing

              • ntlmv2 - Use NTLMv2 password hashing

              • ntlmv2i - Use NTLMv2 password hashing and force packet signing

              • ntlmssp - Use NTLMv2 password hashing encapsulated in Raw NTLMSSP message

              • ntlmsspi - Use NTLMv2 password hashing encapsulated in Raw NTLMSSP message, and force packet signing

              The default in mainline kernel versions prior to v3.8 was sec=ntlm. In v3.8, the default was changed to sec=ntlmssp.

              If the server requires signing during protocol negotiation, then it may be enabled automatically. Packet signing may also be enabled auto‐
              matically if it's enabled in /proc/fs/cifs/SecurityFlags.

Since this is all vanilla Raspberry Pi OS stuff you might be better served asking over at the Raspberry Pi Forum.

If I force my OMV Samba server to use only SMBv1 (sec=NT1) then the scan function doesn't find it but manual mounting it in moOde works whether I explicitly set vers=1.0 in the flags or not. I'm not interested in exploring security protocols such as NTLM. Perhaps someone else is.

Regards,
Kent