Posts by roxton

Apologies, the screenshot was taken when I was making wild attempts to access a share. I know I have to use the username and password that I set in LibreELEC settings.

The above made me try one more thing. I went to the settings and disabled and enabled again the password-protected SMB switch, now I can access all the shares from 24H2.

I then reverted /storage/.config/samba.conf to the state of /storage/.config/samba.conf.sample, ran /usr/lib/samba/samba-config, restarted smbd and rebooted the 24H2 machine and it still lets me in.

So, apologies for making the fuss, I have no idea what was wrong and where. And thanks for your help!

I made sure to check the same credentials multiple times on two separate PCs, one with 24H2 and one with 23H2. On 23H2 they work from the start. On 24H2 they work only after I execute Set-SmbClientConfiguration -EnableInsecureGuestLogons $true and then the problem returns when I reverse this change.

HomerJau , could you please check if Get-SmbClientConfiguration | FL EnableInsecureGuestLogons returns False for you?

I do use them. And they work on 23H2.

Hi everyone!

Windows 11 24H2 started rolling out recently, and with it a new policy for accessing SMB shares. Since upgrading to 24H2 I can't access LibreELEC's default network shares which were accessible from 23H2. Here's what the problem looks like (don't mind the user on the screenshot, I also used libreelec user with the password set in LibreELEC settings):

The only thing that helped was executing Set-SmbClientConfiguration -EnableInsecureGuestLogons $true on the Windows machine.

And because that's not something I want to fix by disabling a security feature on the client side, I started experimenting with various properties in /storage/.config/samba.conf and then doing

systemctl stop smbd
/usr/lib/samba/samba-config
systemctl start smbd

Reading through https://www.samba.org/samba/docs/cur…smb.conf.5.html I tried adding guest ok = no and commenting out public = yes, changing map to guest from Bad User to Never, commenting out guest account = root, adding restrict anonymous = 2, etc. Nothing helped though.

My /storage/.config/samba.conf currently looks like this:

# SPDX-License-Identifier: GPL-2.0-or-later
# Copyright (C) 2009-2016 Stephan Raue (stephan@openelec.tv)
# Copyright (C) 2017-present Team LibreELEC (https://libreelec.tv)

# samba.conf v4 (do not remove)

# This configuration file allows you to customize the samba shares
# available from your machine

[global]
  server string = LibreELEC
  browseable = yes
  writeable = yes
  printable = no
  deadtime = 30
  mangled names = no
  name resolve order = host bcast
  printcap name = /dev/null
  load printers = no
  enable core files = no
  passdb backend = smbpasswd
  smb encrypt = disabled
  # server signing = auto
  fruit:model = Xserve

  # samba share options
  restrict anonymous = 2
  # map to guest = Bad User
  map to guest = Never
  # guest account = root
  security = user

  # samba tuning options
  socket options = TCP_NODELAY IPTOS_LOWDELAY
  min receivefile size = 16384
  aio read size = 16384
  aio write size = 16384
  use sendfile = yes

  # The following are default values for the master selection process
  # local master = yes
  # preferred master = auto
  # domain master = auto
  # os level = 20

  # "strict allocate = yes" breaks large network transfers to external hdd
  # Force this to "no" in case "yes" becomes the default in future
  strict allocate = no

# Using the following configurations as a template allows you to add
# writeable shares of disks and paths under /storage

[Update]
  path = /storage/.update
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Videos]
  path = /storage/videos
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Music]
  path = /storage/music
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[TV Shows]
  path = /storage/tvshows
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Recordings]
  path = /storage/recordings
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Downloads]
  path = /storage/downloads
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Pictures]
  path = /storage/pictures
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Emulators]
  path = /storage/emulators
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Configfiles]
  path = /storage/.config
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Userdata]
  path = /storage/.kodi/userdata
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Screenshots]
  path = /storage/screenshots
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Logfiles]
  path = /storage/logfiles
  available = yes
  browseable = yes
  # public = yes
  writeable = yes
  root preexec = createlog

[Backup]
  path = /storage/backup
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

[Picons]
  path = /storage/picons
  available = yes
  browseable = yes
  # public = yes
  writeable = yes

So here's the question: can we somehow configure SMB on LibreELEC so that SMB shares could be accessed from Windows 11 24H2?

Merged! Thanks for help guys!

Pull request: https://github.com/LibreELEC/documentation/pull/46

Thanks guys! Yeah, looks like an almost complete picture.

Apologies, please treat "OS" as "kernel" in the above post

Thanks, will do.

I intend to add information to installation/docker.md but for that I'll need some historical context

Is it correct that on Raspberry Pi LibreELEC 9 was the last 32-bit Linux and since version 10 the OS is aarch64 with 32-bit userspace, as HiassofT described?

Also is the difference between the OS and userspace true for the Generic x86_64 distribution?

Quote from HiassofT

LibreELEC 11 has aarch64 kernel but arm (32bit) userspace

Could someone mention this in LibreELEC's wiki?

Not really related to Xbox wireless adapter but if you connect your controllers using Bluetooth, you can make them work like this:

1. Update your controller's firmware using Xbox Accessories app on Windows 10/11
2. Disable ERTM on your LibreELEC device, lets the controller be paired and connected (1 command, pastable):
   echo 'options bluetooth disable_ertm=1' > /storage/.config/modprobe.d/bluetooth-disable-ertm.conf
   
3. Ignore libinput, makes the controller's buttons work (2 commands, pastable):
   echo 'SUBSYSTEM=="input", ATTRS{name}=="Xbox Wireless Controller", KERNEL=="event*", MODE="0666", ENV{LIBINPUT_IGNORE_DEVICE}="1"' > /storage/.config/udev.rules.d/99-gamepad.rules
   echo 'SUBSYSTEM=="input", ATTRS{name}=="Xbox Wireless Controller", KERNEL=="event*", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"' >> /storage/.config/udev.rules.d/99-gamepad.rules
4. Reboot and pair your controller
5. Navigate to Settings > System > Input and do Configure attached controllers

The key is updating your controller's firmware.

I haven't updated my XBOX One controller's firmware for several years and on LibreELEC I always had two non-functional buttons: Back and Guide (XBOX button). Then I recently bought a newer XBOX Series X/S controller and it was refusing to connect to my RPi4 with LibreELEC 11.0.1 until I updated its firmware - then it connected and surprised me with letting me map its Back and Guide buttons, which in turn got me thinking that I could try looking for a new firmware for my older controller. The app had found new firmware for it, the controller had been updated and it turned out its Back and Guide buttons also work! Nice!

TL;DR: update your XBOX wireless controller's firmware

On LibreELEC 11.0.1, both these things are still needed to connect your XBOX wireless controller via Bluetooth and use it:

1. Disable ERTM, lets the controller be paired and connected (1 command, pastable):
   echo 'options bluetooth disable_ertm=1' > /storage/.config/modprobe.d/bluetooth-disable-ertm.conf
2. Ignore libinput, makes the controller's buttons work (2 commands, pastable):
   echo 'SUBSYSTEM=="input", ATTRS{name}=="Xbox Wireless Controller", KERNEL=="event*", MODE="0666", ENV{LIBINPUT_IGNORE_DEVICE}="1"' > /storage/.config/udev.rules.d/99-gamepad.rules
   echo 'SUBSYSTEM=="input", ATTRS{name}=="Xbox Wireless Controller", KERNEL=="event*", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"' >> /storage/.config/udev.rules.d/99-gamepad.rules

After running the above, you would reboot and try pairing your controller. Potentially you would fail to do so with a newer XBOX Series X/S controller or succeed with an older XBOX One controller.

If pairing worked, you would usually navigate to LibreELEC's Settings > System > Input and do Configure attached controllers. During configuration you probably would not be able to map the Back and Guide buttons.

The thing that has changed for me (why I'm posting this) is that all the buttons including Back and Guide (XBOX) started working on both my controllers - the older XBOX One controller and the newer XBOX Series S/X - after I updated their firmware via the Xbox Accessories app on my Windows 11 machine (for this, controllers should be connected with a USB-cable or using XBOX Wireless Adapter). So all buttons are now functional, yay!