fokifloor.blogg.se

What I really like is the once-yearly free IDrive express service. Otherwise it's around $70/yr for 5TB which is still cheap. Use this link (working as of this writing) to get the special 90% off deal. For the first year 5TB of personal data is $6.95. ​IDrive is a cloud storage provider that has really good reviews, "snowball" type service (IDrive Express), and is pretty darn cheap.

This means unless ransomware could dig SMB credentials out of Acronis, the file shares with my backups are inaccessible to the client or ransomware.Īnd to be clear, I never access the NAS file shares via any Synology elevated admin accounts, as then all shares would be exposed in a read/write manner (in the default configuration).

The Acronis credentials are only stored in Acronis, and those shares are NOT mounted to my clients. The result is I use a "NAS" account on my PC and Mac to access the general purpose file shares read/write, and an "Acronis" account that can read/write to only the backup shares. In each case I used DSM to explicitly deny access to shares that each account should not have permissions to. The other user is for Acronis (backup software), so it can write to a couple of backup shares on my Synology. So what I did was create two users, one for read/write access to only those couple of shares that clients need (general purpose file shares). I also have a couple of backup shares for Acronis that DO need write access, but only for Acronis and not by clients. The last thing I want is for those shares to be writable by my client computers. OneDrive and Dropbox) being sync'd locally to my Synology, as a backup measure. In my case (described more below) I have shares for cloud storage backups (e.g. Ransomware or a virus could be quite cleaver and look for network file shares to encrypt. On another security note, let's briefly talk about user accounts and file share access. I disabled IPv6 for other reasons, so I personally didn't see the slow share access issue pop up. I chose not to configure a VPN here.įinally, if you have slow SMB share access via a Windows client, check out this thread on the Synology forums. So be careful whether you want to use this VPN, or possibly a Docker Container with a VPN that is more robust (which I'll cover later). However, it does not have a 'kill' switch option, which prevents traffic leaks in case the VPN goes down. If you want your NAS to connect to the internet via a VPN, you can also configure that here as well. Configuring this option creates Bond 1 in the network interface GUI. Balance-SLB was acting weird in my environment (some hosts randomly lost connectivity to the NAS), but Active/Backup has been rock solid. Don't bother with trying LACP (IEEE 802.3ad) with the GS116E, as it will NOT work. So for my situation I configured DSM networking for "Active/Backup", and connected both NICs to my switch. It supports LAG, but not dynamic load balancing. I have a single Netgear GS116E, which is a managed but very entry level switch. So if you are a Nutanix customer, the options presented will seem familiar. Underneath the covers it uses OpenVSwitch.

Configuring networking in DSM is straight forward, but you do have a few options. (Save as PKGBUILD in temporary folder and run makepkg -si to install.​All of these settings are in the Control Panel under Network. Optdepends=('nautilus: For nautilus integration' )Ĭonflicts=('cloudstation-beta' 'cloudstation-3.0' 'cloudstation-drive' ) Here's the PKGBUILD I used to get to the as of this writing recent-most release, v3.0.1: # Maintainer: Felipe Martin ĭepends=('glibc' 'libsm' 'binutils' 'fontconfig' ) +md5sums_x86_64=('6381889cd48f13a18ae60e7c2ca46df7')įor anyone who has already upgraded their NAS to 7.0 and is looking get a working Synology drive again, until the package is updated you might want to upgrade ahead of time. Pkgdesc="Drive for PC, the desktop utility of the DSM add-on package, Drive, allows you to sync and share files owned by you or shared by others between a centralized Synology NAS and multiple client computers."Īrch=('i686' -13,11 +13,11 conflicts=()

Here is a patch if it can help: diff -git a/PKGBUILD b/PKGBUILD