Motherboard Stand-by

[TMzethar]

Yes, it says LAN1 only. The problem arises if using aggregate bonds. Then WOL does not work as far as I can tell(On either port - assuming 2 ethernet ports). Tos does not seem able to set power configurations on the Bond(s).

This could be an important issue worth looking into. Could you please let us know which NAS model you are experiencing this problem on?

[Gremlin]

I was testing suspend on a F2-425+. (Silly me)
I have now done some more testing and I believe my issue may be within TNAS-PC or a combination.
I also have F2-424 - when looking at Tnas-PC I realise that in the "Access History" I see entries for 2 Bond connections plus an entry for LAN1 with the same IP address. This allows me to activate WOL successfully. I can also utilise a 3rd party app ok.

The 425+ has this issue - viewtopic.php?p=58331#p58331
such that in Tnas-PC I see a single Bond connection and the "errant" LAN1 at 169.254.0.0. THIS does not work.

All of which leads to another question of what should I actually be seeing in Tnas-PC? (In addition why does Tnas-PC not display the MAC address in Access History?)
Sorry this has gone a bit off topic.

[TMroy]

Thank you for your suggestion! It's a very practical idea. However, this feature cannot be easily addressed through software alone. Unlike a PC, which can be woken up via physical buttons, a NAS is typically a remote device. Implementing full-system sleep would require a separate wake-up mechanism, possibly even hardware modifications. We will discuss this internally and keep you posted if there are any developments. Thank you!