Important

Netgate is offering COVID-19 aid for pfSense software users, learn more.

Connecting to the Console Port¶

There are times when directly accessing the console is required. Perhaps webGUI or SSH access has been locked out, or the password has been lost or forgotten. This guide shows how to regain access directly through the console.

Install the Driver¶

A Prolific PL2303 USB-to-UART Bridge driver is used to provide access to the console, which is exposed via the Micro-USB B port on the appliance.

If needed, install an appropriate Prolific PL2303 USB to UART Bridge driver on the workstation used to connect with the system.

There are drivers available for Windows available for download.

For Windows, choose Windows Driver Installer Setup Program.

Note

The correct driver should install automatically for Windows 7 and above the first time you connect the workstation to the Netgate appliance. It may take up to 3 minutes for the driver to install.

There are drivers available for Mac OSX available for download.

For Mac, choose Mac OS X Universal Binary Driver.

There are drivers available for Linux available for download.

Recent versions of many Linux distributions include this driver and will not require manual installation.

Recent versions of FreeBSD include this driver and will not require manual installation.

Connect a USB Cable¶

Next, locate an appropriate USB cable that has a Micro-USB B connector on one end and a regular USB Type A plug on the other end. These cables are commonly used with smaller USB peripherals such as GPS units, cameras, and so on.

Gently push the Micro-USB B plug end into the console port on the appliance and connect the USB Type A plug into an available USB port on the workstation.

Tip

Be certain to gently push in the Micro-USB B connector on the system side completely. With most cables there will be a tangible “click”, “snap”, or similar indication when the cable is fully engaged.

Locate the Console Port Device¶

The appropriate console port device that the workstation assigned as the serial port must be located before attempting to connect to the console.

Note

Even if the serial port was assigned in the BIOS, the workstation’s OS may remap it to a different COM Port.

To locate the device name on Windows, open Device Manager and expand the section for Ports (COM & LPT). Look for an entry with a title such as Prolific USB-to-Serial Comm Port. If there is a label in the name that contains “COMX” where X is a decimal digit (e.g. COM3), that value is what would be used as the port in the terminal program.

assignment

The device associated with the system console is likely to show up as /dev/cu.usbserial.

The device associated with the system console is likely to show up as /dev/ttyUSB0. Look for messages about the device attaching in the system log files or by running dmesg.

Note

If the device does not appear in /dev/, see the note above in the driver section about manually loading the Linux driver and then try again.

The device associated with the system console is likely to show up as /dev/cuaU0. Look for messages about the device attaching in the system log files or by running dmesg.

Launch a Terminal Program¶

Use a terminal program to connect to the system console port. Some choices of terminal programs:

For Windows it is recommended to run PuTTY or SecureCRT. An example of how to configure Putty is below.

Warning

Do not use Hyperterminal.

For Mac OSX it is recommended to run screen, or cu. An example of how to configure screen is below.

For Linux it is recommended to run screen, PuTTY, minicom, or dterm. An example of how to configure Putty and screen is below.

For FreeBSD it is recommended to run screen or cu. An example of how to configure screen is below.

Client-Specific Examples¶

PuTTY¶

Open PuTTY and select Session under Category on the left hand side. Next, set the Connection type to Serial. Then, set Serial line to the console port that was located above, in Locate the Console Port Device, and the Speed to 115200 bits per second.

Click the Open button and the console screen will be displayed.

An example of using PuTTY in Windows.¶

GNU screen¶

In many cases screen may be invoked simply by using the proper command line, where <console-port> is the console port that was located above.

sudo screen <console-port> 115200

If portions of the text are unreadable but appear to be properly formatted, the most likely culprit is a character encoding mismatch in the terminal. Adding the -U parameter to the screen command line arguments forces it to use UTF-8 for character encoding:

sudo screen -U <console-port> 115200

Terminal Settings¶

The settings to use within the terminal program are:

Speed: 115200 baud, the speed of the BIOS
Data bits: 8
Parity: none
Stop bits: 1
Flow Control: Off or XON/OFF. Hardware flow control (RTS/CTS) must be disabled.

Troubleshooting¶

No Serial Output¶

If there is no output at all, check the following items:

Ensure the cable is correctly attached and fully inserted
Ensure the terminal program is using the correct port
Ensure the terminal program is configured for the correct speed. The default BIOS speed is 115200, and many other modern operating systems use that speed as well. Some older operating systems or custom configurations may use slower speeds such as 9600 or 38400.
Ensure the operating system is configured for the proper console (e.g. ttyS1 in Linux). Consult the various operating install guides on this site for further information.

PuTTY has issues with line drawing¶

PuTTY generally handles most cases OK but can have issues with line drawing characters on certain platforms.

These settings seem to work best (tested on Windows):

Window: Columns x Rows = 80x24
Window > Appearance: Font = Courier New 10pt or Consolas 10pt
Window > Translation: Remote Character Set = Use font encoding or UTF-8
Window > Translation: Handling of line drawing characters = Use font in both ANSI and OEM modes or Use Unicode line drawing code points
Window > Colours: Indicate bolded text by changing = The colour

Garbled Serial Output¶

If the serial output appears to be garbled, binary, or random characters check the following items:

Ensure the terminal program is configured for the correct speed. (See No Serial Output)
Ensure the terminal program is configured for the proper character encoding, such as UTF-8 or Latin-1, depending on the operating system. (See GNU Screen)

Serial Output Stops After the BIOS¶

If serial output is shown for the BIOS but stops afterward, check the following items:

Ensure the terminal program is configured for the correct speed for the installed operating system. (See No Serial Output)
Ensure the installed operating system is configured to activate the serial console.
Ensure the installed operating system is configured for the proper console (e.g. ttyS1 in Linux). Consult the various operating install guides on this site for further information.
If booting from a USB flash drive, ensure that the drive was written correctly and contains a bootable operating system image.