[OpenWrt Wiki] Command-line interpreter (2024)

See also: SSH access for newcomers

A command-line interpreter is a computer program that reads singular lines of text entered by a user and interprets them in the context of a given operating system or programming/scripting language. The interaction takes place by means of a command-line interface. Other common, but technically not quite correct, denominations are console or shell.

The OpenWrt standard unix shell is the Busybox-fork of the Debian implementation of the Almquist shell (see → https://www.in-ulm.de/~mascheck/various/ash/#busybox). In case you want to read about it.

At the end of the boot up process, the init daemon is started, this can be init or systemd or upstart, etc. OpenWrt currently uses procd. Following the boot up scripts located in /etc/rc.d, init will then start all sorts of programs, amongst them the chosen shell. This listens to keyboard strokes and outputs a more or less colorful command-line interface to the connected display.

But most devices you run OpenWrt on, have neither a keyboard nor a display adapter. So we need to access it over the serial port (=local) or over the Ethernet port (= over the network).

To gain access to a shell over the network, you obviously need some other programs to help you with that. And the whole data exchange (aka communication) has to involve some kind of network protocol.

Network protocols of choice are telnet and SSH. Both follow the server ↔ client scheme. On the device running OpenWrt we deploy telnetd for the telnet protocol and dropbear for for the SSH protocol. Try PuTTY for the real look-and-feel, but you should definitely also checkout WinSCP! The latter won't work quite correctly, however Konqueror with fish:// does! See FISH (Files transferred over shell protocol).

(OpenWrt does also include a SSH-client ssh and a telnet-client telnet, in case you want to login from it to somewhere else.)

Note: Before walkthrough_login only telnetd will run, and after only dropbear.

In case of a successful login dropbear will (generate a LOG and) spawn an instance of the specified shell (more shells can be installed simultaneously) with the users ID.

• SSH Access for Newcomers

In OpenWrt this is done in the file: /etc/profile by setting environment variables and aliases. It comes (of course) pre-configured and will work out-of-the-box, but you can alter and augment it's configuration:

• you can configure the command prompt via the variable PS1. see → https://controlc.de/2010/03/12/bash-shell-einrichten/ and many many many other pages in the web on help with that

• you change the content of existent variables and can define new ones

  See Also

  [OpenWrt Wiki] Reasons to use OpenWrt[OpenWrt Wiki] LuCI – Technical ReferenceWhy The Name “Luci” Rocks![OpenWrt Wiki] Frequently Asked Questions: General

• etc.

* For some orientation with the file system and the whole directories, check flash.layout.

At login you will be in your $HOME directory, which is /root for user root and would be /home/user1 for user1, etc. Commands:

There is a ton of commands with a ton of options.On a full blown Linux distribution you would issue a man command to learn about the command and its options.However OpenWrt is minimalistic and thus does not contain this functionality.So either read the man-pages (manual pages) on another GNU/Linux machine or read them online: e.g. at vi.Man pages are in the process of being translated.

Tip In firefox, you can use keywords to simplify the usage. Create a new bookmark, use https://man.cx/?page=%s as address and man as keyword.

To edit a file you need an editor, to edit a text file, you would use a text editor.

The standard text editor included is vi. Until you get used to it, vi is neither intuitive nor pretty.

• vi has two modes: command mode and insert mode.

• to enter command mode press [Esc] (escape key)

• to enter insert mode press either [i] for insert or [a] for append

• vi starts out in command mode

In order to get out of vi, you have to be in command mode. Press [Esc] (the escape key). Then issue one of the following commands:

• :w to write the current file to disc, this will overwrite the old file

• :q to quit without writing

• :wq! to (forcefully) write to disk and then quit vi

• :%s/string1/string2/g replace string1 with string2 in the whole file

Vi can be configured in command mode by setting certain variables:

• :set ai use auto indentation (sometimes annoying default)

• :set noai NO auto indentation

If you do not like vi, try joe, mg, nano, mc --edit, vim, vim-full, vim-help, vim-runtime or zile

• vim

• joe

• nano

• mc

• zile

• mg

and there may be other text editors available in the OpenWrt repos.

'Note:'* Many modern and free graphical text editors, from Visual Studio Code to Atom to Notepad++, (to say nothing of CudaText, TextMate, Komodo Edit, et al.) offer plugins in their official repositories that add the ability to edit files over SFTP, meaning if you're connected to your OpenWrt device from your desktop computer over SSH, those applications with their respective plugins would be able to edit any file on your OpenWrt device as well.* You may need to restart the device after installing vim for it to function properly.

Shell scripts can be executed with:

sh /path/to/script.sh

After changing the executable bit its also possible to run it without the sh in front:

chmod +x /path/to/script.sh/path/to/script.sh

User profile customization example.

# Configure profilemkdir -p /etc/profile.dcat << "EOF" > /etc/profile.d/custom.shexport EDITOR="nano"export PAGER="less"alias bridge="bridge -color=auto"alias diff="diff --color=auto"alias grep="grep --color=auto"alias ip="ip -color=auto"EOF. /etc/profile

• https://wiki.debian.org/CommandLineInterface

• http://linuxcommand.org/tlcl.php ---- William Shotts free PDF books starting from terminal basics