I’m currently struggeling with the Wake-On-LAN feature. I think the reason may be our somewhat esoteric network configuration (192.168.x.x with a subnet mask of 255.255.0.0 instead of the “classic” 255.255.255.0). As seen on viewtopic.php?f=11&t=549&p=2327 something has changed in the past with respect to subnets and WOL. I wonder if the subnet mask/broadcast address is derived from the IP address or retrieved from the network adapter.
My machine is configured as 192.168.128.3 with a subnet mask of 255.255.0.0. When I send a WOL broadcast via Deadline Monitor, the resulting WOL packet (captured via Wireshark) contains a destination address of 192.168.128.255 instead of 192.168.255.255 which could be the issue as the target machines are mainly on 192.168.192.x.
Any insight would be greatly appreciated!
Thanks in advance
Dennis, finishing an otherwise seamless update to DL3
What we could probably do is send the magic packet 4 times, once to each of the following addresses:
..*.255
..255.255
*.255.255.255
255.255.255.255
That should cover all cases, and ensure that machines in different subnets will always receive at least one packet. Since the mac addresses are unique, it’s not like this is going to wake up more than one machine anyways. What do you think?
Well you could always divide your netblock and have subnet masks ending in 128, 192, 224, 240, 248, 252, 254 as you have 32 subnet masks available (0 to 31 bits network address). Broadcast addresses would be possible with one up to 32 lowest bits of the address set to 1. I think you could either send the magic packet 32 times (as you said, no harm done and not much traffic either) or retrieve the broadcast address from the device used to send the packet (the “clean” way but definitely more complicated to code). Both approaches should cover all cases I think…
