USB to Console with FTDI Chip, VILICONTY USB Console Cable Replaces RS232 (DB9/DB25) for Laptop and PC in Windows, Vista, MAC, Linux

IF YOU'RE NOT SURE HOW TO ACCESS A CONSOLE WITH THIS CABLE on macOS or Linux, READ THIS REVIEW - I've included a guide on how to access consoles using this cable on macOS, and the instructions are mostly applicable to Linux too.While there's a somewhat lack of instructions on how to actually access a console using the cable on Mac/Linux/Windows - the cable is usable on macOS as soon as you plug it in.No third party drivers are required, and similarly, you can access consoles without any additional software, just by using "screen /dev/tty.usbserial-XXXXXX".-----------WARNING: For those who don't know what a console cable actually is - it is NOT an Ethernet (LAN/internet) cable. A console cable is used to connect to a "console port" commonly found on business/datacenter grade network hardware.As the name infers, they're a single purpose port/cable which is used to directly access the command line management console of networking equipment, without using any actual networking, so they work even when the network configuration of the device is broken.While console cables/ports use the same "RJ45" connector as Ethernet, they are NOT Ethernet at all - they're effectively RS232/UART Serial Ports/Cables, but using the much smaller, more compact, and more modern RJ45 port/connector.--------Today I used one of these console cables with my iMac Pro running macOS Mojave (10.14.6), to access the console on my new Mikrotik CRS354-48G-4S+2Q+RM switch (photo #2 attached to this review, is the MikroTik console, accessed using screen + iTerm 2 + this cable).There were no clear instructions on how to actually access the console using the cable - though a few reviewers mentioned that you can use "screen" with it.Having worked with Serial-over-LAN on servers before, I figured it might be under /dev/ttyX, and after poking around I managed to find "/dev/tty.usbserial-A9A7K3X7", which I was able to use with "screen" to access my Mikrotik's console.Despite the lack of instructions - given that the cable works out of the box, and otherwise functions perfectly, I'm giving it 5 stars.###### How to use the Console Cable on MacOS (most things applicable to Linux too)###### Step 1. Plug it in + turn on devicesConnect the USB end of the cable to a USB 2.0/3.0 port on your computer, or on a hub attached to your computer.Connect the RJ45 (transparent ethernet/phone line-like) connector to the "CONSOLE" port of the device you're trying to administer - e.g. a Cisco/Juniper/MikroTik switch/router.Turn on both your computer, and the device you're trying to administer.# Step 2. Open up a terminalOpen up a terminal, such as iTerm 2, or the default macOS "Terminal.app".If you're not sure how - on macOS you can press CMD + SPACE, then type "terminal", and select "Terminal.app" (has an icon of a black screen with the white text >_ in the top left)# Step 3. Locate the console cable's device pathType the command "ls /dev/tty.*" (notice the dot before the asterisk), which will show all available external / third-party console devices: user@macbook ~ $ ls /dev/tty.* /dev/tty.ARPT /dev/tty.Bluetooth-Incoming-Port /dev/tty.usbserial-A9A7K3X7My cable personally shows as "/dev/tty.usbserial-A9A7K3X7" (and "/dev/cu.usbserial-A9A7K3X7"), but be aware that each individual cable may have a different device number at the end.# Step 4. Connect to the consoleIf you're connecting to a device which uses the slow but common 9600 baud (bits per second) console speed, then you can just type "screen /dev/tty.usbserial-xxxxx" screen /dev/tty.usbserial-A9A7K3X7However, if you're connecting to a device which uses a different baud speed (common speeds inc: 3600, 9600, 19200, 28800, 38400, 56000, 57600, 115200), you'll need to specify the baud rate number after the device, for example, my Mikrotik CRS354-48G-4S+2Q+RM switch has a console port which runs at 115,200 baud - so to connect to it, I had to run: screen /dev/tty.usbserial-A9A7K3X7 115200Please be aware that a console port acts just like an RS232 serial port - it's not like SSH, you generally won't see anything on the screen until you press some keys. In most cases, you should just hit ENTER (RETURN), which should show the prompt / login screen.If you're concerned that the device console may be asking you something, and hitting ENTER/RETURN may cause something to happen unintentionally - then you could try using your arrow keys, normal letter/number keys on your keyboard, or even push CTRL-C to ensure any previously typed command at the console would be cleared.# Step 5. Some tips for working with "screen"To detach from a Screen session (i.e. put it in the background), press CTRL-A (like when pressing ctrl-c), then press D to detach.To list all screen sessions running under your user, use "screen -ls" user@macbook ~ $ screen -ls There is a screen on: 13414.ttys012.Example-Macbook (Attached) 1 Socket in /tmp/uscreens/S-example.To reattach to a screen session, use "screen -r SCREEN_ID" user@macbook ~ $ screen -r 13414If you want to disconnect from a console, and you can't do it naturally with commands on the console e.g. "exit" or CTRL-C - then you can use "screen -ls" to get the process ID of the screen session, followed by "kill PROCESS_ID" to terminate the screen session: user@macbook ~ $ kill 13414

Great USB to RJ45 console cable

Using this to build my pfsense box and also setup a couple of Cisco switches. They are faultless so far (the first one was so good I bought another so I could set up more than one device at a time).

Ever had a Network Switch go down? If you work in IT, chances are at some point you're going to and these cables have a nasty habit of vanishing when you most need them. My advice is to pick one up now and just keep it in your rucksack along with a few other IT bits and bobs that'll come in helpful (USB sticks and the link)I grabbed one of these and have needed to use it at least twice this year. It's saved me from some tight spots! It's really just a basic USB to Console cable, plug and play, not much to it. It is of a decent quality though. I don't think it'll break any time soon!

Works like a charm, very easy to use and install. Downloads drivers from The Internet, so make sure you plug the cable in before you go on site to do a console connection to a router or firewall that you still have to configure for Internet. Such a nice cable that my colleagues keep stealing it and forcing me to buy more.

I bought this to avoid having to use multiple adapters to have console access to networking equipment through my Macbook Pro. It works superbly straight out the packet, didnt need to install any drivers, and was immediately recognised by my terminal application. A must buy for any network engineers using USB-C laptops.

Both myself and a colleague bought this product within a week of each other and it worked well, but we both found the USBc plug is susceptible to bending as the connector is quite chunky (quite a lever) and if you put it down a bit clumsy whilst still connect to laptop (mac pro in my case) it just bends the connector and then stops working. Both now use USB2/3 version and a USBc adapter. I reckon cable lasted less than a few weeks of use every day. Saying that if you only use it infrequently and need a light weight cable in your kit bag it pretty good option.

I got this to reset & update a few Cisco switches to the latest software. I originally got a similar priced cable from ebay, but it's a well known problem with a certain cheap chipset, that they struggle to work and just sit there flashing in terminal. This one worked perfectly,

Funktioniert ohne Driver Installation. Einstecken und los legen. Am PC habe ich den Adapter nicht getestet.

Adapter wird sowohl unter Windows als auch MacOS erkannt, nur leider funktioniert nichts. Gleiche software mit einem alten USB Adapter funktioniert tadellos. (Und natürlich habe ich den richtigen COM Port eingestellt).