From owner-freebsd-fs@freebsd.org Mon Oct 2 19:59:52 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79142E26461 for ; Mon, 2 Oct 2017 19:59:52 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-qt0-x242.google.com (mail-qt0-x242.google.com [IPv6:2607:f8b0:400d:c0d::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A03D759E9 for ; Mon, 2 Oct 2017 19:59:51 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by mail-qt0-x242.google.com with SMTP id e19so268900qta.2 for ; Mon, 02 Oct 2017 12:59:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:in-reply-to:references:from:date:message-id:subject:cc; bh=grv+AiG+uwyDRqwa3FyQUYqCMG9R2MiDTUvPkiKvUTY=; b=WdyHvHyxH7VBrobO/q14Q4OQiOoFI3YwT/yj0WK8pDUOzk04Thx14NWW3SnQQshyzd zZXqx8WE0u3DkHGRR0pVhWahB2dzdyoDVqVikob1EbOkeuf2wTlkeJhfDJYED8MZhLlk AHYjaha1dc0B0OSy2wO2GYKIntEcNZuW0RPF8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:cc; bh=grv+AiG+uwyDRqwa3FyQUYqCMG9R2MiDTUvPkiKvUTY=; b=fTOk1W6h3T5xgpdGSgXgVJYaRdRk9dfm0lRP0f0tAqNGyFTkqsZxHsITOU32g1TOBi ljRmWNfa3QV0MXfwPM7/VZgeVXVOG5x9986PgTYskvL1EYnq6fh4idHsPxU6wnhdJA/t S5xEgn3efaHAsRbKk2gXKajZ8G7/PqmCV+B8lZ+coMlq3FEgoMmR/ey0VemFSHt34Qo+ uwLZgXFabP6/mLIQDXu2GZRaKCT0zlJrf0DiDiLWuk2AbMIP42BNqDgw1EM0+8yRWav4 Tcen0CS2hvMrD0shS4hZR7EwnJhw966P+2z/3JRaVZn+ry6Y+OPfOK29htuUv9b4GLDn LgtQ== X-Gm-Message-State: AHPjjUjOQTihF3zWJPI7IBfNkyAL2JN4ar/i2cxYSgf5bkpX/aHzHbUZ 45v+y5QYUKJOUO74tzuSkEnoP/+U2SphQR+ZRyfRVA== X-Received: by 10.129.57.3 with SMTP id g3mt13576002ywa.433.1506974390689; Mon, 02 Oct 2017 12:59:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.179.130 with HTTP; Mon, 2 Oct 2017 12:59:50 -0700 (PDT) In-Reply-To: <20170928184101.55c8a0ec@Papi.lobos> References: <20170927100635.7b56f8fd@Papi.lobos> <20170928184101.55c8a0ec@Papi.lobos> From: Mario Lobo Date: Mon, 2 Oct 2017 16:59:50 -0300 Message-ID: Subject: Re: mount_smbfs question (re-post) Cc: freebsd-fs@freebsd.org, FreeBSD questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 19:59:52 -0000 2017-09-28 18:41 GMT-03:00 Mario Lobo : > On Thu, 28 Sep 2017 17:48:23 -0300 > Mario Lobo wrote: > > > 2017-09-28 17:20 GMT-03:00 Ronald Klop : > > > > > On Thu, 28 Sep 2017 19:08:04 +0200, Erwan Legrand < > > > freebsd@erwanlegrand.com> wrote: > > > > > > On Thu, Sep 28, 2017 at 4:16 PM, Mario Lobo > > > wrote: > > >> > > >>> 2017-09-27 11:20 GMT-03:00 Erwan Legrand > > >>> : > > >>>> On Wed, Sep 27, 2017 at 3:06 PM, Mario Lobo > > >>>> 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@freebsd.org mailing list > > >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs > > >> To unsubscribe, send any mail to > > >> "freebsd-fs-unsubscribe@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!!]