A terminal startup guide · September 2026

Interlinked
Pi

How to get in, find your way around, and see what this little server can do. Keep this page open beside your Terminal.

Current stateThe Pi is online with SSH and a basic set of tools. The ~/servers folder is ready; a game or voice server has not been installed yet.
01

Connect to the Pi

  1. Join the same home network as the Pi.
  2. Open Terminal on a Mac, or Windows Terminal / PowerShell on Windows.
  3. Type this command and press Return:
Your computer → interlinked-pi
ssh USER@interlinked-pi.local

On the first connection, confirm the host prompt if this is your Pi. Replace USER with the login name provided privately, then enter that account's password when asked. The cursor will not move while you type the password; that is normal. Keep the password private and out of this public page.

If the .local name does not resolve, use the reserved local IP instead:

IP fallback · home network only
ssh USER@192.168.0.136

When you see a prompt like USER@interlinked-pi:~ $, you are typing on the Pi. Type exit to disconnect.

02

What's already there

SystemRaspberry Pi OS Lite64-bit Debian Trixie; command line interface.
AccessSSH is enabledThe login name is shared privately. Firewall allows OpenSSH.
ClockLos Angeles timeNetwork time and the real-time clock were checked.
Workspaces~/servers · ~/backups · ~/scriptsFolders prepared for future projects.

Useful tools installed: git, curl, wget, htop, tmux, nano, zip, unzip, rsync, jq, tree, network utilities, ufw, and fail2ban. The firewall is active and currently permits SSH. Installing a game server later may require an additional firewall rule for its port.

Starting point

No game server, TeamSpeak server, or other app service was confirmed running during setup. This page records the prepared base system.

03

Terminal basics

The prompt tells you where a command will run. ~ means your home folder, /home/USER. Commands are case-sensitive. Press Tab to complete a filename; the up arrow recalls the last command. Press Ctrl+C to stop a running command.

A short walk around
pwd
ls -la
cd ~/servers
ls -la
cd ~

pwd shows where you are; ls -la lists files; cd changes folders. Use sudo only when a command specifically needs administrator permission.

04

Useful commands

hostname -IShow the Pi's current network addresses.
df -hSee free space on each mounted drive.
free -hSee available memory.
htopWatch CPU, memory, and processes. Press q to leave.
tree -L 2 ~/serversSee the first two folder levels under servers.
timedatectlCheck time zone and clock synchronization.
systemctl status ssh --no-pagerCheck whether SSH is running.
sudo ufw statusShow active firewall rules.
sudo apt updateRefresh package lists; this does not install updates.
sudo shutdown -h nowShut down cleanly. The SSH session will end.

For help, try command --help or man command. Press q to leave a manual page.

05

Keep a session open

tmux lets an interactive terminal session keep running after your SSH window closes. It is useful while setting up software or watching logs.

A named session
tmux new -s project
tmux attach -t project
tmux ls

Start with the first command. To leave it running, press Ctrl+B, then D. Use the second command later to reattach. A tmux session is not a replacement for a service that starts automatically after reboot.

06

Where to go next

Start with ~/servers. Once you choose a particular game or voice server, record its install steps, start command, service name, ports, and backup location here. Check its requirements against the Pi's ARM64 system before installing.

A good first exercise: connect, run pwd, ls -la, df -h, and htop, then type exit. That confirms you can get in, look around, and leave cleanly.

Prepared from the interlinked-pi setup notes · Updated September 23, 2026