The connectd daemon is used on your target device to enable remote.it Services. The same connectd daemon is used on the initiator device, at the other side of a P2P connection, although in a different mode, in order to connect to those Services. This guide describes the use of connectd on the initiator device.
The commands below show you how to use the macOS console to download and run the connectd daemon on a computer running macOS. Although this example is for the macOS version of the daemon, we have many other versions of daemon available.
# Download the most recent release (this is for OSX)curl -LkO https://github.com/remoteit/misc_bins_and_scripts/raw/master/connectd/connectd.x86_64-osx# Make it executablechmod u+x connectd.x86_64-osx# Move to a folder on your PATHmv connectd.x86_64-osx /usr/local/bin/# Add a connectd symlink to point at the daemonln -s /usr/local/bin/connectd.x86_64-osx /usr/local/bin/connectd
Please follow the instructions at the link below to install the connectd daemon on any Linux system. This also takes care of creating a connectd symlink.
To confirm that you have the correct connectd daemon for your device and its OS, and that your network is configured correctly to allow a remote.it connection, run connectd -n at the command line in order to run remote.it Network Diagnostics. You may have to configure any virus checker that you are using in order to allow connectd to be run. The output from connectd -n should be similar to the following:
My-Air-2:~ macuser$ connectd -nConnectd built Apr 19 2019 at 16:46:38 Now Starting UpVersion 4.6 - (c)2019 remot3.it, Inc. All Rights ReservedBuilt with BCASTER MALLOC_POOL RESOLVE BIGBUF BACKTRACE pool=524288MAC OSX Versionalloc poolRunning Network Diagnostics---------------------------------Checking if DNS works ... .[OK]Checking TCP connectivity to remote.it...<oip=192.168.1.40> [OK]Checking UDP connectivity to remote.it...Send to 188.8.131.52:5959  [mip=184.108.40.206] [oport=59612 mport=59612] [preserve port]Send to 220.127.116.11:5960  [mip=18.104.22.168] [oport=59612 mport=59612] [no remap] [preserve port]Send to 22.214.171.124:5961  [mip=126.96.36.199] [oport=59612 mport=59612] [no remap] [preserve port different IP] [OK]This router preserves ports, this is optimal.This router doesn't remap new connections to new ports.Static Pool FreeEndian : LittleSHA1 test:passed.RC4 test:passedXXTEA test:passed.Looks compatible.Mac-Air-2:~ macuser$
Next, we describe three ways you might use the connectd daemon as a P2P initiator:
Using explicit command line parameters in foreground mode
Using explicit command line parameters in background mode
Using a provisioning file in background mode.
If you are using the P2P connection for an application that does not require the use of the command line (e.g. a web browser), then you may run connectd in the foreground (also called interactive mode). When you are done, you can simply type CTRL-C to terminate the connectd daemon. Foreground mode is demonstrated in option 1 below.
Foreground mode is useful for debugging if you have any problems initiating a P2P connection as it will show you connection status.
The examples supplied for options 2 and 3 use "&" at the end of the connectd command line to force the connectd daemon to run in the background. This allows you to continue to use the same command prompt for an SSH connection, for example.
If you are developing your own apps including P2P mode, you'll need to keep track of the process ID (PID) so that you can kill the connectd daemon when you are done using the P2P connection. Examples 2 and 3 show two different ways this can be done.
connectd -c \BASE_64_USER \BASE_64_PASSWORD \DEVICE_UID \BIND_PORT \ENCRYPTION_MODE \LOCAL_HOST_ADDRESS \MAXOUTSTANDING
Run connectd in P2P initiator mode
Your Base64 encoded username (probably your e-mail)
Your Base64 encoded remote.it password
The ID (also called address) of the device you want to connect to
The port you want to bind the connection to on your local machine (eg 33000)
The level of encryption to use. Choices are:
The address to bind to on your local network. This is normally 127.0.0.1.
Maximum number of packets outstanding on a connection. Set to 12.
connectd -s -c \eW91cm5hbWVAZXhhbXBsZS5jb20= \ # Base64 encoded username/emailc3VwM3JzZWtyZXQh \ # Base64 encoded password80:00:00:00:00:00:00:F1 \ # Device UID on remote.itT33000 \ # Port to bind to, prefixed with "T"1 \ # Encryption mode = RC4127.0.0.1 \ # Localhost address
Run in P2P initiator mode
Display connection status information
Parameters are the same as used in the previous example.
The above command all on one line is:
connectd -s -c eW91cm5hbWVAZXhhbXBsZS5jb20= c3VwM3JzZWtyZXQh 80:00:00:00:00:00:00:F1 T33000 1 127.0.0.1
Once the connection is established, (approximately ten seconds) you will see:
...Starting Proxy on port 33000 on index 1.Proxy started.
Now you can use your P2P connection using 127.0.0.1 on port 33000. For example, you can type 127.0.0.1:33000 in a browser window for a web application, or start an ssh connection to 127.0.0.1 port 33000 in a new console window.
You can hit CTRL-C at any time to terminate the P2P connection.
p2p.sh automates some of the tasks needed to make a repeatable P2P connection to a single service. Download the p2p.sh script to a convenient location on your system.
Edit the following values in p2p.sh as needed, then save the file.
uid - the UID of the Service you are connecting to
address - usually 127.0.0.1
port - any number between 33000 and 65535
Download p2p.sh to your computer, then run:
chmod +x p2p.sh./p2p.sh "username" "password"
where username and password are the credentials for your remote.it account.
This script runs connectd in the background so that you can continue to use the command prompt, and after about 10 seconds, shows you the command you can use to kill the connection when you are done. The value shown in the "kill" command is the process ID (PID) of the connectd daemon which was just launched.
Your connection is now active on 127.0.0.1 port 33100.To terminate this connection, type in:kill 21152$
connectd allows the use of a provisioning, or configuration, file to allow better organization of multiple P2P connections. Here is a sample provisioning file for a P2P initiator.
# setting autoconnect to 1 will autoconnect the p2p initiator to the target# setting autoconnect to 2 will attempt to automatically reconnect in the event# of a network interruptionautoconnect 1#user ID to use for the initiator connection (required)user_id email@example.com#auth_pass users password to use to make the Initiator P2P connection (not recommended, use auth_hash)auth_pass weaved1234#local port to bind TCP proxy socket to, mandatoryproxy_local_port 33300#proxy local IP to bind to, can be 127.0.0.1, 0.0.0.0 or any local adapter IPproxy_bind_address 127.0.0.1#remote_address is the (UID) address of the target to connect to.\remote_address 80:00:00:00:01:00:0A:C2#Maximum buffer depth for each TCP connection (10-25) good range raise for high latency enviormentsmax_depth 12# keep this comment line here
Copy and save this to a file that corresponds to your target Service. For example, if the UID is for an SSH Service running on your Pi, you could call this file SSH-Pi.txt.
Edit the following entries to match your account and target device.
user_id - your remote.it account user name
auth_pass - your remote.it account password
remote_address - your target Service's UID
proxy_local_port - desired localhost port
connectd -f SSH-Pi.txt &
The script will output connection information, then after about 10 seconds, you should see:
Starting Proxy on port 33000 on index 1.Proxy started.
To get the process ID (PID) so that you can kill the connection when you are done, type:
immediately following the connectd command.
Now you can connect to your target remote.it Service using 127.0.0.1 and the port value you chose. The P2P connection will stay open until you terminate the process using "kill", or the internet connection drops.
Supposing that the value was 21456, then when you are done with the P2P connection, type
You can set the autoconnect parameter value to 2 in the initiator provisioning file to have the daemon automatically attempt to reconnect to the target in the event of a network interruption.
Please see our guide on troubleshooting connections: