Hi RLK,   Thanks for that, I have tried a few things and ended up resetting the router, it is working now!   A few notes summarised, in case somebody else is wondering:   If computer A is on the network on a TP-Link VR1600v (HW v2 in my case)use   To wake A: - Ensure MAC and IP for machine A are bound: Advanced -> Security -> IP & MAC Binding   If machine B is on the network: wake on lan to broadcast address works (192.168.1.255), but cannot address (bound) IP of A directly (192.168.1.10 in my case)   If B is on the internet: Go to Advanced -> VPN -> OpenVPN, enable VPN server and allow access from 'Internet and Home', generate certificate and download the config file. Might also be worth setting up Dynamic DNS (I use NO-IP) otherwise the IP in the script will need to change when the router reconnects to the internet, unless it is static.   To set the VPN connection, in Linux with networkmanager I run:       sudo nmcli connection import type openvpn file <path to *.ovpn file>   I then have a script like the following, which uses a command line WoL utility called wakeonlan:         #!/bin/bash       nmcli connection up <name of connection>       sleep 1       wakeonlan -i <bound IP of A> <MAC of A>       sleep 1       nmcli connection down <name of connection>   PS: You can also connect to the VPN when on the network if you want to WoL using the bound IP instead of the broadcast address.   I can then SSH into A from anywhere! I hope this is useful, many thanks for the help.   Regards,   Cam     ... View more

Hi,   I just tried to set this up myself. With port forwarding to the broadcast address blocked, I also went the VPN route. I can successfully connect to the router, however the magic packet sent to the broadcast address (192.168.1.255) still does not trigger a broadcast. Addressing it to the IP (bound and reserved) directly also does not work (192.168.1.10 in my case). I expect the arp table entry is thus not really static and only reassociated once the client connects.  One interesting observation using tcpdump (a packet sniffer). Connecting via vpn: packets sent to regular IPs seem to originate from the VPN, anything sent to broadcast originates from the machine it is sent from directly somehow circumventing the VPN connection, which is beyond my level of understanding of VPNs.   Regards,   Cam ... View more