Hello
i have got a Intel NUC 11 installed LibreELEC on it and want to use the WOL feature of Yatze however the way Yatze implemented WOL does not work. I can use WOL on same network as my Anroid device and it will wake up the NUC but using the app it does not. From packet capture it looks like app is sending the packet direct to the NUC IP instead of the default broadcast address of 255.255.255.255. Etherwake on Linux uses this and it wakes up my NUC fine.
Also Kore Android app also works fine and can wake up my NUC.
I added logs from app here but doubt they will be useful for this. I am not sure where to post em so posted to Encrypted Paste - Private / Secure Paste Service
1 Like
From the logs
Sending WOL to /255.255.255.255 / 7
So it does use the broadcast, it also send another packet for Kodi Starter but it’s unrelated.
Are you sure you did not make a mistake in the MAC as it can no more be auto detected?
If you can packet capture, please provide all the packet sent.
1 Like
hi
the NUC decided to no longer power on so waiting for RMA. i may decide to exchange for a NUC with IR so I dont need to use WOL anymore.
however to answer your question about MAC address, the address is correct as I copied it from app to Kore app on my phone and that worked and woke up my NUC while same MAC on yatse did not.
i can close this as I may no longer need it fixed as I am going to switch to IR
thanks
1 Like
The dump would still be helpful to see what could be wrong.
1 Like
IP ending in 207 is phone and 102 is the NUC
WIFI
igc2 2023-01-20
20:09:35.281239 ethertype IPv4 (0x0800), length 209: (tos 0x0, ttl 255, id 23928, offset 0, flags [none], proto UDP (17), length 195)
xx.207.55551 > xx.54.38900: UDP, length 167
WIFI
igc2 2023-01-20
20:09:35.417008 ethertype IPv4 (0x0800), length 60: (tos 0x0, ttl 64, id 22190, offset 0, flags [DF], proto UDP (17), length 43)
xx.208.44836 > xx.102.7: UDP, length 15
WIFI
igc2 2023-01-20
20:09:35.417203 ff:ff:ff:ff:ff:ff ethertype IPv4 (0x0800), length 144: (tos 0x0, ttl 64, id 35132, offset 0, flags [DF], proto UDP (17), length 130)
xx.208.60796 > 255.255.255.255.7: UDP, length 102
WIFI
igc2 2023-01-20
20:09:40.280894 ethertype IPv4 (0x0800), length 209: (tos 0x0, ttl 255, id 23929, offset 0, flags [none], proto UDP (17), length 195)
xx.207.55551 > xx.54.38900: UDP, length 167
WIFI
igc2 2023-01-20
20:09:42.555721 ethertype IPv4 (0x0800), length 60: (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 29)
xx.208.45335 > 46.68.59.19.4500: isakmp-nat-keep-alive
Hum not 208 the phone ?
First UDP packet should be “YatseStart-Xbmc” and the second the normal WOL broadcast.
Wondering is your phone configured via DHCP? If not can you confirm the network mask of the phone and Kodi are they in the same segment?
Phone is DHCP but Kodi is static IP.
Both are different networks but I have static ARP and port forward to fix that WOL packet not being on same network. I know this setup works as Kore app on same phone can send the WOL packet and wake NUC up and so can laptop running on same network. Its just yatse which dont work.
1 Like
You should have started with that.
Unlike others Yatse tries to fix the common cases and since 99% of users use wol proxy it sends the packet to work for that case. I might probably adopt a dumb approach and send all the possible case at same time.
WOL is not that frequent so the battery/network usage is not that important.
ok
i run opnsense fw so using arp and port forward is only way for 2 LANs and WOL working