From owner-freebsd-hackers@freebsd.org Wed Dec 30 23:33:35 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2A6994D348C for ; Wed, 30 Dec 2020 23:33:35 +0000 (UTC) (envelope-from SRS0=FZaK=GC=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 4D5nfP5KGLz4sVZ; Wed, 30 Dec 2020 23:33:33 +0000 (UTC) (envelope-from SRS0=FZaK=GC=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id B2A7E28416; Thu, 31 Dec 2020 00:33:31 +0100 (CET) Received: from illbsd.quip.test (ip-94-113-69-69.net.upcbroadband.cz [94.113.69.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 1DB7C28411; Thu, 31 Dec 2020 00:33:30 +0100 (CET) Subject: Re: Project information - SMBv2+ To: Daniel Ebdrup Jensen , freebsd-hackers@freebsd.org References: <16e5725b-ec2f-3222-d20d-fd15e597c12c@gmx.net> <075f31cb-dd13-778d-ed50-3ec7d6f30731@gmx.net> <704a700c-32ff-66eb-6711-5d75099abcd4@quip.cz> <20201230225624.atsnf6u5mmtcu5sw@nerd-thinkpad.local> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <8644f79e-3957-3498-efa9-8fbfc7b57581@quip.cz> Date: Thu, 31 Dec 2020 00:33:28 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20201230225624.atsnf6u5mmtcu5sw@nerd-thinkpad.local> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4D5nfP5KGLz4sVZ X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=FZaK=GC=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=FZaK=GC=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [-1.80 / 15.00]; RCVD_TLS_LAST(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[quip.cz]; ARC_NA(0.00)[]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[94.124.105.4:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RBL_DBL_DONT_QUERY_IPS(0.00)[94.124.105.4:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=FZaK=GC=quip.cz=000.fbsd@elsa.codelab.cz]; RECEIVED_SPAMHAUS_PBL(0.00)[94.113.69.69:received]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=FZaK=GC=quip.cz=000.fbsd@elsa.codelab.cz]; MAILMAN_DEST(0.00)[freebsd-hackers] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2020 23:33:35 -0000 On 30/12/2020 23:56, Daniel Ebdrup Jensen wrote: > On Wed, Dec 30, 2020 at 10:16:44PM +0100, Miroslav Lachman wrote: >> On 30/12/2020 20:24, CerebrosuS wrote: >>> >>> >>> Am 30.12.20 um 20:05 schrieb Miroslav Lachman: >>>> On 30/12/2020 18:57, CerebrosuS wrote: >>>>> Hello at all, >>>>> >>>>> the community and developer at FreeBSD seem to know, that SMBv1 for >>>>> clients is nearly over and that the included mount_smbfs doesn't >>>>> support >>>>> newer versions. So good, so far... >>>>> >>>>> So I can find multiple information about the situation, but no clear >>>>> path on how FreeBSD community and developer will go on to solve this >>>>> missing function. (Just got the information on: >>>>> https://wiki.freebsd.org/MateuszPiotrowski/AccessingSmbSharesWithSambaClient) >>>>> >>>>> >>>>> >>>>> >>>>> This is what I am asking: >>>>> - Is there a project existing for solving this problem (with whatever >>>>> target)? >>>>> - What is the way to go in future? Extend mount_smbfs or support the >>>>> fuse-smbnetfs part to be stable and fast like mount_smbfs (buggy and >>>>> laggy here)? >>>>> - Who is mainly working on it, if a project already exist? >>>>> >>>>> I'am just interested, cause of not finding such information >>>>> clearly. Is >>>>> there maybe a general project management list / team to see what >>>>> projects are going on in whatever state? >>>>> >>>>> I am a hobby developer mainly coming from chemical engineering side, >>>>> having some time to help. I've already written some cross platform >>>>> software but never related to network or on os-level. So I am >>>>> motivated >>>>> to invest some time in getting stuff into FreeBSD, but for me, >>>>> there is >>>>> a lack on information (see above). >>>>> >>>>> Thank you in advance for information and help. >>>> >>>> I was involved in the thread linked by Gleb. AFAIK nothing changed from >>>> that time. I tried something from ports but it has more problems >>>> (shares >>>> cannot be mounted on boot like mount_smbfs does). >>>> If somebody has time and skills to try to bring SMBv2 or v3 to FreeBSD >>>> then Apple or Solaris sources is good start. The both were using the >>>> same mount_smbfs (v1) as FreeBSD so one can check their sources and see >>>> how they evolve to v2 / v3. >>> >>> They are both using exactly the same source code as a starting point and >>> extend it (or rewrite it) to SMBv2? >> >> They are based on the ported code. Apple Mac OS X and Solaris have >> different kernel so they needed modified port of the same code as was >> in FreeBSD back in the days (there is the same copyright header). >> Apple sources or Solaris sources cannot be used directly on FreeBSD >> but some skilled developer can look in to those sources to see their >> evolution. But as was already noted v2 and v3 are very different from >> v1. It will be hard to port but not impossible. >> Current solutions in ports (fusefs) are almost useless in server >> environment. >> >> Miroslav Lachman >> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to >> "freebsd-hackers-unsubscribe@freebsd.org" > > Hi folks, > > Assuming that the reasons for not using fuse in a server environment are > related primarily to performance and that the implementation that was in > base used to be quite out-of-date, has this at all been reevalulated > since a new version was merged? [1] Last time I tried smb with fuse it was unstable and does not allowed me to configure what to mount where at boot time. AFAIK fusefs-smbnetfs cannot be used the same way as mount_smbfs in fstab. So I think smbnetfs is not usable solution in our environment even if it works stable and fast. Kind regards Miroslav Lachman