#Synology drive sharesync schedule update#
UPDATE I see that it has been moved per this thread.
#Synology drive sharesync schedule how to#
The one thing I can't figure out is how to put it on a schedule as I do not want it in real time (preferred after hours). At this point I ran only sudo chmod 0666 /dev/net/tun and restarted Tailscale, with expected outbound connections working again. I started playing with Synology Drive ShareSync (part of Synology Drive Server package) and I was able to get it to work. So it appears the tun device permissions are being reset to root. I re-ran the rest of the commands (placed into a shell script):Īt this point (now operating correctly) the following is the status as expected:ĭrwxr-xr-x 2 root root 60 Jan 19 11:10 netĬrw-rw-rw- 1 root root 10, 200 Jan 19 11:10 tunĭrwxr-xr-x 2 root root 60 Jan 19 11:23 netĬrw- 1 root root 10, 200 Jan 19 11:23 tun Re-setting the cap with setcap and restarting Tailscale alone still did not allow outbound. You can do what you want with 'Shared Folder Sync' rather than 'Drive ShareSync'. Set a schedule to automatically take one snapshot within 24 hours Manually take an unlimited number of snapshots within 24 hours Logs and global file locking features are supported on Hybrid Share 1.4. So that part is persistent, however, outbound connections were now no longer functioning. var/packages/Tailscale/target/bin/tailscaled = cap_net_admin+eip On the Cloud Sync user interface, click on the Create icon at the upper-left corner to start the wizard.
$ sudo getcap /var/packages/Tailscale/target/bin/tailscaled The actual problem is that the tun device permissions are getting reset on reboot on DSM7.īackground: I use Tailscale for a Synology-Synology sync where one is behind a T-Mobile CGN rendering most other VPN solutions non-starters. Apologies for mis-identifying the initial problem. Synology Drive ShareSync permite sincronizar archivos entre dos NAS con configuración del modo de sincronización flexible. I did some more testing and it doesn't appear to be the cap.
0 kommentar(er)
