Sam Przyswa wrote:
> 
> Rob Owens a écrit :
>> You could use either a VPN or ssh port forwarding.  For ssh port forwarding, 
>> it would go something like this:
>>
>> ssh -L 2222:remotemachine:22 username@servername
>>
>> Then you can do:
>>
>> ssh -p 2222 someuser@localhost
>>
>> "servername" is a machine behing the firewall that can receive ssh requests 
>> from the internet.  "remotemachine" is a machine on the same network as 
>> "servername", which you want to ssh into (for the purpose of running a 
>> backup).  The port forwarding makes your local port 2222 pretend to be port 
>> 22 on "remotemachine". 
>>
>> This works for one remote host.  You would need to repeat the process for 
>> each remote host.  You could specify a different port (2223, perhaps), or 
>> you could re-use port 2222 as long as you end the previous session before 
>> starting a new one.
>>   
> 
> Ok but with 200 machines, manage 200 port forwards it's not very useful, 
> and what about Windows machines and SMB shares ?

A VPN might be more convenient and OpenVPN is easy to set up.  If you 
can arrange routing through the tunnel you can just use the remote IP 
addresses as usual.  Normally the only tricky part is arranging the 
route back from the clients if the host running the VPN tunnel isn't 
already their default gateway.  If you do other remote administration 
besides backups a tunnel between LANs is even more worthwhile.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
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/