Replies: 2 comments
-
This situation is a bit complicated, and currently only WOL on the same LAN has been implemented. I understand your need, but I can't assess whether this is reasonable or should be implemented. It depends on the author's plan. |
Beta Was this translation helpful? Give feedback.
0 replies
-
It is an old feature on TeamViewer, but now, I use this: https://github.com/seriousm4x/UpSnap |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There are several threads here about WOL (wake-on-lan) and how to make it work. All the comments seem to be about machines that have been identified using discovery, and where there is a panel (or CLI) available to initiate the WOL.
Other remote desktop apps have a WOL functionality that doesn't seem to work using discovery. Instead, WOL is performed by another machine at the remote site.
Example: at a remote site, I have two machines with the client installed. Machine A is sleeping, Machine B is awake but I cannot currently access it (it's accessible only if a user is there to accept my connection). In this circumstance, (e.g.) AnyDesk will transparently use machine B to wake up machine A , even though I don't have control of machine B.
I see a message like "trying to wake machine using another machine at that site". This allows me to wake a machine where I have no active control of any machine at that site.
Is this:
A. not implemented in rustdesk but planned for,
B. not ever intended to be implemented,
C. theoretically implemented but people can't get it to work, or
D. working correctly in rustdesk for at least some users?
Beta Was this translation helpful? Give feedback.
All reactions