News for hackers. Stuff that matters.
Re:Show HN: Wake-On-LAN without public IP or port-forwarding by peterwwillis on Tuesday July 29, 2014 @04:33PM (#8104843)
So basically OpenWRT + "wol" package + google app engine. Write a google app engine script that takes a 'wake up machine' html form, write a bash script on OpenWRT that queries the script regularly, and run the "wol" client when you get a response. Seems useful.
Re:Show HN: Wake-On-LAN without public IP or port-forwarding by jeffijoe on Wednesday July 30, 2014 @02:03AM (#8106655)
I was experimenting with new technologies for this project - yes, to get the core functionality sure this would work. In this case, I wanted to make something more... complete. The communication with the device uses websockets, not polling.
Re:Show HN: Wake-On-LAN without public IP or port-forwarding by gue5t on Tuesday July 29, 2014 @04:16PM (#8104730)
MAC addresses are bitstrings typically written in hex and should not be interpreted in a case-sensitive manner. You should also accept colons, dashes, or nothing as the byte separator.
Re:Show HN: Wake-On-LAN without public IP or port-forwarding by jeffijoe on Wednesday July 30, 2014 @01:56AM (#8106637)
I'll look into that.
Re:Show HN: Wake-On-LAN without public IP or port-forwarding by dmarlow on Tuesday July 29, 2014 @06:45PM (#8105427)
You can also use http://www.smscmd.net/ to connect your raspberry pi/arduino/<insert device> using MQTT and then you can wake your device using SMS.
Re:Show HN: Wake-On-LAN without public IP or port-forwarding by jeffijoe on Wednesday July 30, 2014 @01:59AM (#8106641)
Does it give you an online|offline status indication of your device?

Smart app though!

Re:Show HN: Wake-On-LAN without public IP or port-forwarding by fragmede on Tuesday July 29, 2014 @04:23PM (#8104780)
You should offer up an SD card image to download.

(No, I'm not going to tweet that at you.)

Re:Show HN: Wake-On-LAN without public IP or port-forwarding by jeffijoe on Wednesday July 30, 2014 @02:05AM (#8106659)
Will work on that.

(Why was that last line necessary?)