It’s been two days since I’ve been trying to get a family NAS equipment, and I’ve bought a group of DS218plays and a coyote hard drive in Kyoto, and I’ve been feeling:
It’s hot.
Use
The following features are commonly used:
Time Machine
Backup with Time Machine is always connected to the mobile hard drive, it’s troublesome and easy to forget, often, Mac reminds me that I’ve been missing it for over 10 days to put it back on the mobile hard drive, have NAS and then get a wireless and remote backup, and have Mac automatically back up in the NAS every hour.
# BT download
[nas2] (./attachments/bafkreihslhp7jkexowwnodr3psplblsxptdbbgiq34k32vngowvdyaprwe.jpeg)
Use RSS subscriptions to favorite dramas or aesthetics, with updates that can be downloaded automatically, or see a favorite movie at the company’s time of poaching fish, to log in remotely to the family’s herds, add a BT mission, and go home at night.
Storage
This is NAS’ most basic function, and its greatest benefit can be quickly shared between different devices.
For example, I put a picture of Sakura in NAS on my computer.
[NAS3] (./attachments/bafkreiawzddlndpjamroaxnqjrjq44rypjz3blmdvsb2s3v5v7cqghkbt4jpeg)
And for example, I downloaded a Japanese play that, depending on how I feel, I might want to sit at the table and watch with a computer, or I might want to lie in bed with an iPad.
[nas4] (./attachments/bafkreic 543swlcdjvk4ujstenilfqljshk5tjyh6h3xfjp7x6knmpzvde.png)
And before there’s NAS, I have to connect iPad to the computer with data lines, open the hard-won iTunes, and then copy the video into iPad to see it.
Deployment
There’s a QuickConnect that can assign a QuickConnect domain name that can be used to connect directly to the public network.
But I wanted to tie up my domain name, but I did it.
Port forwarding
To match the extranet to NAS.
The telecommunication broadband in the home already has a public network.
[nas5] (./attachments/bafkreiawy6iujwauiuujqh6j3s5ygol4ceupvxn7sodbp47hgfp6df2oc4.jpeg)
When the router ‘s DMZ function is set for forwarding, it’s not working, access to the public network IP returns the cat login interface, and it’s not a bridge, it’s going to have to be on the cat.
Google found out a couple of telecommunication photocats that didn’t work.
The telecommunication master came in this morning and gave the Superman account.
Super Administrator’s account went backstage, set the cat and router to a bridge back port.
DNS
To map the dynamic public network IP on my domain name
[nas6] (./attachments/bafkreic3k3b23ob5hft7huhjdudwfpp6mla6tyrucjzawfpsrjhwgd2et4.jpeg)
[NAS7] (./attachments/bafkreiccmdcgvxhbney7v3o4zjfq52fdfv7vrqoxo7wa4ksl7hpicazjiq.jpeg)
The swarms and routers carry DDNS, but they don’t support CloudXNS… they have to do it on their own.
This was discovered by surprise at https://github.com/lixuy/ClaudXNS-DDNS-with-BashShell
We’ll run this script for 10 minutes, and we’ll get the DDNS of CloudXNS.
# SSL Certificate
[NAS9] (./attachments/bafkreihajrzs55mrbb427pfa7j3fdndjdsdg7bw5rzmwc3ljmjt2etugom.jpeg)
The swarms bring the auto-certification from Let’s Encrypt.
But it turns out that the swarms have to be certified with an 80-port.
Solutions were also found: http://www.up4dev.com/2018/05/29/synology-sl-wildcard-cert-update/
It’s the same thing as running this script for a month, using the swarm mission plan function.
Finally, it was achieved through its own domain name, https://nas.diygod.me:22222, remotely accessed NAS, which was just seen in the first image of the article.