• February 24, 2025, 07:03:32 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Secure file transfer over internet best practices  (Read 3993 times)

drick

  • Level 3 Member
  • ***
  • Posts: 270
Secure file transfer over internet best practices
« on: October 04, 2009, 10:34:14 AM »

hi,

i want to set up some type of secure file transfer between 2 DNS343's between my house and my parents house. i will be using DynDNS at both locations and want this to be an automated process. i'm sure someone else has already figured out how to do this, so i was wondering what others are doing, and how it works?

both units will be funplugged, so i can go that route as well.
Logged
DNS-323v1.8 + ffp 0.5
2x750GB Seagate HDD's / RAID1+EXT3
DNS-343A - retired due to faulty fan
DNS-343B - retired due to faulty fan
DNS-343C v1.05b + ffp 0.5
4x2TB Seagate HDD's / RAID5+EXT3
Netgear RNDP6000
6x2TB WD HDD's / RAID6
Netgear WNDR4500

drick

  • Level 3 Member
  • ***
  • Posts: 270
Re: Secure file transfer over internet best practices
« Reply #1 on: November 15, 2009, 12:12:24 PM »

bump

someone else must have done this already?
Logged
DNS-323v1.8 + ffp 0.5
2x750GB Seagate HDD's / RAID1+EXT3
DNS-343A - retired due to faulty fan
DNS-343B - retired due to faulty fan
DNS-343C v1.05b + ffp 0.5
4x2TB Seagate HDD's / RAID5+EXT3
Netgear RNDP6000
6x2TB WD HDD's / RAID6
Netgear WNDR4500

affinity

  • Guest
Re: Secure file transfer over internet best practices
« Reply #2 on: November 28, 2009, 07:41:56 PM »

I have two units that have funplug installed and I use an "at" job to backup another server to each of the DNS units.

The script uses rsync; I can see no reason why this couldn't easily be achieved based on my working setup.

I also, at this stage, manually backup remote servers for clients with screen sessions and using rsync; the remote sites are standard server machines that have ssh running.  I use key authentication and to get keys working automagically, I use ssh-agent and ssh-add tools on the DNS units.

Edit: Oh and to lessen the CPU load on the DNS units, I use the "arcfour" cipher.

Here is a sample rsync command:
/ffp/bin/rsync -avxH -e "ssh -l -o -c arcfour" root@other_server:/source-backup-location/ dest-backup-location

An odd thing about using "date" on the DNS box is that it presents the GMT date/time, not the local date/time, but the at scheduling uses actual localized timing.
« Last Edit: November 28, 2009, 07:48:01 PM by affinity »
Logged