From: ronnie sahlberg <ronniesahlberg@gmail.com>
To: Tjernlund <tjernlund@tjernlund.se>
Cc: linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: CIFS version 1/2 negotiate ?
Date: Fri, 27 Aug 2021 04:34:44 +1000 [thread overview]
Message-ID: <CAN05THRp0AcQvgn2ro-0M12i90FMnQfBCo7AFbf1qQCF2dtUjQ@mail.gmail.com> (raw)
In-Reply-To: <bec6e1554ba990330cf812050f4b43feda92aeb9.camel@tjernlund.se>
On Wed, Aug 25, 2021 at 9:49 PM Tjernlund <tjernlund@tjernlund.se> wrote:
>
> We got an old netapp server which exposes CIFS vers=1 and when trying to mount shares
> from this netapp we get:
> CIFS: VFS: \\netapp2 Dialect not supported by server. Consider specifying vers=1.0 or vers=2.0 on mount for accessing older servers
> CIFS: VFS: cifs_mount failed w/return code = -95
>
> If I specify vers=1 manually on the mount cmd it works.
> However, GUI file managers cannot handle this and less Linux savy users don't know how to
> use the mount cmd manually.
>
> I wonder if kernel could grow a SMB1 version negotiate so a standard CIFS mount can work?
> We are at kernel 5.13 and I can test/use a kernel patch.
I don't think we can do that in the client. We are all trying to move
away from SMB1, and a lot of servers already today
have it either disabled by default or even removed from the compile.
So enabling automatic multi-protocol support for SMB1 is the wrong
direction for us.
For that reason I think there will also be pushback from GUI
filemanagers to add a "smb1 tickbox", but you can try.
Other solutions could be to locally hack and replace mount.cifs with a
patch to "detect if servername matches the old netapp and
automatically add a vers=1 to the mount argument string passed to the
kernel".
It would require you to build a patched version of cifs-utils and
distribute to all the client machines though, so ...
>
> Jocke
>
>
next prev parent reply other threads:[~2021-08-26 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 11:32 CIFS version 1/2 negotiate ? Tjernlund
2021-08-26 18:34 ` ronnie sahlberg [this message]
2021-08-26 19:18 ` Steve French
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAN05THRp0AcQvgn2ro-0M12i90FMnQfBCo7AFbf1qQCF2dtUjQ@mail.gmail.com \
--to=ronniesahlberg@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=tjernlund@tjernlund.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).