Starting with Resilio Connect v 2.8.0 Administrators can see the detailed information about network connections established by and Agent in a job run.
This information is available in a Job Run -> Agents-> <agent_name> -> Connectivity. It's available for Agents of version 2.8.0 and newer and is not available for offline Agents.
NOTEThis is on-demand information. It means that it show the current connectivity status for the moment when you open the tab. Information may change if you close it and open again.
The view is divided into two blocks: one shows the discovery mechanisms, the other is connectivity matrix (map).
Agents have a number of ways to discover each other in a job. The view shows the number of agents discovered through this or that channel.
By tracker. By default Management Console gets a tracker server installed on same computer. For remote Agents tracker is available by same IP or DNS name as MC, port 3000. Read more about tracker server here. Resolved address of tracker for the given Agent is seen on the right.
LAN. Agents also make use of multicasting and broadcasting in LAN by sending packets and listening to 18.104.22.168:3838 . It's possible to enable or disable LAN discovery in Agent Profile.
Predefined hosts. These are 'Known hosts' in Agent profile, i.e. the address that Agent is instructed to connect to directly.
Incoming connection. This channel means that this Agent was discovered by others through any of the above channels. It's totally OK to see that the Agent was discovered that many times, since in a peer-to-peer mesh all Agents are trying to find remote peers and thus are found by others at the same time.
Once Agents discovered each other, they will attempt to install a network tunnel to all of the discovered IP addresses trying all protocols. After that best tunnel (*) will be selected and shown in the table. Seeing 'No info' here means that the Agent is not connected to any other Agent at all.
Agents. Column shows the remote Agents with which connection has been established at least once in this job run. If you don't see some Agent here, it means that the current Agent never connected to it at all.
Status. Connected means there is an active connection to the agent at the moment. Not connected means that the Agent used to be connect but is not anymore - connection is lost. This may be a signal of a network problem or simply mean that remote Agent is offline.
Total connections. The number of network tunnels established with the Agent in total.
Best connection (*). The best tunnel selected from all the established tunnels. IP:port in this column is the address of remote peer where the tunnel is opened.
Protocol. Network protocol on which best tunnel is established.
Agent ID. Is the Agent ID as seen in Agents Tab.
Info. Clicking on "More Info" open details about all other attempted and/or failed network tunnels with a given Agent. Best tunnel is marked there as "Best" and "established"
(*) BEST TUNNEL
When establishing connection with each other, Agents will try all discovered local and public IP addresses with each of the protocols - TCP, uTP and uTP2 and ZGT (uTP3). Best tunnel is the protocol/address pair that Agents select to actually transfer files between each other. There's certain priority for a protocol selection:
TCP - for LAN addresses
uTP - for WAN addresses
ZGT (uTP3) - if "WAN Optimization" and 'WAN Optimization in LAN" are enabled for both Agents.
uTP2 - if "WAN Optimization" and 'WAN Optimization in LAN" are enabled for both Agents and ZGT failed to connect for some reason.