I'm running Home Assistant in a Docker container that's on an internal bridge network, and I'd like to wake my PC from it. However, since I can't access my home network directly or broadcast from the isolated container, I've set up this system: I have a proxy service connecting the internal network and an external network. I then created a second proxy using the host driver to help with the broadcasting. Although I've managed to send the magic packets and confirm they're being received on Wireshark, I'm questioning whether my approach is overcomplicated or flawed. I'm also curious about the `--expose` flag on containers using the host driver—does it pose any security risks? Any advice or simpler methods would be appreciated!
2 Answers
It sounds like you're on the right track! Remember that Wake on LAN (WoL) operates at Layer 2, which won't work directly over IP. So your setup using proxies is logical. However, you might want to look into a dedicated WoL relay that can repeat the magic packets from your Docker network to your home LAN—that might simplify things for you!
Setting up a second proxy on the host can definitely eliminate isolation issues! With solid iptables rules in place, it could actually be secure enough. Just be cautious if you decide to expose any ports, as that could introduce vulnerabilities.
Exactly, I think I've bypassed the need to expose ports with the current setup. I'll keep an eye on security as I go along.
Thanks for the suggestion! That's definitely something I’ll explore further.