From owner-freebsd-current@freebsd.org Thu Mar 3 09:47:25 2016 Return-Path: Delivered-To: freebsd-current@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 BA3A6A93033 for ; Thu, 3 Mar 2016 09:47:25 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 822F4FD6 for ; Thu, 3 Mar 2016 09:47:25 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1abPqs-004ANc-Dy>; Thu, 03 Mar 2016 10:47:22 +0100 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (envelope-from ) id <1abPqs-003z9F-2q>; Thu, 03 Mar 2016 10:47:22 +0100 Date: Thu, 3 Mar 2016 10:47:21 +0100 From: "O. Hartmann" To: freebsd-current Subject: mount_smbfs(8): support for SMBv3.02? Message-ID: <20160303104721.097ae352@freyja.zeit4.iv.bundesimmobilien.de> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2016 09:47:25 -0000 Does FreeBSD's mount_smbfs(8) support for Microsoft's SMBv3 protocol introduced with Windows 8 and Windows Server 2012/R2? I tried to find informations/documentation for the kernel options NETSMB SMBFS which I suspect to maintain this aspect, but I couldn't find anything regarding NETSMB or SMBFS. The manpage for mount_smbfs(8) seems not to provide any further informations. What does option "-n opt" of mount_smbfs(8) do? See manpage for that sepcific command, it lacks of explanation. I'm required to mount a SHARE provided by a Windows Server 2012 R2, which has explicitely deisabled NetBIOS over 139/tcp (firewalled, too). I'm running FreeBSD CURRENT, most recent. I'd like to use FreeBSD tools only - as far as this is possible. Now it seems that mount_smbfs(8) can not handle SMBv3 - but this is simply a guess based upon incomplete documentation. Can someone shed light on the maximal protocol version supported by mount_smbfs(8)? I need to track down why I can not mount a share with 445/tcp only. I can do so via 139/tcp NetBIOS from the very same server (windows 2012R2). Since I do not understand much about how windows negotiate the protocol used with a client's request - if any negotiation ever takes place - I try to find out what I did wrong with the configuration/usage of mount_smbfs(8). I have running a Samba 4.3 server on CURRENT on which I can set "min protocol" and "max protocol" as I like. this server does not allow connections via 139/tcp (filtered via ipfw). When setting "min protocol = SMB2" any mount attempt with mount_smbfs(8) fail, setting the tag to NT1 I'm able to succesfully connect via port 445/tcp. So for that reason I suspect a problem with the SMB version negotiated with the 2012 R2 server and the inability of mount_smbfs(8) (or its appropriate kernel backend) to handle any protocol version higher than NT1 (or SMB1). Thanks in advance and kind regards, Oliver