USB serial console adapters for homelab switches and firewalls

The switch is powered on, your laptop is connected, and the management page has vanished. This is when a console cable earns its space in the drawer. Choose it by the electrical interface first: Cisco-style RJ45 console, DB9 RS-232, a board’s 3.3V UART header, or a USB console built into the equipment. The plug is only the beginning.

Cable specifications come from the makers; connection steps follow Cisco, Protectli, OPNsense and the terminal-tool documentation, checked October 26, 2026.

Quick picks: match both ends of the cable

• USB-A laptop to RJ45 console: StarTech ICUSBROLLOVR. A direct Cisco-style rollover cable with a Prolific PL2303GC chip in the current maker specification.
• USB-C laptop to RJ45 console: Cable Matters 201065-6. An FTDI-based cable that removes the extra USB adapter from a modern laptop’s toolkit. The equipment end is still RJ45.
• DB9 toolkit: StarTech ICUSB2321F. An FTDI USB-to-RS-232 adapter for equipment with a DB9 connection or its own documented DB9-to-console cable.
• Board debug: FTDI TTL-232R-3V3. A cable for documented 3.3V UART headers, with separate power and signal pins. Its red power lead supplies 5V; leave that lead disconnected when the board has its own power.

These are alternative routes. Buy the one your equipment needs, rather than collecting four almost-right cables.

Compare the adapters

Adapter, host plug and chipset	Equipment connection and best fit
StarTech ICUSBROLLOVR: USB-A; Prolific PL2303GC; 1.8m cable.	RJ45, RS-232, Cisco-style rollover. Choose it for a compatible switch or router console when your computer has USB-A. No separate DB9 adapter needed.
Cable Matters 201065-6: USB-C; FTDI FT232RQ; 6ft cable.	RJ45, RS-232, Cisco-style rollover. Choose it for a USB-C computer and a documented Cisco-standard console pinout. It contains an RS-232 level shifter.
StarTech ICUSB2321F: USB-A; FTDI FT232RL; 1.8m cable.	DB9, RS-232. Choose it when the equipment’s serial cable already handles the final connector and wiring. COM retention keeps the assigned Windows COM-port number across reconnections.
FTDI TTL-232R-3V3: USB-A; FTDI FT232RQ; six-pin header cable.	3.3V UART signals, separate 5V VCC output. Choose it for board-level serial debugging using the board’s header diagram. This is the TTL route, not an RS-232 adapter.

The StarTech rollover specification, StarTech DB9 specification, Cable Matters product page and shared Cable Matters manual identify the parts and chipsets. The FTDI-authored cable datasheet hosted by Adafruit supplies the TTL cable’s electrical and pinout details.

RJ45 console: same shape, completely different job

A Cisco-style RJ45 console is a serial RS-232 interface, not an Ethernet connection. The Cable Matters adapter includes the USB-to-serial electronics and RS-232 level conversion. Its rollover wiring reverses the connector’s pin order; it isn’t an Ethernet crossover cable.

Plug it into the port labelled Console or COM, using the equipment’s pinout. An RJ45 LAN port, an AUX port and a console port can look frustratingly similar. A USB Ethernet adapter won’t replace this cable, and the console cable won’t give your laptop a network connection.

This also means a managed switch doesn’t automatically need a console cable. Some compact switches use a web interface without an external serial console. Buy for the actual port on your chosen managed switch.

DB9: let the equipment’s cable finish the job

The ICUSB2321F gives your computer an RS-232 DB9 port. What follows it depends on the equipment: a straight-through cable, a null-modem cable, or a documented DB9-to-RJ45 console cable can each be correct for different hardware. A connector adapter alone doesn’t choose the wiring for you.

For example, Protectli’s COM-port guide says its FW Vault models include a DB9-to-RJ45 cable. A USB-to-DB9 adapter lets you keep using that supplied cable. OPNsense’s serial-access guide also calls out null-modem requirements for applicable hardware.

That is the useful reason to own a DB9 adapter: flexibility with the right equipment cable. For one Cisco-style RJ45 console, the direct USB-A or USB-C pick is simpler.

TTL headers: 3.3V signals do not mean 3.3V power

A board UART header is a different electrical interface from an external RS-232 port. Use the TTL-232R-3V3 only where the board documents a compatible 3.3V UART.

The FTDI diagram labels black as ground, orange as the cable’s TX output and yellow as its RX input. Connect cable TX to board RX, cable RX to board TX, and ground to ground, following the board’s header layout. A six-pin socket doesn’t make the board’s pin order universal.

The red VCC lead is 5V even on this 3.3V-signal cable. Keep it disconnected on an independently powered board. Leave unused handshake pins disconnected unless the board’s instructions require them. Never substitute an RS-232 console adapter for the TTL cable.

A USB-C or micro-USB console may need only a data cable

Some equipment puts the USB-to-serial interface inside the box. You connect a normal data-capable USB cable to its labelled USB console port instead of adding a USB-to-RJ45 adapter.

Protectli documents USB-C COM cables for its V1XXX series and different arrangements for other Vault families. Cisco documents a USB Micro Type B console on its Catalyst Micro Switches. Follow that exact model’s driver instructions; an integrated USB console can use a different chip from your external adapter.

The USB-C end on the Cable Matters recommendation goes into your computer. It does not turn an equipment USB-C console into an RJ45 port. Also distinguish a USB console from a USB host socket intended for storage.

Install the driver, then find the port

Windows: open Device Manager → Ports (COM & LPT) and note the COM number that appears when you connect the cable. Use the adapter maker’s download for your Windows version and processor architecture if the port needs a driver. The Prolific cable and FTDI cables use different driver families; the brand on the outer jacket doesn’t decide that.

macOS: compare ls /dev/tty.usb* before and after connection. Use the new device name in your terminal program. Follow the maker’s macOS driver instructions if no serial device appears; a name in the USB hardware list alone doesn’t identify the usable serial node.

Linux: reconnect the adapter and inspect the latest kernel messages with dmesg. Look for a USB serial device assigned to something like /dev/ttyUSB0; built-in USB consoles can use other names. The kernel USB-serial documentation describes node assignment and Prolific/FTDI support. If access is denied, use your distribution’s serial-device permissions rather than making the device writable by everyone.

The assigned node or COM number belongs to your computer. It is unrelated to a switch’s Ethernet address.

First connection: get a prompt before changing anything

For a typical Cisco-style console, start with 9600 baud, 8 data bits, no parity, 1 stop bit, and no hardware or software flow control: 9600 8N1. Cisco’s terminal-settings guide gives those settings. OPNsense uses 115200 8N1 in its serial-access instructions. Use the equipment’s documented speed when it differs.

On Windows, this PuTTY command sets the complete line configuration; replace COM3 with your assigned port:

putty.exe -serial COM3 -sercfg 9600,8,n,1,N

Lower-case n means no parity; upper-case N means no flow control.

On Linux, these are quick launch commands for the identified device:

screen /dev/ttyUSB0 9600
minicom -D /dev/ttyUSB0 -b 9600

The Screen manual and minicom manual cover their options. These launch lines select the device and speed. For an explicit 8N1/no-flow setup, use PuTTY’s configuration above or minicom: Ctrl+A, then O → Serial port setup; set Bps/Par/Bits to 9600 8N1 and both Hardware Flow Control and Software Flow Control to No.

For OPNsense, replace 9600 with 115200. If it was installed without serial access, enable Serial console as a primary or secondary console under System → Settings → Administration, as its guide explains.

Open only one serial program on the port, press Enter and look for a readable prompt. Read the version or help output first. Save configuration changes only after you understand which device you’re controlling, and keep a configuration backup before experimenting. Keep a short note with the cable naming its target equipment, pinout source and normal line settings.

When the screen stays stubbornly blank

Symptom	Next useful check
No COM port or device node appears	USB data cable, host port, correct chip driver and OS support. Baud rate won’t fix USB detection.
Readable output, but typing does nothing	Flow control, correct serial node and equipment cable pinout.
Random symbols instead of words	Baud rate first, then data bits/parity/stop bits.
Port opens, but no prompt	Press Enter, then check whether that model enables serial output and which console port takes priority.
Ethernet link won’t negotiate correctly	Diagnose the network cable separately with our Ethernet cable tester guide. A serial console cable isn’t that tool.

For a switch drawer, start with the direct RJ45 cable that matches your laptop. Add DB9 when your equipment needs its supplied serial cable, and keep a clearly labelled TTL cable for boards. The right electrical interface makes this a recovery tool rather than a guessing game.

If the machine has HDMI output, a portable crash-cart monitor and wired keyboard give you the local video console alongside your serial toolkit.