Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/KevinCruz-cell/Redes-de-comunicaciones-/llms.txt

Use this file to discover all available pages before exploring further.

The administration page centralizes SSH access control for your router. You can adjust Dropbear’s listening configuration, change the root password, and manage the list of trusted public keys — all without a direct shell session. Navigate to /sistema/administracion to access these settings.

​
SSH configuration

These settings control how Dropbear accepts incoming SSH connections.
SettingDefaultDescription
Port22TCP port Dropbear listens on. Valid range: 1–65535.
Password authenticationonAllow users to authenticate with a password.
Root loginonAllow the root user to log in via SSH. Sets both RootPasswordAuth and RootLogin for compatibility across OpenWrt versions.
Gateway portsoffAllow remote hosts to connect to forwarded ports.
Interface(none)Restrict Dropbear to a specific network interface. Leave blank to listen on all interfaces.
After saving, the application commits and restarts the SSH daemon: 
uci commit dropbear
/etc/init.d/dropbear restart
Changing the port takes effect immediately after save. If you change the port, update any firewall rules and your SSH client configuration before the next connection attempt.

​
Change root password

1

Enter a new password

Type a new password in the New password field. The password must be at least 4 characters long.
2

Save

Click Change password. The application runs passwd root on the router using piped input:
printf '%s\n%s\n' 'newpassword' 'newpassword' | passwd root
The ROUTER_PASSWORD value in your application’s .env file is used to authenticate SSH commands from the web interface. If you change the router’s root password here, you must also update ROUTER_PASSWORD in .env to match — otherwise all subsequent router commands will fail.

​
SSH authorized keys

Authorized keys allow passwordless authentication using a public/private key pair. Keys are stored at /etc/dropbear/authorized_keys on the router.

​
Uploading a key

1

Generate a key pair (if you don't have one)

On your local machine, run:
ssh-keygen -t ed25519 -C "my-router-key"
This creates a private key (~/.ssh/id_ed25519) and a public key (~/.ssh/id_ed25519.pub).
2

Upload the public key file

Click Upload public key and select your .pub file. The application validates that the file begins with a recognized key type prefix before uploading.Supported key types:
  • ssh-rsa
  • ssh-ed25519
  • ecdsa-sha2-nistp256
  • ecdsa-sha2-nistp384
  • ecdsa-sha2-nistp521
3

Confirm the key appears in the list

After upload, the key list refreshes showing the key type, comment/label, and a truncated preview of the key body.
The upload command appends the key only if it is not already present, then sets correct permissions: 
mkdir -p /etc/dropbear
touch /etc/dropbear/authorized_keys
grep -qxF 'KEY' /etc/dropbear/authorized_keys || printf '%s\n' 'KEY' >> /etc/dropbear/authorized_keys
chmod 600 /etc/dropbear/authorized_keys
/etc/init.d/dropbear restart

​
Viewing existing keys

The key list displays each authorized key with:
  • Type — the algorithm family (RSA, ED25519, ECDSA)
  • Label — the comment field from the key file
  • Preview — first and last 28 characters of the base64 key body

​
Deleting a key

Click Delete next to any key to remove it. The application rewrites authorized_keys excluding the selected entry, then restarts Dropbear.

Build docs developers (and LLMs) love

Get started for freeTalk to us