(sorry – your credentials on both computers must allow you to create the TAP device). On the basis of mention I included the important parts of the source below.ġ) both computers must have root login enabled. Therefore I see no reason to do without sending machines to sleep. There is a fancy way to build a Layer 2 tunnel with SSH, and with this WOL should work well. This means configuring the VPN gateway/finding an option, to forward broadcast traffic from VPN remote clients to the local network. So routing it is really straightforward, the issue may lie with broadcasting it correctly from the target VPN gateway. As long as the VPN client has the correct routes, it can send a broadcast packet such as 192.168.1.255 (a broadcast address) correctly to the VPN gateway across the internet. Most implementations of the magic packet use UDP port 9 although this really does not matter as long as it is routed correctly and transmitted on the same broadcast domain as the target computer.
So essentially it becomes a matter of getting a regular routable packet to the target host with the "magic" sequence inside its payload. The reason for this is the "magic" sequence can be anywhere within the payload. Yes the WOL magic packet is defined within the constrains of layer 2 but this does not mean it cannot be contained inside a network and transport protocol entity which can then be used to route it across the VPN. Old thread but I wanted to chime in because it is still the top rated search result for "wol over vpn".
0 kommentar(er)
