05-17-2025, 11:19 PM
Mounting CIFS is a bundle of joy when it comes to version definition ?
So I guess the advice is to pick a dialect that matches and then rewrite it according to the vers arguments valid values.
E.g.
202 = 2.0
210 = 2.1
300 = 3.0
302 = 3.0.2 or 3.02
Yay! lol
Code:
man mount.cifs
Quote: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 initial re‐
lease 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.
So I guess the advice is to pick a dialect that matches and then rewrite it according to the vers arguments valid values.
E.g.
202 = 2.0
210 = 2.1
300 = 3.0
302 = 3.0.2 or 3.02
Yay! lol