Canada
Hi Guzzi,
Please find attached updates source (version 0402). I've also attached the new dll in case anyone wishes to give it a test run.
Wireless access points will not "route" general broadcasts, so a "directed" wake-up is required in order to wake-up a server on the LAN from a wireless device. This version calculates the broadcast address for the subnet where the server resides so that a directed wake-up broadcast can be sent to the subnet.
The implementation requires the subnet address for the server that needs awakening. I don't see a way to get that programmatically, so the plug-in attempts to find the subnet mask for the local adapter and uses this subnet mask for the broadcast address calculation (I say "attempts" because the local computer may have several IPs if it has multiple NICs, virtual or otherwise). Because the plug-in can't reliably tell what the local computer IP is (nor the server IP for that matter) to get the subnet mask, I've made those fields optionally editable in the setup screen. The user can then correct the settings if the plug-in makes the wrong "guess". Users should use "ipconfig" on the server to get the correct IP and subnet mask, but the "guess" should be correct for 99% of users.
The implementation now supports everything that a general WOL utility provides. You can wake up computers on the same or other subnets and even do so from the Internet if you set up port forwarding in your router's NAT settings.
I also took the liberty of cleaning up some of the English whenever I noticed something odd.
Please let me know if you notice anything wrong or not working as expected. I've noted that I can't get Manual Control to work on my PC, but I think it's a MP setup issue with using the blue button on my remote.
Please find attached updates source (version 0402). I've also attached the new dll in case anyone wishes to give it a test run.
Wireless access points will not "route" general broadcasts, so a "directed" wake-up is required in order to wake-up a server on the LAN from a wireless device. This version calculates the broadcast address for the subnet where the server resides so that a directed wake-up broadcast can be sent to the subnet.
The implementation requires the subnet address for the server that needs awakening. I don't see a way to get that programmatically, so the plug-in attempts to find the subnet mask for the local adapter and uses this subnet mask for the broadcast address calculation (I say "attempts" because the local computer may have several IPs if it has multiple NICs, virtual or otherwise). Because the plug-in can't reliably tell what the local computer IP is (nor the server IP for that matter) to get the subnet mask, I've made those fields optionally editable in the setup screen. The user can then correct the settings if the plug-in makes the wrong "guess". Users should use "ipconfig" on the server to get the correct IP and subnet mask, but the "guess" should be correct for 99% of users.
The implementation now supports everything that a general WOL utility provides. You can wake up computers on the same or other subnets and even do so from the Internet if you set up port forwarding in your router's NAT settings.
I also took the liberty of cleaning up some of the English whenever I noticed something odd.
Please let me know if you notice anything wrong or not working as expected. I've noted that I can't get Manual Control to work on my PC, but I think it's a MP setup issue with using the blue button on my remote.
