Hi,
Has anyone gotten WOL to work on the PCs connected to their RED?
I've been playing around with it but have only had limited success. I've found that if I send a WOL packet directed to the computer's exact IP, not broadcast, that I can wake up the PC. BUT only if I send the WOL packet within in a minute or so after turning off the PC. It seems that the RED puts the port into some kind of sleep mode after there is no activity. Even if another computer is plugged into the RED and is on, a PC that is off will timeout and not accept the WOL packet. It's really annoying.
I know that it must be the RED shutting down the port because I'm using three completely different computers on the RED network. At first, I was thinking that maybe the PC was going into some ultra-low powersave mode and was disabling the nic. Nope. They all work perfectly when connected to my local network. No timeout problem.
Trying to broadcast the packet isn't working either. For instance, my internal network is set to 10.0.0.1/16 and my RED network is set to 10.20.0.1/24. If I try to broadcast to 10.20.0.255, it doesn't make it. I've watched the packet filter log and nothing is coming up as being blocked. I've also tried broadcasting to 255.255.255.255 and that doesn't make it through to the RED network either.
I'm guessing that I need to route the broadcast traffic. I've tried a couple things with no luck.
With the PCs turned on, on the RED network, I've run this handy WOL packet sniffer...
Wake-on-LAN Packet sniffer
The WOL packet only makes it through to the RED network when I specify the computer's IP address, nothing comes through when trying to broadcast.
BTW, to generate the WOL packet, I've using both WOL from Simplyware and MC-WOL...
Simplyware Downloads
Wake-on-LAN [ MATCODE.com ]
Any ideas would be greatly appreciated. I'm new so yes, I'm probably doing something dumb. [;)]
Thanks,
Ben
This thread was automatically locked due to age.
