VPN Details and dialog explained.

Uptime 

This is the length of time that this VPN has been up

Roundtrip 

This is the round trip time (RTT) for an IP packet from your device to your friend’s and back

RTT can tell you a lot about your connection to your friend. 834ms like you see in this dialog is really a long time. For example, if I ping google.com I see RTTs in the 30ms range.

With an 834ms RTT for packets you can expect that communications to this peer will feel laggy. This is not anything related to Gabriel, but is more a function of either this peer’s network or my own.

Peer 

This is the secure domain name (SDN) of the peer you’re communicating with

Device 

This is the name of your peer’s device (a name that he/she chose)

Presence 

This will show “Active” unless the peer goes offline or the only device they have online is a server device (cloud) in which case it will be “Online”.

Active VPN 

This will be true as long as the VPN is still alive

TCP Only 

Our VPNs tunnel through both TCP and UDP packets. Users can disable UDP tunneling which would be indicated here as “true” for TCP only

Connection 

This shows your VPN’s IP address -> your friend’s VPN IP address. For example, if I were to ping 172.18.58.66 I would be pinging the Galaxy S tablet of this peer.

VPN statistics

Below the blue bar you will see 2 columns (TCP, UDP)

Direct 

This tells you if you are able to directly connect/tunnel a route directly to the peer. In most cases this should be true. Depending on the peer’s network configuration behind routers it may be impossible for us to discover a NAT route. In this case (as you see here) you will be communicating with the peer over a relay server.

Note that our relay servers never have access to view your data. It is always encrypted end-to-end and only your peer has the key to decrypt the information. All the relay server sees is the destination and forwards the data. No data is ever kept on the relay server.

Address 

This is the public IP address of the endpoint for your peer (in a direct connection), or the IP address of the relay server (if a relay is required). For example, if you did an nslookup on 192.241.213.206 you’d see that is one of our west coast relay servers (w2.virnetx.net). If this peer and I had a direct connection the
IP address here would likely be the IP address from his/her Internet Service Provider (ISP).

Sent 

The number of bytes sent from me to this peer over TCP and UDP

Received 

The number of bytes received by me from this peer over TCP and UDP

Even though both TPC and UDP will show data sent and received, a direct UDP connection is preferred. You will notice a majority of data will be transmitted using this protocol, when available.

Powered by BetterDocs

Theme: Overlay by Kaira