remote.it Connection methods
remote.it supports two methods of connection:
- Peer to Peer (P2P)
Each one uses a hostname and port. The relative advantages and disadvantages of each connection method are detailed below.
Peer to Peer Connections
In order to make a peer to peer (P2P) or direct connection the remote.it connectd daemon needs to be running on both systems, but has several advantages over using a proxy connection.
Data does not pass through our servers. Only the connection initialization touches the cloud.
Data throughput is significantly faster.
The connection will stay active as long as there is an internet connection available to both devices.
The URL will remain the same and can be bookmarked.
A P2P connection looks similar to:
127.0.0.1 is a "localhost" address.
34000 is a user-configurable port to use for this connection.
To learn how to make a P2P connection, please see our documentation on:
- Making Connections with the Desktop App
- Making connections using the remoteit command line
- Using connectd in P2P initiator mode in Windows
- Making P2P connections with connectd
Cloud proxy connections are the simplest to set up and test with as you only need our connectd daemon on the target device. However there are limitations compared to a direct P2P connection.
The URL and port will change every time you connect (this only applies to the web portal at https://remote.it and using the /device/connect API endpoint). When using the remoteit Desktop application, proxy connections are also in the form localhost:port.
Proxy connection expiration
Proxy connections, which are made when you connect using the web portal or the /device/connect API endpoint, are not permanent. As long as an active tunnel is maintained, the proxy address will remain active for about 8 hours. How an active tunnel is maintained depends on the type of service you are using.
SSH Establishing and keeping an SSH session open to the endpoint maintains an active tunnel, even if you are not typing. If you disconnect the SSH client, the proxy will expire in another 15 minutes.
SCP Doing file transfers via SCP command line only keeps the tunnel active for the duration of the file transfer. You may do multiple SCP commands using the same proxy URL and port, as long as they are less than 15 minutes apart. The proxy will time out 15 minutes after the end of the last transfer if no further commands are executed inside that window.
VNC and RDP For VNC and RDP, as long as the VNC or RDP client is connected to the server, the tunnel is open, even if you aren’t doing anything.
Web servers If you connect to a web page, simply keeping the web page visible is not sufficient to maintain the tunnel. You’ll have to navigate around or refresh the browser. Web connection proxies expire 15 min after the last web request is issued. The proxy will timeout 15 minutes after the last web request if no further web requests are executed inside that window.
Other service types The behavior of other service types will depend on whether an active client-server maintains a TCP connection. If a TCP connection remains open, the proxy connection will remain active for about 8 hours. If not, the proxy connection will expire about 15 minutes after the last TCP connection closes.
Why? We’ve shortened the expiration time on proxy connections to prevent unused connections being left open and consuming unnecessary resources on our servers that would reduce capacity and needlessly burden the service. This helps to improve overall performance of the remote.it service.
In addition, users whose targets are on metered cell connections were experiencing data charges accumulating even after they stopped using the connection. The shortened timeout will help reduce those data charges.
To learn how to make proxy connections, see our guide on connecting to a remote.it Service in the web portal, or our tutorial on connecting to a Service using the API.