Discuss, seek assistance, and report issues related to hardware components, such as hardware platforms, memory, network ports, power supplies, UPS systems, and so on.
You do realise that you have to select your date format in the control panel? Or, are you saying that whatever application you were using was not adopting the designated format?
FWIIW a NAS is a server and would not be designed from the outset to be turned off and on based on some external user's needs.
We will verify the issue you mentioned regarding the Wake-on-LAN (WOL) function not working properly.
As for the date and month order problem you referred to, perhaps we can attempt some optimizations to help you distinguish them more clearly.
Regarding the connection speed of TNAS Mobile, please check if your mobile device has enabled a dedicated VPN service for the TNAS Mobile app (icon resembling a key). If the dedicated VPN service on your mobile device is disabled, remote connection speeds will only support basic access.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
The cause of the issue has been identified and the problem has been fixed. Please wait for the subsequent version update.
This issue is an compatibility problem between the 424 Max model you are using and the network tool. Other TNAS models do not have this problem.
Apologize for the inconvenience caused to your WOL usage. And thank you for reporting the issue to help us improve TOS.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Would you mind telling me which specific version of TOS6 you are currently using? (6.0.xxx)
Hello, my version is 6.0.794.01324 and seems to be the last proposed version of the security system.
And i confirm you never solved this problem, juste asking questions and saying it will be solved or "it is already solved" like each time.
So my network turn off with the nas half the time (instead ok keeping alive and listening the port).
I am also wondering why there is no wol item on tnas mobile.
Seems to me it does not really matter if you can find the wol settings or not.
The help files state that wol ONLY works on LAN1 - I presume they mean eth0. I have done a bit of digging and it seems that (in some cases?) wol is deliberately disabled on interfaces other than eth0 (eg 'ethtool eth1 == Wake-on d'). Plus it seems it is possible to enable it using 'ethtool' on any standard interface. Whether it will work, or not, is debatable since wol also does not work on bonded interfaces.
More to the point, is it even a consideration if when a device is shut down, the network interfaces are effectively dead. It appears that wol only works when a system is suspended (ref Ubuntu based devices).
I'm not sure how wol is actually configured under TOS as it seems it does not figure in the standard 'systemctl' services. It may well be that TOS has "moved things around" as with other functions. I would delve deeper, except I know that either on install of a new version or on reboot everything will be overwritten (again).
So, does @TMSupport have any bones they can toss us? For myself, I would like WOL to work on all interfaces including aggregated/bonds. I would also like it to be configurable to work on other triggers (there are several). Magic Packet is OK but that tends to limit and the port needs to be known. I have different wakeonlan apps that can use different triggers but only one that only uses Magic Packet.
Gremlin wrote: ↑01 May 2026, 23:06
Seems to me it does not really matter if you can find the wol settings or not.
The help files state that wol ONLY works on LAN1 - I presume they mean eth0. I have done a bit of digging and it seems that (in some cases?) wol is deliberately disabled on interfaces other than eth0 (eg 'ethtool eth1 == Wake-on d'). Plus it seems it is possible to enable it using 'ethtool' on any standard interface. Whether it will work, or not, is debatable since wol also does not work on bonded interfaces.
More to the point, is it even a consideration if when a device is shut down, the network interfaces are effectively dead. It appears that wol only works when a system is suspended (ref Ubuntu based devices).
I'm not sure how wol is actually configured under TOS as it seems it does not figure in the standard 'systemctl' services. It may well be that TOS has "moved things around" as with other functions. I would delve deeper, except I know that either on install of a new version or on reboot everything will be overwritten (again).
So, does @TMSupport have any bones they can toss us? For myself, I would like WOL to work on all interfaces including aggregated/bonds. I would also like it to be configurable to work on other triggers (there are several). Magic Packet is OK but that tends to limit and the port needs to be known. I have different wakeonlan apps that can use different triggers but only one that only uses Magic Packet.
For models where only LAN1 can respond to WOL, we currently have no way to make their other network interfaces also respond to WOL.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
We heard you, we will verify the issues you reported.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
