etherwake doesn't generates Magic Packets

Bug #1300504 reported by J Queiroz on 2014-03-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
etherwake (Ubuntu)
Undecided
Unassigned

Bug Description

I'm trying to use a Kubuntu machine to generate WakeOnLan magic packets.

I'm using Kubuntu 14.04, fresh install. No PPAs neither external packages installed, except vmware player 6.

Installed etherwake and tryed to send WoL magic packets, but they are not being sent. I confirmed this using WireShark on two machines; if I use a WoL software on the other machine (running windows 7 on the same hardware), I can see the magic packets on both machines.

$ lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

$ uname -s -r -p -i
Linux 3.13.0-19-generic x86_64 x86_64

$ apt-cache policy etherwake
etherwake:
  Installed: 1.09-4
  Candidate: 1.09-4
  Version table:
 *** 1.09-4 0
        500 http://br.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
        100 /var/lib/dpkg/status

Please note that I'm not trying to wake up this machine, I'm trying to ***send magic packets to wake up other machines***.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: etherwake 1.09-4
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Mar 31 19:50:31 2014
InstallationDate: Installed on 2014-03-07 (24 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227)
SourcePackage: etherwake
UpgradeStatus: No upgrade log present (probably fresh install)

J Queiroz (zekkerj) wrote :

Is WOL active on the receiving machine?

Run "ethtool eth0" on that machine and look for

Supports Wake-on: g
Wake-on: g

If the second line is empty then run "ethtool -s eth0 wol g"

J Queiroz (zekkerj) wrote :

There's no problem on the receiving machine.
The problem is only on the ***SENDING*** machine, that just don't sends the magic packet.

I confirmed this behaviour using Wireshark both on the sending and the receiving machine.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers