From nobody Tue Jul 11 14:12:59 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4R0jWs220gz4dWP9 for ; Tue, 11 Jul 2023 14:13:13 +0000 (UTC) (envelope-from paulbeard@gmail.com) Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R0jWs0KcBz4FkL for ; Tue, 11 Jul 2023 14:13:13 +0000 (UTC) (envelope-from paulbeard@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oi1-x230.google.com with SMTP id 5614622812f47-3a40b756eb0so1112019b6e.2 for ; Tue, 11 Jul 2023 07:13:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689084792; x=1691676792; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=CGxO8YfVhILHLLHsS6HGZ7X8TfFUPLl0urOQjZcslAg=; b=Y42yX09ztNjF7j3m2y87u2TDV60lxwbfg+m529ykiW6cnrsSjzkaaPpzyyuLEhr+PK WJTk9HdHXW70cKIPNs7IvVSDTbJSf9js8MaIW8t20GLUuNFRu6oxj66QTHGn63dTRMCZ GVfyRNX+QXizcMaN/BVwgdz0m0BSOZ7Gr+6ryJq/KDLMI5wL0So50iSsbDJrO6P9Yzj+ 5AAwQr06+rjJgY6CbCKxNIlAHuWUYaHTPQnFDyh7CaMKh+gnEGx53SKAvVHPyVN2bzVK B4qXPBdChkRpk/PV1mRMY19SVYDMG8FE33eLtwWpUuG/k3gZnJql8R0QUlSnWsVuvIG9 +h6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689084792; x=1691676792; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CGxO8YfVhILHLLHsS6HGZ7X8TfFUPLl0urOQjZcslAg=; b=SFHoWGh4sRdbrkQb52ip/3Ke/L2ITjEuFHh/O7WbLR+RnDwWCeDWOvrX4I/60qUW2y A6Qd2+JT1iulfQamIV39XVNJ1CLoTwaVK8Mrx9xufKjG2ZgJQt+HXajLzl+q+jUOa9R8 mYoo3uuhoinXl/lTT/HrzqV5FVQzMeYg2Ujgpwh+2YYZp4iEml5K0xtAJSXYVwZM5m4Y Kgz0iA7ivBYqJvrkcdsRO9d6lHE/wZdLL44IA0ltUUVo8cIWjpO5t7SGm/TK+/ppND8Y MZNUND4HIHDiUXE0tYJGYpkBvdzlb7tctV9LSAOcKY3a+zZciyA7AwWC9zRRbeKbfB51 0edQ== X-Gm-Message-State: ABy/qLZrDBSLG8VpgoNtM1vD7M6s/pPygDtCfj0ZWwBQsCjuRTKaEUqA a/W8Eko2p4hokodbF/SDgW2YmApdSh9fX29P9UfYZN74YlQ= X-Google-Smtp-Source: APBJJlGhWWDg8eYLAkAt7uzg7v+kQ8zWR8OcLzuA+AtqbDTh2n+NQqTtbgpFs4Tud1f7NUzDOvsrl5rRHuzsi710sbI= X-Received: by 2002:a05:6808:23d3:b0:3a1:efe3:e815 with SMTP id bq19-20020a05680823d300b003a1efe3e815mr14951321oib.34.1689084791572; Tue, 11 Jul 2023 07:13:11 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: paul beard Date: Tue, 11 Jul 2023 07:12:59 -0700 Message-ID: Subject: =?UTF-8?Q?Re=3A_SMB_authentication=E2=80=A6flakiness=3F?= To: Paul Mather Cc: FreeBSD-questions Content-Type: multipart/alternative; boundary="000000000000ff4e6f060036b241" X-Rspamd-Queue-Id: 4R0jWs0KcBz4FkL X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000ff4e6f060036b241 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I'll take a look but am reluctant (read: lazy) to install a whole new thing to do something that worked as recently as yesterday. Seeing this on the client side: Jul 10 18:15:18 www kernel: smb_smb_negotiate: Don't know how to talk with server xxx (65535) I assume this was during the testing of smb v1, v1 + v2 and pure v2. I did install samba on the client so I could use smbclient, hoping for more debugging info. smbclient -U www -I omphalos -N /tmp/mnt/storage //mnt/storage session setup failed: NT_STATUS_LOGON_FAILURE and of course, now smbutil doesn't work as it used to. The client on busybox allows some custom config to added: is there any logging I can toggle on there? On Tue, Jul 11, 2023 at 5:47=E2=80=AFAM Paul Mather wrote: > On Mon, 2023-07-10 at 18:30 -0700, paul beard wrote: > > having some trouble mounting an smb volume hosted by a wireless base > station running linux/busybox. > > smbutil works, mount_smbfs doesn't. password is in .nsmbrc, seems to be > readable by smbutil. > > smbutil view //www@omphalos > Share Type Comment > ------------------------------- > jffs disk JFFS > storage disk STORAGE > EFI disk EFI > IPC$ pipe IPC Service (FreshTomato Samba Server) > > mount_smbfs -I omphalos -N //tmp/mnt/storage /mnt/storage > mount_smbfs: unable to open connection: syserr =3D Authentication error > > tail -1 /etc/fstab > //omphalos/STORAGE /mnt/storage smbfs rw,noauto, > -N,-I192.168.0.1 00 > > This all used to work, but a couple of firmware upgrades have taken place= . > This was working yesterday after the latest update but now is failing and= I > am not seeing what's wrong with it. > > The server offers Samba protocol version v1, v2 or mixed v1/v2. v1 doesn'= t > work at all, returns > mount_smbfs: unable to open connection: syserr =3D RPC struct is bad > > The others will allow smbutil to work but not mount_smbfs. Logging isn't > telling me much on the server side. I could mount the disk on macOS but > that's not working now either. smbutil still works there but not > mount_smbfs. > > > > When my OpenELEC server stopped supporting SMB1 by default I decided to > bite the bullet and abandon mount_smbfs, which does not support anything > higher than SMB1. (See the STANDARDS section of the mount_smbfs(8) manua= l > page.) > > In my case, I switched to the sysutils/fusefs-smbnetfs port. It uses > Samba4 under the hood, so supports both SMB2 and SMB3, making it more > compatible with other OSes (like macOS). I found fusefs-smbnetfs a littl= e > bit of a pain to set up, but very reliable. Its main advantage, for me, = is > supporting modern SMB standards. > > Cheers, > > Paul. > --=20 Paul Beard / www.paulbeard.org/ --000000000000ff4e6f060036b241 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'll take a look but am reluctant (read: lazy) to inst= all a whole new thing to do something=C2=A0that worked as recently as yeste= rday.=C2=A0

Seeing this on the client side:=C2=A0
<= div>Jul 10 18:15:18 <kern.crit> www kernel: smb_smb_negotiate: Don= 9;t know how to talk with server xxx (65535)
I assume this wa= s during the testing of smb v1, v1=C2=A0+ v2 and pure v2.=C2=A0
<= br>
I did install samba on the client so I could use smbclient, h= oping for more debugging info.=C2=A0

smbclient -U = www -I omphalos -N /tmp/mnt/storage =C2=A0//mnt/storage
sessi= on setup failed: NT_STATUS_LOGON_FAILURE

and o= f course, now smbutil doesn't work as it used to.=C2=A0

<= /div>
The client on busybox allows some custom config to added: is ther= e any logging I can toggle on there?=C2=A0

On Tue, Jul 11, 2023 at 5:4= 7=E2=80=AFAM Paul Mather <pau= l@gromit.dlib.vt.edu> wrote:
On = Mon, 2023-07-10 at 18:30 -0700, paul beard wrote:
having some trouble mounting an smb volume hosted by a wireless base = station running linux/busybox.

smbutil works, mount_smbfs doesn'= ;t. password is in .nsmbrc, seems to be readable by smbutil.=C2=A0

<= font face=3D"monospace">smbutil view //www@omphalos
Share =C2=A0 =C2=A0 = =C2=A0 =C2=A0Type =C2=A0 =C2=A0 =C2=A0 Comment
-------------------------= ------
jffs =C2=A0 =C2=A0 =C2=A0 =C2=A0 disk =C2=A0 =C2=A0 =C2=A0 JFFSstorage =C2=A0 =C2=A0 =C2=A0disk =C2=A0 =C2=A0 =C2=A0 STORAGE
EFI =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0disk =C2=A0 =C2=A0 =C2=A0 EFI
IPC$ =C2=A0= =C2=A0 =C2=A0 =C2=A0 pipe =C2=A0 =C2=A0 =C2=A0 IPC Service (FreshTomato Sa= mba Server)

mount_smbfs -I omphalos = -N //tmp/mnt/storage /mnt/storage
mount_smbfs: unable to open connection= : syserr =3D Authentication error

tail -1 /etc/fs= tab
//omphalos/STORAGE =C2=A0 =C2=A0 =C2=A0/mnt/storage =C2=A0 =C2=A0sm= bfs =C2=A0 rw,noauto, -N,-I192.168.0.1 00

This all used to wor= k, but a couple of firmware upgrades have taken place. This was working yes= terday after the latest update but now is failing and I am not seeing what&= #39;s wrong with it.=C2=A0

The server offers Samba proto= col version=C2=A0v1, v2 or mixed v1/v2. v1 doesn't work at all, returns= =C2=A0
mount_smbfs: unable to open connection= : syserr =3D RPC struct is bad

The others wil= l allow smbutil to work but not mount_smbfs. Logging=C2=A0isn't telling= me much on the server side. I could mount the disk on macOS but that's= not working now either. smbutil still works there but not mount_smbfs.


When my OpenELEC se= rver stopped supporting SMB1 by default I decided to bite the bullet and ab= andon mount_smbfs, which does not support anything higher than SMB1. =C2=A0= (See the STANDARDS section of the mount_smbfs(8) manual page.)
In my case, I switched to the sysutils/fusefs-smbnetfs port.= =C2=A0 It uses Samba4 under the hood, so supports both SMB2 and SMB3, makin= g it more compatible with other OSes (like macOS).=C2=A0 I found fusefs-smb= netfs a little bit of a pain to set up, but very reliable.=C2=A0 Its main a= dvantage, for me, is supporting modern SMB standards.

<= div>Cheers,

Paul.


--
Pa= ul Beard / www.paul= beard.org/
--000000000000ff4e6f060036b241--