Reply to thread

Message

<blockquote data-quote="Brownard" data-source="post: 1215015" data-attributes="member: 48291">[USERGROUP=40]@Testers[/USERGROUP] new version added to first post. I managed to get the client to resolve the server hardware address directly for both IPv4 and IPv6 addresses so the server plugin is no longer necessary and has been removed.[USER=50482]@azzuro[/USER] would be good if you could test to see if it's still working in your environment <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />[USER=55546]@happyf1sh[/USER] The plugin should now wait for the network connection to become available before sending the WOL packet (by default it will wait for up to 20 seconds). Hopefully this will fix your issues when waking the client.This is next on the TODO list.</blockquote>

[QUOTE="Brownard, post: 1215015, member: 48291"] [USERGROUP=40]@Testers[/USERGROUP] new version added to first post. I managed to get the client to resolve the server hardware address directly for both IPv4 and IPv6 addresses so the server plugin is no longer necessary and has been removed. [USER=50482]@azzuro[/USER] would be good if you could test to see if it's still working in your environment ;) [USER=55546]@happyf1sh[/USER] The plugin should now wait for the network connection to become available before sending the WOL packet (by default it will wait for up to 20 seconds). Hopefully this will fix your issues when waking the client. This is next on the TODO list. [/QUOTE]

Verification