2015-03-20 0:39 GMT+01:00 Adam Goryachev <mailinglists AT websitemanagers.com 
DOT au>:

> That is certainly one method. I would prefer one of the following options:
> 1) Configure SSH server on one of the machines (server), then use ssh
> tunneling+ rsync to connect to each client (only single exposed port,
> all traffic is encrypted, downside is overhead on the one machine
> picked. Some potential benefits from ssh compression.

They are mainly Windows clients, not server and nor Linux. Is it
possible to have ssh server working good also for Windows ? Further,
Backuppc can use this kind of configuration or will I have to manage
rsync ?

> 2) Use a VPN, then just talk directly to the clients like they were on
> the LAN

I think this is a bit difficult. They are my customers' pc so it is
not always possible.

> If you do expose rsyncd directly to the Internet, then I would suggest
> that you restrict the source IP addresses if possible.

Is it enough "host allow" per share in rsync.conf file ?

Thank you
Antonio


-- 
Antonio Sanguigni alias slapshot
----------------------------------------------------------------------
Servizi informatici Windows e GNU/Linux- http://www.pieroni.biz
GioveLUG (Linux User Group) - http://www.giovelug.org

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/