Date: Wed, 30 Dec 2020 18:54:26 +0100 From: CerebrosuS <CerebrosuS@gmx.net> To: Dale Scott <dalescott@shaw.ca>, "Kevin P. Neal" <kpn@neutralgood.org> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Project information - SMBv2+ Message-ID: <a9e406e6-5693-abfc-b40d-4584073fff80@gmx.net> In-Reply-To: <29490187.204174646.1609349437600.JavaMail.zimbra@shaw.ca> References: <f0c2fe80-5362-4259-2924-7fb2eed0d640@gmx.net> <X%2Bvnh0Q//Eir2v9a@neutralgood.org> <29490187.204174646.1609349437600.JavaMail.zimbra@shaw.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 30.12.20 um 18:30 schrieb Dale Scott: > ----- Original Message ----- >> From: "Kevin P. Neal" <kpn@neutralgood.org> >> To: "CerebrosuS" <CerebrosuS@gmx.net> >> Cc: "freebsd-questions" <freebsd-questions@freebsd.org> >> Sent: Tuesday, December 29, 2020 7:35:51 PM >> Subject: Re: Project information - SMBv2+ > >> On Mon, Dec 28, 2020 at 10:13:07PM +0100, 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 suppo= rt >>> 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/AccessingSmbSharesWithSamba= Client) > > Can someone give a quick big picture? What would this mean for someone e= .g. > wanting to build an enterprise file server? Can FreeBSD currently serve = (I see > latest samba413 is in ports), but not connect as client to other (newer)= servers? > > Thanks The problem is using FreeBSD as an SMB client. SMBv1 is possible through mount_smbfs. SMBv2+ is possible with gvfs and smbnetfs from fuse. SMBv1 has some bad security issues (thats' why everyone is switching to SMBv2+) and MS Windows 10 switched to SMBv2+ meaning, SMBv1 is not supported by default. The fuse module is known be slow and unstable. I read the "unstable" and "slow" argument for gvfs too, but have only tested the fuse module. Third party packages are also problematic when using with /etc/fstab (there seem to be some workarounds with extension scripts). So to use freebsd as an SMB client would need to extend the mount_smbfs module or invest time to speed up smbnetfs/gvfs to make it usable. For an enterprise file server serving samba is no problem as far as I know and as long as you don't need to mount SMB sources to serve the data. Anyone might want to correct me, if my collected information are wrong. :-= ) > >> >> Two days with no response... I suggest trying the freebsd-hackers list >> instead, or the freebsd-arch list if that doesn't work, and my last >> guess would be freebsd-current. Only try one list at a time. >> > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.= org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a9e406e6-5693-abfc-b40d-4584073fff80>