hilton
August 19, 2009, 7:58am
1
Right, decided to use WOL on a NAS box. It’s a brand spanking new HP ML110 with WOL enabled in the BIOS.
In RouterOS, I run the command /tool wol 00:01:02:03:04:05:06 (whatever the MAC really is) but bugger all happens.
I’ve checked the MAC and I’ve even tried the SolarWinds WOL utility but for the life of brian I cannot get this server to switch on.
Incidentally, I’ve tried WOL with other computers but nuffin work
What am I doing wrong? I’m sure it’s something rather trivial and silly but I just can’t get ANY computer to switch on.
Please put me out of my misery.
normis
August 19, 2009, 8:23am
2
did you try v3.28?
*) added ethernet broadcast support for WakeOnLan tool;
hilton
August 19, 2009, 8:28am
3
Alas that’s what I have both at the office and home.
If you say it’s working then I’ll believe you, it just seems like such a trivial issue and yet one that has me stumped.
normis
August 19, 2009, 8:31am
4
the other utility worked? if yes, make some sniffer files and send to support, so we can see what was different in RouterOS wol packet.
tgrand
August 19, 2009, 12:01pm
5
Gotta be a gonfig issue with the (un)waking hardware.
The WOL packet is almost to simple to get wrong.
hilton
August 19, 2009, 12:03pm
6
I agree. This is what is so frustrating.
I’m using a mix of 100Mb and Gig switches; would this perhaps be a cause of the problem?
I have this problem on some un-managed switches. Some switches will not send traffic out a port until traffic first comes in that port. I’m not sure if it’s a timeout or MAC table expire issue.
hilton
November 2, 2009, 2:51pm
8
Turned out I wasn’t doing anything wrong, it was a bug.
It’s now working as expected (4.1)
And these people are relied upon to keep your network running… hmm…
There are two well known projects (wakeonlan and etherwak) that are used in every linux router operating system. Did one of these packages have a problem?