Date: Thu, 28 Sep 2017 19:08:04 +0200 From: Erwan Legrand <freebsd@erwanlegrand.com> To: Mario Lobo <lobo@bsd.com.br> Cc: freebsd-fs@freebsd.org, FreeBSD questions <freebsd-questions@freebsd.org> Subject: Re: mount_smbfs question (re-post) Message-ID: <CA%2B4G5KZwp=3nQfs7pj5fkB-sLErJ6i-jiF4cTyUkBecDZjTdig@mail.gmail.com> In-Reply-To: <CA%2ByoEx8kVpoHrZOv5fCSa6=YaaCQ3YWJUQtYiPVhqR6ZnjufCg@mail.gmail.com> References: <20170927100635.7b56f8fd@Papi.lobos> <CA%2B4G5KZP5TsGk53Wvf3SYCHwbTDry21qxa=0Sq%2BH5-voZWeumQ@mail.gmail.com> <CA%2ByoEx8kVpoHrZOv5fCSa6=YaaCQ3YWJUQtYiPVhqR6ZnjufCg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 28, 2017 at 4:16 PM, Mario Lobo <lobo@bsd.com.br> wrote: > 2017-09-27 11:20 GMT-03:00 Erwan Legrand <freebsd@erwanlegrand.com>: >> On Wed, Sep 27, 2017 at 3:06 PM, Mario Lobo <mlobo@digiart.art.br> wrote: >> > Since my environment is tottaly surrounded with shares that no longer >> > accept SMBv1 (Windows, Linux AND FreeBSD servers), so basically in the >> > end, what I'm really looking for is a confirmation that I'll just have >> > to dump all Freebsd samba clients because the OS can't deal with SMBv2 >> > or above. >> >> Perhaps have a look at implementations of SMB on top of FUSE? >> >> http://portsmon.freebsd.org/portoverview.py?category=sysutils&portname=fusefs-smbnetfs > > I did. Same problem. > smbnetfs only works with SMBv1 > It is based on libsmbclient, thus it should support SMB2 if smb.conf allows it. According to the following thread, the client protocol is resticted to SMB1 by default: https://lists.samba.org/archive/samba-technical/2016-November/thread.html#116999 This might be fixed by setting "client max protocol = SMB2" in smb.conf. ($HOME/.smb/smb.conf in this case?)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B4G5KZwp=3nQfs7pj5fkB-sLErJ6i-jiF4cTyUkBecDZjTdig>