WOL being unreliable is usually a question of hardware. If it works sometimes, then your configuration is probably correct and the issue les6s in your switching network, your NIC, or your motherboard.
A lot of switches suck. Start by validating that every single wakeup packet is getting from wakeup server to client while it’s awake, and make sure the payload is intact.
If you’re seeing occasional packet loss, modify your WOL script to spam several magic packets over a couple minutes. Won’t hurt devices that are already awake.
If you’re not getting packets lost, put another WOL device on the same port and see if it wakes up more reliably.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Normally wake on län is a bios setting and has not much to do with your software.
I did turn it on a Dell computer at my parents summer house and the sending the magic package from a raspberry pie worked without problems every time.
WOL being unreliable is usually a question of hardware. If it works sometimes, then your configuration is probably correct and the issue les6s in your switching network, your NIC, or your motherboard.
A lot of switches suck. Start by validating that every single wakeup packet is getting from wakeup server to client while it’s awake, and make sure the payload is intact.
If you’re seeing occasional packet loss, modify your WOL script to spam several magic packets over a couple minutes. Won’t hurt devices that are already awake.
If you’re not getting packets lost, put another WOL device on the same port and see if it wakes up more reliably.
In addition to the BIOS settings, I had to create a systemd service that prevents Linux from disabling Wake-on-LAN on shutdown.
I just turn it on in the bios. And on windows, disable fast startup
I have never gotten WoL to work reliably in any condition. I would just assume it’s not going to, and use other power controls.