Missing WOL and buggy tags (/B) in recent OSMC

fzinken · 14 July 2017 06:30

Well I still would correct it as it is not correct syntax.

timzett · 14 July 2017 06:31

You were faster with answering than me with correcting my post - please lookup
Example:
smb://NAS/Filme/

fzinken · 14 July 2017 06:34

I am not sure if the Netbios Name resolution works for WOL setup
Check your Sources entries if you use the Netbios based Source you still have the IP including the wrong syntax in there. I suggest for testing purpose you remove all sources and just add the IP based one without the port.

timzett · 14 July 2017 07:10

Will do. Talk to you later

timzett · 14 July 2017 09:15

Unfortunately it still does not work, even with IP. It just says:
“No route to host”
as if it wouldn’t even try…

fzinken · 14 July 2017 09:19

Suggest, you upload new debug logs.
Next step is to check the network with tcpdump to see if a WOL packet is sent or not.

timzett · 14 July 2017 09:20

Could you please post a short description on how to do that?
I would then do both things in one go

fzinken · 14 July 2017 09:28

No promise it being right but try
sudo apt-get install tcpdump
sudo tcpdump -i eth0 '(udp and port 7) or (udp and port 9)'

timzett · 14 July 2017 10:14

Thanks fzinken. Will do that likely in the evening and then get back - hopefully with some results.

timzett · 3 October 2017 16:28

After a long time, longer than I’d expected, I am back here.
So what happened? After having issues with the latest Kodi I had to go back to 16.1. And there WOL works just fine - with the same wakeonlan.xml and with the folllowing SMB share notation:
smb://192.168.0.16/Filme

What now? Is it a bug in the recent version(s)?
I will try again with another SD card and the latest KODI.

timzett · 5 October 2017 18:34

Problem solved - at last
The important thing was to use the same naming convention in the wakeonlan.xml than for the media source.
E.g. when you specified a NetBIOS name in the source you must also use NetBios for the WOL device specified in the wakeonlan.xml.
Same goes for a SMB link, NFS mount and so on.

Example:
smb://buffalo_NAS/movies => for the media source, results in:

...        
<host>buffalo_NAS</host>
        <mac>00:01:02:03:AB:04</mac>
...

=> for the entry in the wakeonlan.xml

Consequently this means that you must not mix different naming schemes for the same source if you want to ensure it’s always woken up.

Hope this helps also another poor guys who ran into this trap.