powerwake triggers wakeonlan monitor, but other wakeonlan implementations do not

Bug #705943 reported by Dustin Kirkland  on 2011-01-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
powernap (Ubuntu)
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...

 * 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
Andres Rodriguez (andreserl) wrote :

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.

Changed in powernap (Ubuntu):
status: Confirmed → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package powernap - 2.0-0ubuntu1

powernap (2.0-0ubuntu1) natty; urgency=low

  [ Andres Rodriguez ]
  * powernap/monitors: Re-work Monitors to integrate them with PowerNap.
  * powernap/powernap.py: Minor fixes to not crash when loading monitors.
  * sbin/powernapd: Integrate Monitors approach to work with Daemon.
  * Update copyright headers for some files
  * Update manpages and add one for powernap-action.
  * Update packaging:
    - debian/control: Add python related fileds.
    - debian/rules: Add dh_pycentral related rules.
  * Add new package to contain new modules and monitors:
    - debian/control: Add package powernap-common.
    - debian/powernap-common.install: Install new files (PowerNap class and
      Monitors); Move action scripts installation to this package.
  * sbin/powernapd: Improve WoL monitor to listen in eth* interfaces.
  * config: Update and cleanup.
  * sbin/powernapd,bin/powerwake: Fix generation of WoL Magic Packet.
    Apparently, more data than required was addeed. (LP: #705943)
 -- Andres Rodriguez <email address hidden> Fri, 21 Jan 2011 15:53:11 -0500

Changed in powernap (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers