search

basildane / WakeOnLAN

Wake On LAN, WakeOnLAN, shutdown software for Windows. A powerful WOL, ping, shutdown, GUI application.
http://wol.aquilatech.com
Other
998 stars 147 forks source link

how to make WOL work on different subnets #128

Open wolwol opened 5 years ago

wolwol commented 5 years ago

Hi i would like to ask if there is a way to make WOL work on different subnets in my network. The WOL program can find the PC in other subnets but it does not show whether it's online or offline. It just shows as "unknown" . I think i hav to do something with my router but i am not sure yet.

Thank you in advance

basildane commented 5 years ago

It uses "ping" to determine if the remote machines are online. Can you ping one of them, from the machine you installed WOL on? If not, let's look at firewall rules next.

wolwol commented 5 years ago

Thank y your for your kind reply. you meant "pinger" function in WOL software? when I hit the pinger function, it automatically shows online and offline machines and also unknown machines. On the list, machines are shown online in the same subnet but machines are in different subnet are shown as unknown. Could you please suggest me next steps i can try? Thank you again

Wrong-Code commented 4 years ago

Please see this article covering the same issue, on Linux:

https://robert.penz.name/294/workaround-for-routing-wol-packets-with-linux/

I've managed to setup an unused IP address on the target subnet and, assumed you have your router/firewall properly configured to forward the WOL magic packet, the workaround works, at least using another WOL app on my mobile phone.

Unfortunately, there doesn't seem to be a way to trick WakeOnLAN to use the workaround. You can put the fake IP address in either Broadcast address or FQDN/IP, but the remote host would not wake up. To be honest, I've tried with a remote host which is on the same subnet where the WakeOnLAN runs, I have no means right now to test with WakeOnLAN on a different subnet.

basildane commented 4 years ago

To send a WOL packet to another subnet, you use "broadcast subnets". For example, 10.0.20.255. That is a broadcast address in the 10.0.20.0/24 subnet. WOL supports this.

Another option is to use the Agent program to receive a standard packet and rebroadcast it out as a broadcast packet. This is typically used for WOL over Internet, where it is not possible to send a broadcast packet directly to the client because the Internet won't carry that.

Third, you ask about showing the status as online/offline or unknown. WOL uses the network ping function to do this. If it can ping the remote client, it shows it online. You can use the command line command "PING" to see if you can ping the client. If you cannot, then WOL will not be able to either. If the remote client is not routable, wrong name, or WOL doesn't know how to find it, then it will show as "unknown".

If you can go to the command line and try to ping the remote client, that would be good to see what the result is. Sorry this can be complex, and I've been too busy to respond quickly.