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.