# Linux to Linux ### Step 1 to Step 4 These initial steps set up the machine initiating the connection.
On the machine you are connecting from {% hint style="warning" %} In this installation guide, `@example01_np` will represent the client atSign, while `@example02_np` will represent the device atSign. {% endhint %} ### Step 1: Download and run the Installer {% hint style="warning" %} Do not run the following commands while logged in as the root user. Instead, use `sudo` from a regular account when elevated privileges are required, and create a regular account if one does not already exist. {% endhint %} Open a terminal and download the installer from GitHub by running the following command: ```bash curl -L https://github.com/atsign-foundation/noports/releases/latest/download/universal.sh -o universal.sh ``` To check if the installation downloaded correctly: ```bash stat universal.sh ``` Make the script executable and run the script by running the command below: ```bash chmod u+x universal.sh ./universal.sh ``` {% hint style="info" %} You may be asked to enter your password if your machine requires sudo privileges. {% endhint %} **The install type** * Enter `client` when prompted. **Your atSigns (Skip this step)** * To skip this step, simply press the Enter/Return key twice. Your atSigns will be activated in the upcoming steps. ### Step 2: Activate your client atSign (@example01\_np) {% hint style="warning" %} If you've already activated your **client** atSign on another device, this step will not work. Instead, follow this guide: [Reuse your client atSign on another machine](/installation-faq/reuse-your-client-atsign-on-another-machine.md) {% endhint %} This command activates your atSign and prompts you to enter an OTP. This is only done during the setup of a brand new atSign. {% hint style="warning" %} Replace `@_np` with your **client atSign.** {% endhint %} ``` ~/.local/bin/at_activate -a @_np ``` #### Enter the one-time password (OTP) & Check your SPAM/PROMOTIONS folders at\_activate will pause and wait for the input of a one-time pin (OTP) sent to your email or phone number.\ \ Once activated, the master keys will save at `~/.atsign/keys`. ### Step 3: Activate your device atSign (@example02\_np) Run the same command, but for your device atSign. {% hint style="warning" %} Replace `@_np` with your **device atSign.** {% endhint %} ``` ~/.local/bin/at_activate -a @_np ``` #### Enter the one-time password (OTP) & Check your SPAM/PROMOTIONS folders at\_activate will pause and wait for the input of a one-time pin (OTP) sent to your email or phone number.\ \ Once activated, the master keys will save at `~/.atsign/keys`. ### Step 4: Generate an atSign authorization passcode for your device atSign Run the following command to generate a 6-character one-time passcode. You will use this passcode in **Step 6.** {% hint style="warning" %} Replace `@_np` with your device **atSign.** {% endhint %} ```bash ~/.local/bin/at_activate otp -a @_np ```
### Step 5 and Step 6 After setting up the machine you're connecting from, you'll configure the machine you're connecting to.
On the machine you are connecting to ### Step 5: Download and run the Installer {% hint style="warning" %} Do not run the following commands while logged in as the root user. Instead, use `sudo` from a regular account when elevated privileges are required, and create a regular account if one does not already exist. {% endhint %} Open a terminal and download the installer from GitHub by running the following command: ```bash curl -L https://github.com/atsign-foundation/noports/releases/latest/download/universal.sh -o universal.sh ``` To check if the installation downloaded correctly: ```bash stat universal.sh ``` Make the script executable and run the script by running the command below: ```bash chmod u+x universal.sh ./universal.sh ``` During installation, you’ll be prompted to enter the following items: {% hint style="info" %} You may be asked to enter your password if your machine requires sudo privileges. {% endhint %} **The install type** * Enter `device` when prompted. **Your atSigns** * Client atSign: e.g., `@example01_np` * Device atSign: e.g., `@example02_np` **Your device name** * This should be the name of the machine you're currently installing on. ### Step 6: Initiate atSign authorization request Run the following command to make an authorization request. {% hint style="warning" %} Be sure to replace the following values: `@_np` with your **device atSign**, `` with the **passcode generated in Step 4**, `@_np_key` with your **device atSign**, `` with the name of the machine you are on {% endhint %} 
~/.local/bin/at_activate enroll -a @<REPLACE>_np \
  -s <PASSCODE> \
  -p noports \
  -k ~/.atsign/keys/@<REPLACE>_np_key.atKeys \
  -d <DEVICE_NAME> \
  -n "sshnp:rw,sshrvd:rw"
Once you see this text, you're ready to continue to the next step. ``` Submitting enrollment request Enrollment ID: --------------------- Waiting for approval; will check every 10 seconds ```
### Step 7 and Step 8 With both machines now configured, the final steps bring us back to the machine initiating the connection.
On the machine you are connecting from ### Step 7: Approve the atSign authorization request Run the following command: {% hint style="warning" %} Be sure to replace the following values: `@_np` with your **device atSign**, `@` with the **device name** **from Step 6.** {% endhint %} ```bash ~/.local/bin/at_activate approve -a @_np --arx noports --drx ``` ### Step 8: Use NoPorts! That's it. You can start using NoPorts or explore some of the documented use cases, including [MCP](/use-cases/mcp.md), [SSH](/use-cases/ssh.md), [RDP](/use-cases/rdp.md), [SFTP](/use-cases/sftp.md), [Web Server](/use-cases/web-server.md), and [SMB](/use-cases/smb.md).
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.noports.com/installation/connecting-from-linux/linux-to-linux.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.