KACE Product Support

From the support site:

How does KBOX wake on LAN work?
A device supporting Wake-on-LAN keeps it's network port powered up and is listening for a specific pattern that includes 6 bytes of all 1's, followed by the device's MAC address repeated 16 times. Since the device doesn't have an IP address when it is in this state, the typical way to get a wake-up frame delivered is to send a broadcast packet to the subnet that the machine is sitting on. This wake-up frame can be encapsulated in any protocol.

The KBOX implementation encapsulates the wake-up frame in a UDP packet sent to port 7 on a number of broadcast addresses. We use the device's last known IP address and loop over the possible subnets from */16 to */32, sending a packet to the broadcast address for each subnet. A lot of these packets will "miss" because they're not correct. The KBOX does it this way to avoid requiring the user to enter the subnet for each address. Note that when we send to the /32 subnet, we're directly addressing the device.

Yeah, that is actually what I found. From that, I concluded that it looked like it was a directed broadcast. I just wanted to make sure. We are having issues waking up computers at offsite locations and VLANS. We are trying to figure out the best way to handle it.

The "broadcast address for a subnet" is another way of saying subnet's multicast address.

The problem that we have is that, if a machine is off, the K1000 will have no way of knowing where it is, so it takes a best guess as described above.

ORIGINAL: jkatkace

The "broadcast address for a subnet" is another way of saying subnet's multicast address.




You know, I read that about 4 or 5 times and did not see that! [8|] Thanks.

Wake on LAN doesn't work very well on the K1000. I can take a brand new PC out of the box and power it on long enough to retrieve the MAC address, then shut it back down. If I manually enter the MAC and any valid IP address on the network into the K1000 Wake-on-Lan Manual Entry section, the PC won't power on. My understanding is that the IP address is only needed so the K1000 knows what subnet to send the broadcast packet on. I have tried third party freeware WOL tools such as SolarWinds, and they wake up the machine just fine.

What I have found is that if a PC on the network is getting its IP address using DHCP, WOL from the K1000 will turn on the PC if it uses the last known IP for the machine, AND no other PC has been assigned the IP you are trying to use.

WOL by KACE is arp dependent.  There is a uservoice article to vote on if you want this changed.

 

http://kace.uservoice.com/forums/82699-k1000/suggestions/3939749-wake-on-lan-to-be-not-dependent-on-arp-cache