V9.8.0 pi5 widelinks in smb.conf causes not connecting of Windows 10 Network drive

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | cat /boot/dietpi/.version
    G_DIETPI_VERSION_CORE=9
    G_DIETPI_VERSION_SUB=8
    G_DIETPI_VERSION_RC=0
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’
  • Distro version | bookworm 0
  • Kernel version |Linux pi5 6.6.51+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux
  • Architecture |arm64
  • SBC model | RPi 5 Model B (aarch64)
  • Power supply used | 5V 3A RAV
  • SD card used | Transcend Premium

Additional Information (if applicable)

Steps to reproduce

in /etc/samba/smb.conf section global

wide links = yes → Windows 10 Networkdrive NOK, fail to connect: No messages in dmesg or journalctl

#wide links = yes → Windows 10 Networkdrive OK, could be established and works as expected

Expected behaviour

Actual behaviour

Extra details

Hmm you are sure using our DietPi configuration?? Because this is how it should looks like

with smb.conf above Networkdrive is OK, but no wide links
to achive wide links I added as below, which works great since 4 years on pi4 and dietpi 8.25.2

  follow symlinks = yes
  wide links = yes
  unix extensions = no
  allow insecure wide links = yes

but on pi5 with dietpi 9.8.0 unable to connect a Networkdrive, unless I comment out “wide links = yes”

I just tried to mount this pi5 to pi4 and receive in pi4s dmesg

[Sun Nov 24 14:15:40 2024]   cache: cifs_request, object size: 16588, buffer size: 16640, default order: 3, min order: 3
[Sun Nov 24 14:15:40 2024]   node 0: slabs: 8, objs: 8, free: 0
[Sun Nov 24 14:15:40 2024] CIFS: VFS: cifs_mount failed w/return code = -13
[Sun Nov 24 14:15:40 2024] CIFS: Attempting to mount //192.168.1.51/ftpuser
[Sun Nov 24 14:15:40 2024] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
[Sun Nov 24 14:15:40 2024] SLUB: Unable to allocate memory on node -1, gfp=0xcc0(GFP_KERNEL)
[Sun Nov 24 14:15:40 2024]   cache: cifs_request, object size: 16588, buffer size: 16640, default order: 3, min order: 3
[Sun Nov 24 14:15:40 2024]   node 0: slabs: 9, objs: 9, free: 0
[Sun Nov 24 14:15:40 2024] CIFS: VFS: cifs_mount failed w/return code = -95

seems to be quite old and outdated. Maybe the old system is not able to connect to a newer version of SMB running on the new RPi5

the old connects and shows content at that moment I comment out the wide links = yes
please advise for the new pi5 system how to configure for wide links

can you share some information on the old RPI4??

Required

  • DietPi version | cat /boot/dietpi/.version
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
  • Kernel version | uname -a
  • Architecture | dpkg --print-architecture

G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=25
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘8’
G_GITOWNER=‘MichaIng’
buster 1
Linux plex-pi 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
armhf

might be Buster is not supporting features for newer SMB version from Debian Bookworm

to recap
on Buster pi4 the wide links are working great towards pi5 and Windows ← no issue there
on Bookworm pi5 the wide links tag prevents any samba functionality
imho the wide links tag is broken on Bookworm and need to be fixed

We don’t maintain SMB package as we use the official one from Debian Repository.

Things have changed between an old, outdated system (Buster) and a modern operating system (Bookworm). Security has been increased and some insecure functions may no longer work ootb. Perhaps you should take a look at the SMB documentation smb.conf(5) — samba-common-bin — Debian bookworm — Debian Manpages
Search for allow insecure wide links

yep, the bookworm man states on allow insecure wide links
… This option was added at the request of sites who had deliberately set Samba up in this way and needed to continue supporting this functionality without having to patch the Samba code. …
But it in bookworm it doesn’t work as described.
Anyway, thank you for the support and as OOTB issue I have to follow up in Debian forum.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.