So far it's worked fine if I ever need to account for more metrics in detecting idle state, I'll consider using a more sophisticated option like circadian. To keep things simple, I opted for a cron job that triggers a bash script - check out the final version shared above. Count of connections on the AFP port (548), using lsof (I'm using AFP for Time Machine network shares)įor both metrics, I noted the values first at idle, and then again when the server was busy.I asked myself what server activity would constitute being busy, and landed on two things:Ĭhoosing corresponding metrics was pretty straightforward: In general, though, there didn't seem to be a standard/best-practice way to do it, so I decided I'd roll it myself the simplest way I could. I came across a few tools that looked promising, the most notable being circadian. Most of the guides I found for sleep-on-idle, like this one, were for Ubuntu Desktop - sleep-on-idle doesn't seem to be something that's commonly done with Ubuntu Server. How to automatically suspend to RAM after being idle for some time.How to determine if the server is idle or busy at any given moment.I started with sleep-on-idle, which boiled down to two questions: To prevent unwanted wake-ups, you'll need to ensure no device on the network is sending extraneous packets to the serverįirst, a bit about my hardware, as this solution is somewhat hardware-dependent:.The server's network device needs to support wake-on-LAN from unicast packets.It is almost the same as WoL but because the power plugs are many times designed to be access remotely from other network you should have less issues getting it to function from the wan side of the router.Systemctl status rvice Caveats You can then set the pc to boot as soon as it gets power. ![]() If you already have home automation software consider using one the automated power plugs that lets you turn outlets on and off. ![]() You are going to have to look through the manual and see if there is any special app, from the little I can find the router you call redmi is some kind of device made by XIAOMI and these appear to be very simple routers with not a lot of fancy features. Your other router would also need something similar. The fritz router actually is one of the rare ones that has a web interface. This would be something custom that is not actually wake on lan even. The only way to even think to accomplish this is if the redmi router has some special app that can be used to wake a pc. It has been explained multiple times why you can't make wake on WAN work. When the android device is on the same lan network it should be able to send a WoL packet. Why do you connect your android device to the fritz router why don't you connect it to the redmi router. Many times you must send the packet multiple times. WoL tends to not work real well even when it works. You could use something like a raspberry pi or buy a router that lets you log into the router and ask it to send a WoL packet on the local network for you. Other wise you need some device on the LAN to send the signal. Another way is to use the Bios option that boots on power restore and use one of the fancy power outlets that let you turn off and on the power remotely. There is almost no difference in the power consumption. ![]() The best option is to use one of microsofts power save/sleep modes rather than WoL. It might work for a few minutes but then ARP tables timeout in the router and it no longer function. The confusion comes because there are a bunch of apps written by people that do not really understand how this works and think you can use IP addresses. This means the wake signal must be sent from a machine on the same network/lan. The Wake on LAN uses mac addresses it does not use IP addresses. Your main problem is there is no such thing as "Wake on WAN". Your post is a little hard to understand.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |