powerwake triggers wakeonlan monitor, but other wakeonlan implementations do not
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
powernap (Ubuntu) |
Fix Released
|
High
|
Andres Rodriguez |
Bug Description
Binary package hint: powernap
I love the new wake on lan monitor in PowerNap. It's awesome. Well done, Andres!
It seems to work well with some WoL utilities, but not with others.
Here's my testing...
Working:
* powerwake(1)
Not Working:
* dd-wrt's wol
- powernap's log sees the packet, but doesn't do anything about it
* wakeonlan(1)
- by default, this tool uses port 9, and powernap is watching port 7, so powernap doesn't even recognize see the packet
- calling wakeonlan with -p 7 allows powernap to see the packet, but doesn't do anything with it
* etherwake(8)
- powernap receives the packet but doesn't do anything with it
If this is monitor really is wake-on-lan, then it should really work with at least a couple of common wake on lan implementations. Otherwise, it's really something that's specific to only powernap/powerwake
Changed in powernap (Ubuntu): | |
assignee: | nobody → Andres Rodriguez (andreserl) |
status: | New → Confirmed |
importance: | Undecided → High |
summary: |
- powerwake triggers wakeonlan monitor, but other wakeonlan implementation - does not + powerwake triggers wakeonlan monitor, but other wakeonlan + implementations do not |
Changed in powernap (Ubuntu): | |
status: | Confirmed → Fix Committed |
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.