Resilio Connect is designed to automatically overcome any changes in the network and reconnect using all available connectivity routes. However, non-default configuration may lead to connection disruption between the Agents which will negatively affect files synchronization flow.
Below are the best practices for the most popular use cases when Resilio Agent is installed on a device that travels with a person and thus changes the network that it's connected to. This may affect connection of the device to the Management Console and other Agents.
Scenario without Resilio Proxy
Here's the network topology
The scenario implies that the Management Console, Tracker server and an Agent that have access to all files managed by Resilio Connect are running inside protected network and do have port forwarding configured.
To ensure Roaming laptop works well in both locations A and B you need to define DNS name that resolves differently inside the protected network and outside. It should resolve to your network public IP (one used for port forwarding) outside of the LAN and it should resolve to the Management Console's and Tracker host's internal IP inside the LAN. Use this DNS name in sync.conf file or when connecting your Roaming laptop Agent using Console IP address.
Once it's done, the Roaming Agent will be able to connect to the MC and Tracker both in the internal network and over the WAN. Since Tracker server is available, it will take care to provide proper central Agent IP address for roaming laptop automatically without additional configuration.
Scenario with Resilio Proxy involved
Here's the network topology
The scenario implies that no incoming connections are possible to the Office LAN, while outgoing connections to selected ports are allowed. Proxy server and tracker server are installed on some hosting provider with public address available.
To ensure Roaming laptop works well in both locations A and B follow the steps below:
- Configure Resilio Proxy server on the Management Console
- place its public IP address / DNS name as primary address;
- if the Proxy is a part of DMZ, place its internal_IP_address:3328 as a secondary address the proxy is available at. - When configuring Roaming Agent by entering IP and port in the Agent UI, use Proxy IP:3328 as Management Console's address.
- When configuring Roaming Agent via sync.conf file: add internal Management Console's address and port 8444 in management_server -> host section, as well as add parameter "mc_proxy": "public_ip:3328" on a top level of configuration JSON.
- If the Roaming Latop's user may use VPN and you do not want data traffic to go over VPN - also block port 3839 on your VPN tunnel firewall.