Yes, I know. I've shared the photo to other forums and platforms and the discussion seems split between those who adhere to the markings on the enclosure and with DSM, and those that prefer starting at 00 because other platforms use that notation, or they just think it look geekier? Either way, the decals are ultimately just for decoration, really.
I've been working out that DSM7 allows upnp2 rules to persist even if a QuickConnect or DDNS instance is closed and disabled. If the rules are manually cleared and DSM7 is restarted or awakened from its slumber the unused and unneeded upnp2 rules are forwarded to the router again.
Why do we spend ages trying to work out why they changed something that wasn't broken in the first place?
Then again I am on bed-rest after 4-days unexpectedly in hospital, so I guess I have time to burn...
Last week I discovered that one of the spokes just decided to stop syncing for about 3/4 weeks....
So, within 'Drive ShareSync' on the rouge spoke NAS I had to resetup the sync by deleting the synced databases of the impacted shares and initialized a new sync. Everything re-synced again but obviously had to manually fix a few conflicts as file/folder edits are done over the multiple NAS"es.
This is not the first time this happened and these boxes give absolutely no warning. Need to figure out how to monitor this. If I had some Windows machine running 24/7 , I could write a PowerShell script to just create a dummy file and check if this file appears on all the NAS'es as a way to monitor the syncs.