Ok, so found the Issue. Powerwake was creating "incorrect" data for the WoL Magic Packet. Consequently, powernapd was creating incorrect data to compare with the data received from powerwake. The fix was quite simple, however, there are some other issues that I can figure out.
For now, though, it works with: - dd-wrt wol - wakeonlan - powerwake No, as far as etherwake, it seems that the implementation of WoL is completely different from the other tools. When using Wireshark to monitor network traffic, it detects packets from etherwake as WoL packets, however, it doesn't do the same for WoL packet from the other tools. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705943 Title: powerwake triggers wakeonlan monitor, but other wakeonlan implementations do not -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
