Wake on lan (WOL) Not working at all

(2012-04-13 12:13)Gekkegast Wrote:  The PC I'm trying to wake is connected with a wire. I'm trying to send the magic packet with my laptop connected to the same network using WIFI.

If you connect that laptop to your network using Ethernet (instead of WiFi), are you able to send the magic packet to wakeup your HTPC system? I know you previously said that you were able to use another PC (wired) to wakeup your HTPC, but I wasn't sure if you had done a wired test using your laptop.

Since your other wired PC can wakeup your HTPC, that indicates your HTPC is setup correctly for WOL. The issue then seems to be with your laptop.

It's strange that it makes a difference whether the machine you're using to wake it is on wifi or ethernet. I don't have Windows to test, but WOL is working on my XBMCbuntu machine (connected via ethernet), and it works the same if I ssh into my Ubuntu NAS (also connected via ethernet) and run etherwake, or if I use a WOL widget to wake it up from a MacBook that's connected via WiFi. The Android app works the same way when connected to the local network via WiFi, and even with WiFi turned off on my phone, I can use a DynDNS address instead of a local IP and it will wake my XBMCbuntu box.

I can also wake it up from the Mac (WiFi), Android (local WiFi, not over the internet) or my NAS (ethernet) from a full shutdown or in hibernation. It doesn't have to be suspended.

When you enabled wake in your BIOS, did you have any other options? I remember there were a couple of types of Wake on LAN in my BIOS. What do you get if you run the following command?

(2012-04-15 20:33)digitalb0y Wrote:  It's strange that it makes a difference whether the machine you're using to wake it is on wifi or ethernet. I don't have Windows to test, but WOL is working on my XBMCbuntu machine (connected via ethernet), and it works the same if I ssh into my Ubuntu NAS (also connected via ethernet) and run etherwake, or if I use a WOL widget to wake it up from a MacBook that's connected via WiFi. The Android app works the same way when connected to the local network via WiFi, and even with WiFi turned off on my phone, I can use a DynDNS address instead of a local IP and it will wake my XBMCbuntu box.

Thanks for checking it. I'm not home now, but when I am I will check if i can wake my machine using the same laptop connected with a wire. I will also try to wake the machine using the remote android app being not on the network.

(2012-04-15 20:33)digitalb0y Wrote:  I can also wake it up from the Mac (WiFi), Android (local WiFi, not over the internet) or my NAS (ethernet) from a full shutdown or in hibernation. It doesn't have to be suspended.

Nice, I will try that also. But im afraid that wont be work cause as I said in the original post that my power supply doesn't has a physical on/off button.

(2012-04-15 20:33)digitalb0y Wrote:  When you enabled wake in your BIOS, did you have any other options? I remember there were a couple of types of Wake on LAN in my BIOS. What do you get if you run the following command?

Code:

ethtool eth0 | grep Wake-on

Will report back when I'm home

http://wiki.xbmc.org/index.php?title=HOW...n_(Ubuntu)

When the computer is shut down, do you see a light on the Ethernet port? If yes, then the computer is still giving the ethernet port power, which is a good sign. If not, there is probably something wrong with the settings in the BIOS.

Also, waking on the Internet doesn't work well at all, the command needs to be sent from within the Lan.
This is what makes DDWRT's WOL command great.

I take no credit for this as the info was taken from a few places but I got WOL working on my Ubuntu boxes by doing the following (after making sure the necessary options were enabled in the BIOS):

1. Edit the /etc/init.d/halt file and change the "NETDOWN" option to prevent network interface being disabled at power-off.

2. Run the following command to check the status of eth0 - you are interested in the "Wake-on: x" line (you want it to be "Wake-on: g").

3. If it isn't set to "g" already, run the following command.

4. To force this option to be set at power-on, add the following to /etc/rc.local (before the "exit 0" line).

5. Reboot your system before testing.

Note: This is the list of options for waking with WOL:
p Wake on phy activity
u Wake on unicast messages
m Wake on multicast messages
b Wake on broadcast messages
a Wake on ARP
g Wake on MagicPacket™
s Enable SecureOn™ password for MagicPacket™
d Disable (wake on nothing). This option clears all previous options.

This is all that was needed on my HP N36L server but on my Acer Revo 3610 I found that in the BIOS, I had to enable WOL but also disable the option for "allow deep power off" (something like that) - the option under WOL.