Support FAQ

Command line configuration

Managers with LINUX/UNIX experience may be more comfortable configuring and operating the console server from the command line. Only Administrator class users have command line access.

To log in you connect using a terminal emulator directly (or via a modem) to the local console serial port or by SSH/Telnet through the LAN. The Administrator can then configure the console server and attached serial console and host devices using LINUX/Busybox/Opengear commands:

If you are connecting using the serial line, plug a serial cable between the console server Local/Modem port and terminal device. Configure the serial connection of the “terminal” device/program you are using to 115200bps, 8 data bits, no parity, one stop bit and software (Xon-Xoff) flow control. If you are using a program running on a Windows PC as the terminal device, then the connecting cable to the DB9 Local/Modem connector is made up from a Cat5 UTP (#449016) cable and two DB-9 to RJ-45 adapters (#319000 and #319001)
To enable dial-in access to the console port, first activate and configure ppp. Authenticated remote dial-in access can also be configured using the web Console Manager by selecting the Network: Dial In menu option
If you are connecting over the LAN then you will need to interconnect the Ethernet ports and direct your terminal emulator program to the IP address of the console server (192.168.0.1 by default)

Command line access

Log on to the console server by pressing ‘return’ a couple of times. The console server will request a user name and password. Enter the user name root and the password default and you'll see the hash (#) command line prompt.

Opengear console servers all run an embedded Linux operating system and listed below are some of the standard Linux and Busybox commands and applications that are in the default Opengear build tree. It is possible to configure the console server just using these commands.

Opengear has also developed a number of custom command line utilities to make changes easier, and to ensure the changes are permanent (i.e. stored in the console server's flash memory):

The config tool allows manipulation and querying of the system configuration from the command line. Using config the new configuration can be activated by running the relevant configurator, which performs the action necessary to make the configuration changes live.
Similarly the portmanager application provides a buffered interface to each serial port.
It is supported by the pmchat (similar to the chat) and pmshell (similar to the tip or cu) commands, which ensure all serial port access is directed via the portmanager.

Default commands

adduser *, agetty, bash, busybox, cat *, chat, chgrp *, chmod *, chown *, config, cp *, date *, dd *, deluser *, df *, dhcpcd, discard, dmesg *, echo *, erase, eraseall, false *, flashw, flatfsd, ftp, gen-keys, getopt *, gettyd, grep *, gunzip *, gzip *, hd, hostname *, httpd, hwclock, inetd, inetd-echo, init, ip, iptables, iptables-restore, iptables-save, kill *, ln *, login, loopback, loopback16, loopback48, loopback8, ls *, mail, mkdir *, mkfs.jffs2 mknod *, more *, mount *, msmtp, mv *, nc, netflash, netstat, ntpd, pgrep, ping, pkill, pmchat, pmdeny, pminetd, pmloggerd, pmshell, pmusers, portmanager, portmap, pppd, ps *, pwd *, rm *, rmdir *, routed, routef, routel, rtacct, rtmon, scp, sed *, setmac, setserial, sh, showmac, sleep *, smbmnt, smbmount, smbumount, snmpd, ssh, ssh-keygen, sshd, sslwrap, stty, stunnel, sync *, sysctl, tar *, tc, tcpdump, telnetd, tftp, tip, top, touch *, traceroute, true *, umount *, uname *, usleep *, vi *, w, zcat *

Commands which are appended with * above all come from BusyBox

Use the ls command to view the standard commands available in the /bin directory in your console server. For more information on the command line interface refer the User Manual which can be found on the CDROM or online.