Wake on Lan after latest update

Help and Support
1

Hi,

Getting a Wake on Lan and then an Extended wake on Lan after the latest update for Vero 4K.
Which delays the playing of videos significantly.

Synology NAS, very fast network, never had any network issues previously.

Also, when stopping a film, it is sometimes going to a black screen for 30 seconds.

Build 21.1

Log: https://paste.osmc.tv/uligusahus

Any advice to fix appreciated, or… if that’s not possible, what is the easiest way to downgrade to one of the recent backups that I have?

Thanks,

2

Hi,

Does the issue still occur if you disconnect from the wifi?

Suspect vero may be favouring wifi over the wired connection.

Regards Tom.

3

Hi Tom,

Thank you.

I disconnected the wifi and did a reboot, and it was responsive and playing promptly to start with.

However, when left on the home screen for 10 minutes, and I hit play again… back to having the wake on lan and extended wake on lan delay.

Appreciate the quick advice.

4

Hi,

Apologies looks like this may be a known issue and being looked into:-

Regards Tom.

5

I still can’t see how the original implementation could have worked as there wouldn’t be the correct socket permissions.

But someone did post a workaround and I can see how that would have worked. I think Kodi just waits for longer now when trying to WoL.

Unfortunately there was a bit of reluctance testing a proper solution there, but I do plan to resolve this properly.

6

I’ve got a Vero 4k and have the same problem, since last update my WoL is broken. When I start a film , always try to WoL the NAS ( some times is boot and isn’t detected

7

Unfortunately I don’t have enough information to proceed with this further at this time.

8

Possibly related to Wake on Lan triggered for NFS share that is already accessible

The solution is to set the net.ipv4.ping_group_range permissions correctly as per https://old.reddit.com/r/Fedora/comments/llsht8/ping_socket_operation_not_permitted_check/

This is probably something that should be done automatically as part of the OSMC install or update process.

9

Hi @planetmarshall

Interesting find. Did you confirm this on the latest OSMC stable?
Was this the only change you needed to make?

10

Yes - here is the head from my current logs

2025-02-01 16:19:30.589 T:2934     info <general>: -----------------------------------------------------------------------
2025-02-01 16:19:30.589 T:2934     info <general>: Starting Kodi (21.1). Platform: Linux ARM 32-bit (version for Vero)
2025-02-01 16:19:30.589 T:2934     info <general>: Using Release Kodi x32
2025-02-01 16:19:30.589 T:2934     info <general>: Kodi compiled 2024-10-03 by GCC 10.2.1 for Linux ARM 32-bit version 5.10.158 (330398)
2025-02-01 16:19:30.589 T:2934     info <general>: Running on OSMC Vero 4K / Vero 4K + with Open Source Media Center 2024.10-1, kernel: Linux ARM 32-bit version 4.9.269-62-osmc

sudo sysctl -w net.ipv4.ping_group_range="0 2000"

resolves the issue but the setting does not persist after a restart

1 Like
11

I love you for this. I had the same issue for quite a while and can confirm this fixed my problems.

12

Can confirm that the issue is still present in the Vero V on the following version:

2025-11-30 19:09:16.752 T:2809     info <general>: Starting Kodi (21.2). Platform: Linux ARM 32-bit (version for Vero)
2025-11-30 19:09:16.752 T:2809     info <general>: Using Release Kodi x32
2025-11-30 19:09:16.752 T:2809     info <general>: Kodi compiled 2025-02-20 by GCC 10.2.1 for Linux ARM 32-bit version 5.10.158 (330398)
2025-11-30 19:09:16.752 T:2809     info <general>: Running on OSMC Vero V with Open Source Media Center 2025.03-1, kernel: Linux ARM 32-bit version 4.9.269-80-osmc
2025-11-30 19:09:16.759 T:2809     info <general>: FFmpeg version/source: 6.0.1-Kodi

I was able to resolve the issue persistently by adding the following line:

net.ipv4.ping_group_range=0 2000

to /etc/sysctl.d/98-local.conf (I created the file).

Note that there are no quotation marks around the value, as opposed to when sysctl is called on the command line.

1 Like
13

This seemed to slip my memory.
I will check and get this sorted.

Sam

14

Had it in my notes, but missed it.

Hopefully the issue is now addressed with the following commit:

I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:

  1. Login via the command line
  2. Run the following command to add the staging repository:
    echo 'deb http://apt.osmc.tv bullseye-devel main' | sudo tee /etc/apt/sources.list.d/osmc-devel.list
  3. Go to My OSMC → Updater → Manual Controls → and select Check for Updates now. When prompted to do so on screen, please choose to install the update.
  4. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you remove /etc/apt/sources.list.d/osmc-devel.list after updating.

This will deactivate the staging repository. You can do so with the following command:
sudo rm /etc/apt/sources.list.d/osmc-devel.list.

Please note that we will automatically disable this update channel after 14 days on your device in case you forget to do so to ensure that your system reverts to the stable update channel.

Thanks for the reports and suggested fix @planetmarshall and thanks to @CestLeBob for confirming.

Sam

1 Like