[Not Accepted] Wake On LAN option for Interfaces

Problem/Justification
(What is the problem you are trying to solve with this feature/improvement or why should it be considered?)
My NAS is only running if it is really needed and later shut down. So I want to start my NAS remotely using the Wake On Lan functionality.

Impact
New (optional) feature to start a NAS remotely.

User Story
Go to “Network” and “Edit” one of the “Interfaces” in the list.

A new option should be (maybe as a drop down) with the following options:
d Disable (wake on nothing) - Default
p Wake on PHY activity
u Wake on unicast messages
m Wake on multicast messages
b Wake on broadcast messages
a Wake on ARP
g Wake on MagicPacket™

This setting can be set using the ethtool (already pre-installed on the system). For more details check:
https://manpages.debian.org/bookworm/ethtool/ethtool.8.en.html#wol

Or this can be set directly in the /etc/network/interfaces.d/ file.

This was originally reported here.

Would love to see this feature

Also having the reverse would be nice. I have a second TrueNAS server where the motherboard supports Wake On Lan, but there is not an easy way to settup a task every week to wake up the second server before replication. I am looking at getting a docker container to do that, but it would be nice to have something trusted and built in.

Thank you for submitting this feature request. After keeping it open to gauge community interest, we’re closing it as it hasn’t received enough votes to prioritize for development.