Skip to content

SSH Login ​

This article describes how to log in to the Rhino Pi IQ9N remotely over SSH.

Prerequisites ​

  • The device is powered on and connected to the network; for how to confirm the IP address, see IP Address Confirmation
  • The PC and the device are on the same LAN
  • The SSH service is enabled on the device (enabled by default on the IQ9N)

SSH Service Status ​

The IQ9N has openssh-server preinstalled (version 1:9.6p1 in testing) and the SSH service is enabled by default, so installation is generally not required.

The service uses systemd socket activation, with ssh.socket listening on port 22, so checking ssh.service shows inactive (dead), which is normal. Check the listening status:

bash
sudo systemctl status ssh.socket

Confirm that port 22 is listening:

bash
sudo ss -tlnp | grep :22

If you need to re-enable it:

bash
sudo systemctl enable --now ssh.socket

Logging In to the Device ​

In the PC terminal, run:

bash
ssh aidlux@<device IP address>

For example:

bash
ssh aidlux@192.168.1.100

The default password is aidlux; on the first login you are prompted to confirm the host fingerprint, so enter yes to continue.

Passwordless Login with a Key ​

  1. Generate a key pair on the PC:
bash
ssh-keygen -t rsa -b 4096
  1. Copy the public key to the device:
bash
ssh-copy-id aidlux@<device IP address>
  1. After that, no password is required to log in.

Common Operations ​

OperationCommand
Transfer a filescp <file> aidlux@<IP>:<path>
Run a remote commandssh aidlux@<IP> "command"
Mount a remote directorysshfs aidlux@<IP>:<remote path> <local path>

Note

sshfs is not preinstalled; before mounting a remote directory, install it on the device first: sudo apt install -y sshfs.

FAQ ​

  • Connection refused: confirm that the SSH service on the device is running and that port 22 is not blocked by a firewall.
  • Permission denied: confirm that the username and password are correct, or check whether password login is disabled on the device.
  • systemctl status ssh on the device shows inactive (dead): this is normal; SSH is activated by ssh.socket, so use systemctl status ssh.socket to check the status instead.