Protocols: SSH, Telnet, Rlogin & Raw
Every device gets a protocol. SSH for anything modern, Telnet for legacy gear, Rlogin for trusted hosts and Raw TCP for console servers and serial-to-network adapters. Whichever you pick, commands run through the same prompt-smart engine.
- In the device editor, pick the protocol: SSH (22), Telnet (23), Rlogin (513) or Raw TCP (23 by default) — the default port fills in automatically and stays editable.
- Rlogin and Raw TCP need no credentials: Rlogin connects through the trusted-host model and Raw connects the moment the port opens.
- For Rlogin a username is still required — it is sent so the host can authorize you.
- The protocol badge on each device row and session card tells you which one is in use.
- Everything else — preparing the device, turning off output paging, raising privileges, answering confirmations — works the same on all four protocols.
Tip
Console servers and serial adapters usually speak Raw TCP — connect to their port and you get the device console directly.
Note
SSH stays the first choice: it is encrypted. Use Telnet, Rlogin or Raw only where the equipment forces you to.