Not the typical WoL Question
What is the actual underlying mechanism used to deliver a wake on LAN (WoL) magic packet to the intended host computer? I am very familiar with using WoL through LMI, so I am reasonably confident...
Forum Discussion
etb Since we store the MAC address on DB side, we likely don’t need the ARP cache. As long as another LMI host is present on the same LAN, that should be able to broadcast the magic packet with the WOLable host MAC.
Hi AshC ,
Thanks for your response. What you said here was generally my understanding, but there were/are many of our LMI hosts present on the same LAN, yet only about half of them were able to WoL through LMI after the new hardware firewall was installed.
After my original post here, all but 1 of our other hosts have actually returned to being WoL-able through LMI. There was nothing I could figure to do to resolve the issue, so I really didn't do anything. I had tried restarting the hosts multiple times, shutting them down all the way and starting them up again, etc, but it did not seem to help. They seem to have just eventually resumed working on their own. As I mentioned, about half resumed working pretty much right away. Then all but 3 were working within about 1 day later. But as of today, I believe there is still 1 host that is not WoL-able through LMI.
So I am mostly okay right now, but I would like to know how to prevent or fix this in the future in case I need to take the network down again in the future. Is there some way that I can trigger LMI's DB to refresh and recognize that all of our LMI host computers are on the same LAN? Or something like that?
I'm not sure if illustrations might help. See a couple snips from my Central dashboard right now.
The following 2 images show the case of the 1 LMI host that I described is still not WoL-able. This is the only one that is still affected, though there was a point were about 50% of our hosts were like this.
