Wake On LAN

So it appears when I woke up today I may have railed two lines of Fucking Retarded. Last night I spent ages learning how to use the CLI-based operating system on my server. It's now able to work as a web server with a shared main drive so I can load pages onto it remotely.

However I turned it off last night (I don't like it staying on at night because it's not energy-friendly and it's an ancient obsolete desktop from work that makes a sneezing sound after long operation) and forgot to turn it on in the morning before I left to test out some programs.

Thankfully I remembered I activated Wake-On-LAN so using one of the ports that the router currently forwards to it, I should be able to remotely turn it on. All I needed was the MAC address of the server. Thankfully that was on the web page I set up last night on some member webspace my ISP provided!

Except I changed that page last night because I need it there so I put in on the web server. Which is off.

Head, meet desk.

Thankfully home is 5 minutes away; I just wanted to be lazier then normal but alas, was not meant to be.

Regards,
Adam O'Grady

EDIT: Brute force is out of the question. Worst case scenario would be 274,941,996,890,625 tries (255^8 possible MAC combinations). Obviously the best case scenario is much nicer given that the first three octets are the manufacturer label and three would be a smaller number of them, but I'm going to just try and grab the MAC manually when I'm home.

UPDATE:
Turns out I'm actually limited by the modem not allowing subnet directed broadcasts. Better luck next time.