WOL not working

Lockheed · 2012-03-05 10:09:44

Do you have an idea why the windows command

WolCmd.exe 00902789FB02 192.168.7.12 255.255.255.0

but linux command

wol -i 192.168.7.12 00:90:27:89:FB:02

doesn't?

Last edited by Lockheed (2012-03-05 10:10:25)

scar · 2012-03-05 12:15:07

andif you try : wol 00:90:27:89:FB:02 ?

Lockheed · 2012-03-05 12:18:33

This one works on LAN, but I will need to run it from the internet through router's port forwarding and I don't think it will forward it if I do it this way, without the IP.

scar · 2012-03-05 12:22:08

Exactly. But you will need to specify the EXTERNAL ip of your router.

wol -i <your.external.ip.address> 00:90:27:89:FB:02

and you'll have to forward the right port to your target machine. ( 40000 by default, if I remember well )

Lockheed · 2012-03-05 13:44:19

That's the problem It doesn't work with -i even if I use local IP.

xephinx · 2012-03-05 16:26:27

Lockheed wrote:

That's the problem It doesn't work with -i even if I use local IP.

I use for wake on lan this:
https://aur.archlinux.org/packages.php?ID=52919

Here is the usage:
https://github.com/Asfaloth/Woly/blob/master/README.md

R00KIE · 2012-03-06 14:09:32

My knowledge of the OSI layers is a bit rusty, but from what I can read on wikipedia it seems that you might be out of luck unless you put the machine you want to wake up in the DMZ. Wake on lan might not use tcp or udp so forwarding a tcp/udp port will not work I suppose.

Different implementations (software wise) of wake on lan do things differently so you may want to try a few different programs. You really should at least read [1] and then try to move to more specific pages.

I have seen cases where a recently powered off machine would wake up fine but if left alone for some time (say 1 week) it would not wake up, even though the router would say a link was detected at the port used by the machine in question, so I'd say you might want to start with a direct connection to see if things work and then move from there.

[1] http://en.wikipedia.org/wiki/Wake-on-LAN

xephinx · 2012-03-06 18:41:38

R00KIE wrote:

My knowledge of the OSI layers is a bit rusty, but from what I can read on wikipedia it seems that you might be out of luck unless you put the machine you want to wake up in the DMZ. Wake on lan might not use tcp or udp so forwarding a tcp/udp port will not work I suppose.

Hey R00KIE,

WoL is a stupid (= very simple) protocol.
The network card just checks for the Magic Packet sequence.

TCP will never work, because it's connection oriented. The 3-way handshake won't work with only one hand

You have to forward a UDP port on your router which routes the UDP traffic to your sleeping computer.

Then call Woly:

$ ./woly -4 -h YYY.YYY.YYY.YYY -p ZZZZ -m XX:XX:XX:XX:XX:XX

Where:
YYY.YYY.YYY.YYY stands for your public ip address (http://whatismyip.org)
ZZZZ is the forwarded port
XX:XX:XX:XX:XX:XX is the MAC address of the sleeping computer

hope my post was clear enough (-;

R00KIE · 2012-03-06 21:05:51

I knew tcp wouldn't work, but there is no assurance that the used program will use udp either (unless that can be forced or the program explicitly says it uses udp), to quote wikipedia:

The magic packet is a broadcast frame containing anywhere within its payload 6 bytes of all 255 (FF FF FF FF FF FF in hexadecimal), followed by sixteen repetitions of the target computer's 48-bit MAC address, for a total of 102 bytes.
Since the magic packet is only scanned for the string above, and not actually parsed by a full protocol stack, it may be sent as any network- and transport-layer protocol, although it is typically sent as a UDP datagram to port 7 or 9, or directly over Ethernet as EtherType 0x0842.

The problem is if one is trying to use a program that sends the packet as EtherType 0x0842 and expecting it to pass the router, and believe me, I've seen both implementations. That is why I suggested to try different programs as some send udp packets and others use EtherType 0x0842. Even on the local network things might not work well, or the cards might not like one of the ways of doing it, that is why I also suggested to start with a direct connection if possible and then go from there.

On another note, make sure you activate wol *every* time before you turn off the machine as that setting is reset every time the driver is loaded (that can be done on rc.local).

Arch Linux

#1 2012-03-05 10:09:44

WOL not working

#2 2012-03-05 12:15:07

Re: WOL not working

#3 2012-03-05 12:18:33

Re: WOL not working

#4 2012-03-05 12:22:08

Re: WOL not working

#5 2012-03-05 13:44:19

Re: WOL not working

#6 2012-03-05 16:26:27

Re: WOL not working

#7 2012-03-06 14:09:32

Re: WOL not working

#8 2012-03-06 18:41:38

Re: WOL not working

#9 2012-03-06 21:05:51

Re: WOL not working

Board footer