andyjmorgan/wolmesh

Wake on Lan Mesh Service for remote PC use cases. This project provides a way to monitor and wake remote pc's leveraging a web server and agent.

wolmesh's Issues

WOLMeshClientDaemon start issue

On a Raspberry Pi 3 with Linux ubuntu 5.4.0-1028-raspi #31-Ubuntu SMP PREEMPT Wed Jan 20 11:30:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux, the WOLMeshClientDaemon will not start.

Error message:
"bash: ./WOLMeshClientDaemon: No such file or directory"

File is executable:
-rwxrwxr-x 1 root root 76K Mar 31 2020 WOLMeshClientDaemon

If I try running this as a service, syslog message is:

May 26 10:05:30 ubuntu systemd[1]: Started WOL Mesh Daemon Service.
May 26 10:05:30 ubuntu systemd[13385]: WOLMeshDaemon.service: Failed to execute command: No such file or directory
May 26 10:05:30 ubuntu systemd[13385]: WOLMeshDaemon.service: Failed at step EXEC spawning /usr/bin/wolmeshclient/WOLMeshClientDaemon: No such file or directory
May 26 10:05:30 ubuntu systemd[1]: WOLMeshDaemon.service: Main process exited, code=exited, status=203/EXEC
May 26 10:05:30 ubuntu systemd[1]: WOLMeshDaemon.service: Failed with result 'exit-code'.

We reinstalled Ubuntu a lot of times. Everytime the same error. We're not able to start the WOL Deamon.

Unable to install WOL Agent

Unable to install the WOL Agent. tried on Windows10 1909 and .NET v4.8.0372

Machine Name Sort

In Registered Devices, clicking on the Machine Name column does not re-sort the list. Other columns work as expected.

Client did not work at Ubuntu bookworm/sid

● WOLMeshDaemon.service - WOL Mesh Daemon Service
Loaded: loaded (/etc/systemd/system/WOLMeshDaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2022-12-27 14:06:43 UTC; 144ms ago
Main PID: 5152 (WOLMeshClientDa)
Tasks: 7 (limit: 2237)
Memory: 5.9M
CPU: 84ms
CGroup: /system.slice/WOLMeshDaemon.service
└─5152 /opt/wolmeshclient/WOLMeshClientDaemon

Dez 27 14:06:43 ctd-slimer systemd[1]: Started WOL Mesh Daemon Service.
Dez 27 14:06:43 ctd-slimer WOLMeshClientDaemon[5152]: No usable version of libssl was found

root@host:/opt/wolmeshclient# service WOLMeshDaemon status
● WOLMeshDaemon.service - WOL Mesh Daemon Service
Loaded: loaded (/etc/systemd/system/WOLMeshDaemon.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: core-dump) since Tue 2022-12-27 14:07:23 UTC; 97ms ago
Process: 5406 ExecStart=/opt/wolmeshclient/WOLMeshClientDaemon (code=dumped, signal=ABRT)
Main PID: 5406 (code=dumped, signal=ABRT)
CPU: 91ms

Dez 27 14:07:23 host systemd[1]: WOLMeshDaemon.service: Main process exited, code=dumped, status=6/ABRT
Dez 27 14:07:23 host systemd[1]: WOLMeshDaemon.service: Failed with result 'core-dump'.

Suggestion: Search for device name

Hello, love your project!
A search function would be amazing to easy handling in large networks .

Waking Manual Device does not use relays

When waking a Manual Device, it does not seem to use clients on the local subnet to relay the wake request/packet. When I attempt to wake a manual device, the app only reports a Directed Broadcast attempt.