Netgear RN00RPL1 Replicate for Desktop Software Guide

Page of 36
  Appendix A.  Network Virtualization and Architecture
 
   
|
     
33
ReadyNAS Replicate Software Manual 
Architecture
ReadyNAS Replication software application allows you to create an on-demand virtual 
private connection between two or more ReadyNAS units. Unlike traditional VPN application, 
this connection is established without the need for any complicated setup; all you need to do 
is add your ReadyNAS to your virtual network and register the unit with the centralized 
management portal. Once the connection is formed, your devices act as if they are on the 
same LAN.
ReadyNAS Replication runs on business-class ReadyNAS units, and forms a direct 
connection between any two devices. This connection is facilitated by our ReadyNAS 
Remote servers. With few exceptions, once the connection is established, the ReadyNAS 
Remote servers are not used, and forms a direct connection between your units. With a 
direct or relayed connection your data is safe and fully encrypted using NETGEAR’s 
end-to-end security model; only the endpoints can decode the data. In very few cases, when 
a direct connection cannot be formed, our relay servers are used to create the connection
1
In order to form a connection between your ReadyNAS units, both devices need to be 
registered with our ReadyNAS Remote servers. Your ReadyNAS automatically registers itself 
once the Replication add on has been enabled. Your device uses its unique MAC address as 
its user name, but there is no reason to remember this user name since it is always readily 
available in your Replication network. 
Once your ReadyNAS devices are registered, they log into and form an SSL connection with 
the ReadyNAS Remote servers. The ReadyNAS Remote servers are then used to form a 
control channel. The control channel is used to route end-to-end control messages between 
ReadyNAS units. 
For example, one ReadyNAS might request a connection to another ReadyNAS. In this case, 
a control message flows from the caller, through the ReadyNAS Remote Servers, to the 
callee. The receiving ReadyNAS can choose to accept or decline the incoming connection 
request, and send a response back to the caller over the same control channel. If the 
connection is allowed by the ReadyNAS, the connection setup begins.
During the connection setup phase, our patented NAT traversal technique is used to setup a 
direct peer-to-peer connection between ReadyNAS units so no port-forwarding or dynamic 
DNS is required. The connection setup phase requires temporary use of ReadyNAS Remote 
servers, and exchanges AES keys, which are only shared between endpoints so the data the 
flows between the devices is protected by end-to-end encryption. Once the peer-to-peer 
connection is formed, the data travels directly between your ReadyNAS devices. 
responses back to the caller, and uses NAT traversal technique so no port-forwarding or 
dynamic DNS is required.
1. A relay server is used in less than 5% of connections.