OPNsense Forum

English Forums => 25.7 Series => Topic started by: jonny5 on July 28, 2025, 06:35:37 PM

Title: Wake On LAN Dashboard does not show active status correctly
Post by: jonny5 on July 28, 2025, 06:35:37 PM
I have several WOL hosts on my network, and I can trigger them to turn on, that works.

What does not work is the 'active status' on the WOL Plug-in Dashboard on the OPNSense. Further, it seems you have to 'wake all' now from the Wake On LAN plug-in menu... it seems you cannot select a specific device to wake up when in the plug-ins menu?
Title: Re: Wake On LAN Dashboard does not show active status correctly
Post by: jonny5 on July 28, 2025, 07:36:03 PM
There's a patch:
opnsense-patch -c plugins a80156815
should've read the posts before posting... thank you everyone and Franco!!!

Title: Re: Wake On LAN Dashboard does not show active status correctly
Post by: franco on July 28, 2025, 07:52:58 PM
Sorry, I was only the one advocating for the change that broke it (but for the right reasons if that counts for anything).  This and other similar issues will be patched in 25.7.1 later this week.


Cheers,
Franco
Title: Re: Wake On LAN Dashboard does not show active status correctly
Post by: Gobd on July 29, 2025, 02:18:36 AM
I noticed this issue as well, I'll wait for the 25.7.1 rather than using the patch since it's not a big deal.
Title: Re: Wake On LAN Dashboard does not show active status correctly
Post by: abenaou on July 31, 2025, 09:06:45 PM
I upgraded to the 25.7.1 and I still don't see the individual wake up button, I used a private browser window but still the same issue.

Is this a know problem?
Title: Re: Wake On LAN Dashboard does not show active status correctly
Post by: Monviech (Cedrik) on July 31, 2025, 09:08:31 PM
https://forum.opnsense.org/index.php?topic=48256.0
Title: Re: Wake On LAN Dashboard does not show active status correctly
Post by: abenaou on July 31, 2025, 09:24:30 PM
Quote from: Monviech (Cedrik) on July 31, 2025, 09:08:31 PMhttps://forum.opnsense.org/index.php?topic=48256.0
Thanks for replying back, I guess I am just going to wait for it be fixed in the upcoming version, I want to keep a consistent build.