From owner-freebsd-fs@freebsd.org Thu Sep 28 21:39:19 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 B9B72E0CF9A for ; Thu, 28 Sep 2017 21:39:19 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-qk0-x244.google.com (mail-qk0-x244.google.com [IPv6:2607:f8b0:400d:c09::244]) (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 76CB56F20B for ; Thu, 28 Sep 2017 21:39:18 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by mail-qk0-x244.google.com with SMTP id g128so1904408qke.0 for ; Thu, 28 Sep 2017 14:39:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=YYTRXIuDeGWEXpdp2T83ELhnAPVEcrgYZbOQyWlCC/k=; b=EMsu0AMFZsD4m+uyHZZDAXzwz8J8EFgz4sjUv4XztGe8PanoQFVKlt2OoUEJF3mUOa XldD+wZmMc260kW6Pbax5I0zinC7NGzDooXEBEKhFpI8GICRk4pHgG8H2eWif1xJABN6 Ud6xHpmCP+zQPlEYxtBOfSwtpza92k1NXl49I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=YYTRXIuDeGWEXpdp2T83ELhnAPVEcrgYZbOQyWlCC/k=; b=hQcNKyObFZyQjs/I7BKgCDX8ao3VL/4UAuJwa2+Iid4VETHGZaCi6YiUNIlPour5uA 3e2r025E5/y8Rn+WuIU6GEqLJFgbnJvOby2sDnDX2NqmHBRe2CE7sYNPgGYa4sMyJNmk mPEFLUkJeJchUTTfmJN6auZWRTE4FXjp2Zh+2YsPEUAlsB801ykYTbXwi0+tjSYj4TAz uldIn2gVO3h8duL2rbi/TWLbelKwCe2Bbp7qdwpOK4/7SS4EDMBgLOQY/wiEwUz+xsBO RbulMsvOYmr6bls7cHogenxK2l+Bq7pews27gtsOCYh6dptwMVWIG9Ko5COq3TX1RyE9 HuUg== X-Gm-Message-State: AMCzsaWVNMp4AD0OcBTVSUOGkvkQ8mui8TQzxL5k/vUa64F8+hWU5X8f 3k5G6upUceHrXNSHQagvOWJpsg== X-Google-Smtp-Source: AOwi7QBA52j7W29GpHUJPfvjSgxHbYbcg6p+ieyavurl/usnKzhNneKLSVruqj/Hf8yP8kywjVYOQQ== X-Received: by 10.55.104.132 with SMTP id d126mr523126qkc.142.1506634757667; Thu, 28 Sep 2017 14:39:17 -0700 (PDT) Received: from Papi.lobos ([187.59.113.250]) by smtp.gmail.com with ESMTPSA id v32sm1700728qtc.66.2017.09.28.14.39.15 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 28 Sep 2017 14:39:17 -0700 (PDT) Date: Thu, 28 Sep 2017 18:41:01 -0300 From: Mario Lobo To: Ronald Klop Cc: Erwan Legrand , freebsd-fs@freebsd.org, FreeBSD questions Subject: Re: mount_smbfs question (re-post) Message-ID: <20170928184101.55c8a0ec@Papi.lobos> In-Reply-To: References: <20170927100635.7b56f8fd@Papi.lobos> Organization: BSD X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Thu, 28 Sep 2017 21:39:19 -0000 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. > > The first I can read/write anywhere in it > The second I can't even see whats in it. > > These are the msgs from running smbnetfs -d /shares > > when accessing the SMBv1 share (OK): > > unique: 1178, opcode: READLINK (5), nodeid: 11, insize: 40, pid: 36429 > readlink /SEAWAY/NEWSITE 1025 > unique: 1178, success, outsize: 26 > unique: 1179, opcode: GETATTR (3), nodeid: 1, insize: 40, pid: 36429 > getattr / > unique: 1179, success, outsize: 112 > unique: 1180, opcode: LOOKUP (1), nodeid: 12, insize: 51, pid: 36429 > LOOKUP /NEWSITE/.directory > getattr /NEWSITE/.directory > unique: 1180, error: -2 (No such file or directory), outsize: 16 > unique: 1181, opcode: READLINK (5), nodeid: 11, insize: 40, pid: 36429 > readlink /SEAWAY/NEWSITE 1025 > unique: 1181, success, outsize: 26 > unique: 1182, opcode: GETATTR (3), nodeid: 1, insize: 40, pid: 36429 > getattr / > unique: 1182, success, outsize: 112 > unique: 1183, opcode: READLINK (5), nodeid: 11, insize: 40, pid: 36429 > readlink /SEAWAY/NEWSITE 1025 > unique: 1183, success, outsize: 26 > unique: 1184, opcode: GETATTR (3), nodeid: 1, insize: 40, pid: 36429 > getattr / > unique: 1184, success, outsize: 112 > unique: 1185, opcode: LOOKUP (1), nodeid: 12, insize: 51, pid: 36429 > LOOKUP /NEWSITE/.directory > getattr /NEWSITE/.directory > unique: 1185, error: -2 (No such file or directory), outsize: 16 > unique: 1186, opcode: GETATTR (3), nodeid: 1, insize: 40, pid: 36429 > getattr / > unique: 1186, success, outsize: 112 > unique: 1187, opcode: GETATTR (3), nodeid: 3, insize: 40, pid: 36429 > getattr /SEAWAY > unique: 1187, success, outsize: 112 > unique: 1188, opcode: GETATTR (3), nodeid: 11, insize: 40, pid: 36429 > getattr /SEAWAY/NEWSITE > unique: 1188, success, outsize: 112 > unique: 1189, opcode: READLINK (5), nodeid: 11, insize: 40, pid: 36429 > readlink /SEAWAY/NEWSITE 1025 > unique: 1189, success, outsize: 26 > unique: 1190, opcode: READLINK (5), nodeid: 11, insize: 40, pid: 36429 > readlink /SEAWAY/NEWSITE 1025 > unique: 1190, success, outsize: 26 > unique: 1191, opcode: GETATTR (3), nodeid: 1, insize: 40, pid: 36429 > getattr / > unique: 1191, success, outsize: 112 > unique: 1192, opcode: GETATTR (3), nodeid: 12, insize: 40, pid: 36429 > getattr /NEWSITE > unique: 1192, success, outsize: 112 > unique: 1193, opcode: GETATTR (3), nodeid: 3, insize: 40, pid: 36429 > getattr /SEAWAY > unique: 1193, success, outsize: 112 > unique: 1194, opcode: GETATTR (3), nodeid: 12, insize: 40, pid: 36429 > getattr /NEWSITE > unique: 1194, success, outsize: 112 > unique: 1195, opcode: GETATTR (3), nodeid: 11, insize: 40, pid: 36429 > getattr /SEAWAY/NEWSITE > unique: 1195, success, outsize: 112 > unique: 1196, opcode: READLINK (5), nodeid: 11, insize: 40, pid: 36429 > readlink /SEAWAY/NEWSITE 1025 > > > > when accessing the SMBv2 share (BAD): > > readlink /SEAWAY/SITE-DESIGN 1025 > unique: 1157, success, outsize: 30 > unique: 1158, opcode: GETATTR (3), nodeid: 1, insize: 40, pid: 36446 > getattr / > unique: 1158, success, outsize: 112 > unique: 1159, opcode: OPENDIR (27), nodeid: 18, insize: 48, pid: 36446 > opendir flags: 0x0 /SITE-DESIGN > unique: 1159, error: -5 (Input/output error), outsize: 16 > 2017-09-28 17:40:21.948 srv(39637)->smb_conn_srv_opendir: errno=22, > Invalid argument > unique: 1160, opcode: GETATTR (3), nodeid: 17, insize: 40, pid: 36429 > getattr /SEAWAY/SITE-DESIGN > unique: 1160, success, outsize: 112 > unique: 1161, opcode: READLINK (5), nodeid: 17, insize: 40, pid: 36429 > readlink /SEAWAY/SITE-DESIGN 1025 > unique: 1161, success, outsize: 30 > unique: 1162, opcode: GETATTR (3), nodeid: 1, insize: 40, pid: 36429 > getattr / > unique: 1162, success, outsize: 112 > unique: 1163, opcode: GETATTR (3), nodeid: 18, insize: 40, pid: 36429 > getattr /SITE-DESIGN > unique: 1163, success, outsize: 112 > unique: 1164, opcode: READLINK (5), nodeid: 17, insize: 40, pid: 36429 > readlink /SEAWAY/SITE-DESIGN 1025 > unique: 1164, success, outsize: 30 > unique: 1165, opcode: GETATTR (3), nodeid: 1, insize: 40, pid: 36429 > getattr / > unique: 1165, success, outsize: 112 > unique: 1166, opcode: GETATTR (3), nodeid: 17, insize: 40, pid: 36429 > getattr /SEAWAY/SITE-DESIGN > unique: 1166, success, outsize: 112 > > > 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. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things."