mount_smbfs question (re-post)

[Mario Lobo]

2017-09-28 18:41 GMT-03:00 Mario Lobo <lobo at bsd.com.br>:

> On Thu, 28 Sep 2017 17:48:23 -0300
> Mario Lobo <lobo at bsd.com.br> wrote:
>
> > 2017-09-28 17:20 GMT-03:00 Ronald Klop <ronald-lists at klop.ws>:
> >
> > > On Thu, 28 Sep 2017 19:08:04 +0200, Erwan Legrand <
> > > freebsd at erwanlegrand.com> wrote:
> > >
> > > On Thu, Sep 28, 2017 at 4:16 PM, Mario Lobo <lobo at bsd.com.br>
> > > wrote:
> > >>
> > >>> 2017-09-27 11:20 GMT-03:00 Erwan Legrand
> > >>> <freebsd at erwanlegrand.com>:
> > >>>> On Wed, Sep 27, 2017 at 3:06 PM, Mario Lobo
> > >>>> <mlobo at 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=sysutil
> > >>>> s&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-Novembe
> > >> r/thread.html#116999
> > >>
> > >> This might be fixed by setting "client max protocol = SMB2" in
> > >> smb.conf. ($HOME/.smb/smb.conf in this case?)
> > >>
> > >
> > > I'd suggest setting "client min protocol".
> > >                             ^^^
> > >
> > > Regards,
> > > Ronald.
> > >
> > >
> > > _______________________________________________
> > >> freebsd-fs at freebsd.org mailing list
> > >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs
> > >> To unsubscribe, send any mail to
> > >> "freebsd-fs-unsubscribe at freebsd.org"
> > >
> > I just tested it!
> >
> > 2 shares. 1 with SMBv1 and 1 with client min protocol=SMBv2
> > They are both SAMBA with FREEBSD.
> >
>

 [snip]


> > Unless I'm missing some tuning option in smbnetfs for SMBv2 and above,
> > It doesen't work!
> >
> > Thanks,
> >
>
> One more thing.
>
> If I gear down the second server to SMBv1, I can access it just fine.
>
> --
>

Well, after wearing my eyes off everywhere I could looking for a solution
to this issue, I came to the conclusion that accessing an SMBv2+ share
with FreeBSD is on a limbo that I can't reach. And it is dormant.

I am a stubborn person so I started looking at the OS source code but so
far it is way beyond me. I can't even make out how it currently works, and
much less
implement two new protocols on top of it. But I'll keep going forward ...

I also can't find anything other than mount_smbfs and smbnetfs that can
access smb shares, and much less integrate with the OS as they do.

As much as it breaks my heart to drop a reliable, fast and stable OS
because of this ONE issue, on my current environment its seems to be my
only choice left.

Thanks to all that tried to help.

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!]