Some extra info
Any ddwrt router has the capability to remember mac adress and host ip adress. My asus rt66 has also a commandline in which i set my arp table manually. So after my server turns off, i still can wake up this server.
Works great!
Thanks for sharing.
Just to be clear so other ddwrt users can follow can you confirm this is what you did...
1. Fix MAC Address and IP association in ARP table
2. Port forward UDP port '9' to the IP reserved above
1. Fix MAC Address and IP association in ARP table
2. Port forward UDP port '9' to the IP reserved above
3. Send a magic packet to your Public IP
ThanX for sharing, and for the rest of people up here, this means, that of you have a low-end home router/fw, that you have to hack it, and add your own firmware to it, making warranty goes away
Nope...Cuz you never read the pinned FAQ for this fora, stating that for a vote to be valid, you should press the like button on the first post in the thread.
And when that's said.....did you actually read every post in this thread before trying to vote?
Cuz if you did, you would have noted, that it req. either high enterprise routers/switches or a carefully selected home router, that has to be hacked, in every instance on the way from issuer of WOL to the end target.
As such, it's IMHO doubtful that Plex will ever impliment this, since it'll only work in a local network, and the only benefit would be, that you didn't have to walk to your server, and press the button
WOL is an essential feature for me, looks like its back to XBMC :( Plex was looking so promising with all its streaming capabilities. Why is there always 1 or 2 features lacking in every media centre platform? aaaargh!
I would love a WOL feature as my Plex server is in the basement and I need to start an additional WOL app before I can start the Plex client.
Should be easy to implement for local servers: If Plex server is in same subnet as client, store server's MAC address on configuration of the client and send WOL magic packet if server is unreachable...
I can only agree to previous posts. Being able to start PMS and Plex client computer using WoL is a nice feature. Have a look at Yatze android app for XBMC. It has the ability to send WoL package. The Plex android app also has some other stuff to learn from Yatze...
Want this so my server can take a rest once in awhile. Only downside is itāll take a min for it to wake back up and some from of session cache will need to be implemented to clients so they still think the server is there.
Want this so my server can take a rest once in awhile. Only downside is it'll take a min for it to wake back up and some from of session cache will need to be implemented to clients so they still think the server is there.
Or you just put a waiting screen 'PMS is starting'. From sleepmodus in Windows it will just take 5 seconds.
This āproblemā occurs only when your computer is completly turned off. Then you need to change your routers ARP table and give it a fixed adress.
When your computer is in sleepmodus, WOL will still works without changing this ARP table, because your router still āseesā your computer. Sleepmodus will consume around 5W. Much better than the normal 100+W usage.
So you can wake up your server from every place, any timeā¦
This feature will ensure that you donāt need to build your own energy efficient Plex server, but now you just can use your home PC without having a expensive energy bill. Also you can now build a powerful server which do multiple HD transcoding and still can be efficient.
I'd like this feature for my setup. Ā I have a Mac Mini that is the Plex Media Server, amongst other things, and it is on 24/7. Ā I have a 10TB unRAID server that stores all the media. Ā Would like to sleep the unRAID server when Plex doesn't need it, but have Plex wake up the server when it does. Ā That way, no matter if I'm accessing locally or from the WAN, PMS will wake up my disk drives.
I sleep my drives - but the server case they are in still puts out a good bit of heat. Ā I still would like this feature so I can sleep my server, reducing energy consumption and heat generations.
For servers, that are only used for Plex, this would be great.
It's really annoying how the thing is basically on 18h+ a day just idling around.
Please implement a Wake-On-Lan control logic into Plex. The server should only be required to spin up, if clients are actually accessing it. Contrary to what some people have stated here, it is perfectly reasonable for a "server" not to be accessible all the time. It just doesn't make much sense for servers that are frequented often.
Wake-of-Lan AND Wake-of-WAN implementation for Plex Player (Ios, WP ect...) woud be great.... Specially for people that install Plex sever on a real server (WHS 2011, WS) with a stand-by mode actived.
For servers, that are only used for Plex, this would be great.
It's really annoying how the thing is basically on 18h+ a day just idling around.
Any modern chipset will actually drastically reduce the power utilization during idle. Using a reasonably power-conscious CPU (say, an AMD 605e) can give you reasonable power without needing heavy wattage 24/7. This can be much more effective than WOL without the relatively high-impact power-on and power-off cycles that are particularly dangerous for physical disks.
A really simple implementation of WOL that would only work on the local LAN (or require advanced router configuration) would be for each client to remember the MAC address of the Plex server it talked to last (or get it from plex.tv) and send a WOL packet anytime the server is unreachable. This isn't really practical for most users. I am guessing something similar to this is how XBMC's plugin works.Ā
Because of the nature of WOL a reliable implementation that would work from anywhere would need to be structured similar to log me in and would require at least one active client on the local network.Ā
I am not really sure what the nature of the current connection back to Plex.tv is but the way to make this work would be as followsĀ
The server would need to register as online/offline with Plex.tv (which it does now)Ā
Each client would need to either maintain a persistent connection or be scheduled to "check in" every few seconds with Plex.tv
When a request to talk to an offline server is made the client would send that request to Plex.tv which would in turn hand a command to all other online clients asking them to send out a WOL packet to the MAC address of the plex serverĀ
Each client would then have to be modified to handle an appropriate amount of wait time to allow the plex server to start responding again
Additionally each client would need to be able to produce a suitable error message if no clients on the same LAN as the Plex server were currently on and able to send the WOL packet
and 2000 other things I cannot think of right at the moment
On top of all that I am reasonably sure a thin client device like a Roku would only be able to issue the WOL packet if Plex were left open and running. I suspect smart TV apps would have similar limitations. Chromecast is a different animal all together and I don't know if that could really work at all.Ā
When you tie together all the things that would need to happen to make WOL work smooth and for everyone it kinda turns into a rather large amount of work to implement. On top of that WOL is not the most reliable protocol in the world so I imagine the Plex guys would have a lot of associated support issues. WOL would be a cool feature but there are a lot of other things I would much rather see the plex team focus on.