Bug #705

smb config needs updating

Added by Hammel 10 months ago. Updated 10 months ago.

Status:In ProgressStart date:18 Mar 2019
Priority:UrgentDue date:
Assignee:Hammel% Done:


Category:00 - Basic Build Issues
Target version:1.1.0 - Upgrades
Severity:04 - Low


The latest boot is showing the following in dmesg:

[ 51.971329] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[ 52.913554] CIFS VFS: Unable to select appropriate authentication method!
[ 52.913587] CIFS VFS: Send error in SessSetup = -22

It's a config update that hasn't been propagated to PiBox's smb configuration.

Associated revisions

Revision 87a31c6a
Added by Hammel 10 months ago

RM #705: Add vers=1.0 to default smb mount command. Add support for disabling smb and streaming threads for devices that won't need them (like Xeon).

Revision a4078b5c
Added by Hammel 10 months ago

RM #705: Also disable IoT processing on demand.


#1 Updated by Hammel 10 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

This appears to be a change to the smb command in piboxd, where the "-o <options>" needs to include "vers=1" or "vers=3" or something. It's not clear what it should be but "vers=1" seems to be the fallback for the old default setting (which is no longer set).

Also, or possibly in place of, I can try removing ",sec=ntlm" which is set in piboxd:smb.c in the default command.

#2 Updated by Hammel 10 months ago

  • % Done changed from 10 to 50

"vers=1.0" fixes this problem. At the same time, I'm implementing the option of disabling both SMB and stream handling in piboxd. This will allow piboxd to be more lightweight on systems like Xeon.

Currently need to implement -x option for piboxd's cross.sh, as was done for the launcher, so the build picks up the proper app.cfg file.

#3 Updated by Hammel 10 months ago

  • Priority changed from Immediate to Urgent
  • % Done changed from 50 to 80

Fixes tested, committed and pushed - including metabuild.

Changes seem to work but it's unclear if this fixes the reported issue.

Moving this down the priority list and will recheck again later to see if the problem shows up anymore.

#4 Updated by Hammel 10 months ago

  • Severity changed from 05 - Very Low to 04 - Low

Also available in: Atom PDF