-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request WOL (Wake On Lan) #159
Comments
While I agree this would be a nice feature (that I would also find useful), I think this is non-trivial to implement. WOL packets are sent via the network broadcast address and are implicitly link-local. Default docker networks are created in bridge mode, creating their own LAN and any WOL packet from sablier wouldn't be forwarded to other hosts on separate networks (i.e. your LAN). I think there are some workarounds, but am not sure on their reliability. The alternative is running sablier or traefik in host mode, which is probably a bad idea if exposed to the internet. A better solution might be to have the capability to send an arbitrary GET request to another host running a microservice that can fire off the WOL packet. You could then trigger other automations too via webhooks in home-assistant, node-red, whatever... |
WOL is layer 3 and this solution is more layer 7, maybe using with another services that support WOL like, UpSnap, added a rule on midleware to call the api. But this sounds out of scope. |
I would be also interested in that feature, but if its out of scope then adding ability to execute shell command |
While the API is layer 7, the calls it can make are not bound to any layer. I think it's a very neat feature actually ! |
Send a Wake On Lan packet to a predefined device. maybe add the possibility of setting a minimum wait time.
The text was updated successfully, but these errors were encountered: