Client not waking server after resume (1 Viewer)

[jonm]

I've got an issue where a client isn't waking the server after it resumes from suspend.

I think the reason might be because when the wol packet is sent, the network interface isn't ready.
So it doesn't matter how long I set the WOL timeout to, because that WOL packet only gets
sent once and then the server just gets repeatedly pinged, the server will never wake up.

Does that sound like a viable explanation?

I was wondering if it's possible to change how this works so that the wol packet is sent
repeatedly for the set server wakeup timeout duration?

In the meantime, any suggestions on how I can work around this?

 

[robbo100]

will the server wake if you use a WOL command from another machine using other software?

 

[jonm]

Yep, other clients can wake the server fine - and it wakes from this one when it's first booted - it's only on resume that it doesn't work, which is why I'm suspicious about the network i/f not quite being ready at the time the WOL packet is sent.

I'm trying to fathom how to compile MP myself so I can try tweaking WakeupSystem in WakeOnLanManager.cs - I've got as far as finding the right file in the source, at least