Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Unable to access pfsense via serial cable

    Scheduled Pinned Locked Moved General pfSense Questions
    37 Posts 10 Posters 4.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      smrehan00
      last edited by

      Hi Everyone,

      I am trying to access pfsense via console cable which I just bought. I have a mini pc from Pondesk with 4x Intel NICs, HDMI and a console port (USB to RJ-45). Currently it has the VGA based version installed. I am trying to access it via the console cable. I have installed the drivers for it in Windows 10 x64 Pro. I have adjusted the settings as per pfsense from device manager:

      Speed: 115200
      Data Bits: 8
      Parity Bits: None
      Stop Bits: 1

      I have enabled SSH and console connectivity from the advanced section in pfsense gui but when I try to access it via console through putty while setting it on the mentioned speed and selecting serial while setting the COM to COM5 as detected by Windows 10. Then I select start and nothing happens. I press the space bar and enter key multiple times but to no avail. Pfsense version is 2.4.4 p3.

      Any idea what I am doing wrong? The cable is brand new.
      I am also attaching the screenshot of the cable.
      51oFSg-YkoL.AC_SL1000.jpg

      I appreciate the help.

      JKnottJ GertjanG 2 Replies Last reply Reply Quote 0
      • JKnottJ
        JKnott @smrehan00
        last edited by

        @smrehan00

        Is that cable compatible with whatever hardware you're using? For example, Cisco cables are different from Adtran. What does the RJ45 end connect to? Find out what the pin out is on that cable and short the Tx & Rx lines. You should then be able to use a terminal emulator app, such as Putty and see the characters echoed back.

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan @smrehan00
          last edited by

          @smrehan00 said in Unable to access pfsense via serial cable:

          a console port (USB to RJ-45)

          So it another NIC ?
          Shouldn't this be something like USB to RJ-45 to RS232 ?
          Like : internally (in the pfSense) device there is some UART, and its interface is ported to an (micro) USB on the outside of the box.
          To be used with an USB cable that exposes itself to your PC as a COM port (over USB) - the micro USB on the other side connects to your RS-232 port, which physicality is micro USB port.

          To make it short : what is this RJ-45 plug on your cable ?

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          JKnottJ 1 Reply Last reply Reply Quote 0
          • JKnottJ
            JKnott @Gertjan
            last edited by

            @Gertjan

            That cable is likely a Cisco console cable. However, without knowing what he's plugging into, it's impossible to say if it's the right cable. There are differences in console cables. I've seen at least 3 different configurations in my work. Hopefully, he's not trying to plug it into an Ethernet port.

            PfSense running on Qotom mini PC
            i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
            UniFi AC-Lite access point

            I haven't lost my mind. It's around here...somewhere...

            S 1 Reply Last reply Reply Quote 0
            • S
              smrehan00 @JKnott
              last edited by

              @JKnott
              @Gertjan

              Hi Guys! Thank you for responding back. Well, I am not an idiot :) and I know where to put the console cable in the console port.

              mnho-073 console.JPG

              The USB end goes into the USB port on my laptop and the rj-45 end goes into the console port.
              Can you tell me how to short the Tx and Rx lines?
              Can you share the color code for the wires required for it to work? In case the color code is not correct in my cable. I'll post the actual cable color code tomorrow as the cable is in the office and I am at home.

              Unfortunately, manufactures don't offer Rs-232 port anymore so I am stuck with the RJ-45 based console port.
              Here is the link to the serial cable which I got:

              https://www.daraz.pk/products/usb-to-rj45-for-cisco-usb-console-cable-ftdi-744664241835-i126626956-s1285112387.html?spm=a2a0e.searchlist.list.1.109060eaanGv2O&search=1

              JKnottJ jahonixJ 2 Replies Last reply Reply Quote 0
              • JKnottJ
                JKnott @smrehan00
                last edited by

                @smrehan00

                Here's the Cisco pin out, which likely matches your adapter. There is no standard colour code I'm aware of as different manufacturers do what they want. However, it's pins 3 & 6 that have to be connected. The easiest way to do that is with an Ethernet jack. However, those will generally need a punch tool, though some come with their own tool. You might also find some with screw terminals. If you're handy with soldering, you could make your own, with a circuit board mount connector, with which you'd then solder a jumper between 3 & 6.

                PfSense running on Qotom mini PC
                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                UniFi AC-Lite access point

                I haven't lost my mind. It's around here...somewhere...

                1 Reply Last reply Reply Quote 0
                • jahonixJ
                  jahonix @smrehan00
                  last edited by

                  @smrehan00 said in Unable to access pfsense via serial cable:

                  don't offer Rs-232 port anymore so I am stuck with the RJ-45 based console port.

                  What?
                  That IS a serial RS-232 port just not on a DB-9 but an RJ-45 connector. Problem is that the pin-out of the RJ-45 is not standardised. Katron/KTI networks uses the same serial on RJ45 but with reversed RX/TX lines as compared to Cisco. That's an adaptor-mess unless you built your own cable.

                  Ask the board manufacturer for the RJ-45 pin-out, maybe that's even printed in the manual.

                  JKnottJ 1 Reply Last reply Reply Quote 0
                  • JKnottJ
                    JKnott @jahonix
                    last edited by

                    @jahonix said in Unable to access pfsense via serial cable:

                    DB-9

                    Actually, that should be DE-9. DB-9 is used by those who don't know any better. The "D" refers to connector type, the 2nd letter the shell size and the number refers to the number of pins. So, the old 25 pin serial connectors are DB-25 and the 9 pin, DE-9.

                    D-subminiature

                    BTW, at one point in my career, I used to order connectors by the hundreds. I wouldn't get very far ordering the wrong item.

                    PfSense running on Qotom mini PC
                    i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                    UniFi AC-Lite access point

                    I haven't lost my mind. It's around here...somewhere...

                    jahonixJ 1 Reply Last reply Reply Quote 1
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      @JKnott said in Unable to access pfsense via serial cable:

                      What does the RJ45 end connect to?

                      We could also argue that it is not an RJ45, but an 8P8C connector/jack.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      S JKnottJ 2 Replies Last reply Reply Quote 0
                      • S
                        smrehan00 @Derelict
                        last edited by

                        @Derelict
                        @JKnott
                        @Gertjan
                        @jahonix

                        Guys do any of you have a working console cable? If yes then can you post a picture of it ? Moreover, can you post an up close zoomed in on the pin layout of the Rj-45 connector? So, I can take notes and create a new connector?

                        JKnottJ 1 Reply Last reply Reply Quote 0
                        • DerelictD
                          Derelict LAYER 8 Netgate
                          last edited by

                          It depends on how the port in your device is configured. You will need the documentation for that before anyone can help you.

                          Chattanooga, Tennessee, USA
                          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

                          1 Reply Last reply Reply Quote 0
                          • provelsP
                            provels
                            last edited by provels

                            Beyond cable incompatibility, I'd probably try 9600 and 19200 baud as well. Then again, I might just SSH over IP and call it a day.

                            Peder

                            MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                            BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                            1 Reply Last reply Reply Quote 0
                            • JKnottJ
                              JKnott @smrehan00
                              last edited by

                              @smrehan00

                              I have a few for Cisco, but they are DE-9 on one end, not USB. Regardless, a picture won't tell you anything. I have used cables for Cisco, Adtran and Ciena and they weren't compatible. You need to find out the connections required for your device and compare it with the Cisco pin out I provided.

                              PfSense running on Qotom mini PC
                              i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                              UniFi AC-Lite access point

                              I haven't lost my mind. It's around here...somewhere...

                              1 Reply Last reply Reply Quote 0
                              • JKnottJ
                                JKnott @Derelict
                                last edited by

                                @Derelict said in Unable to access pfsense via serial cable:

                                We could also argue that it is not an RJ45, but an 8P8C connector/jack

                                RJ45 is valid, as it refers to a registered jack type. 8P8C is the connector used with it. On the other hand, DB-9 doesn't exist, at least not in the commonly used connectors.

                                PfSense running on Qotom mini PC
                                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                                UniFi AC-Lite access point

                                I haven't lost my mind. It's around here...somewhere...

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  smrehan00 @JKnott
                                  last edited by

                                  @JKnott

                                  This is the cable pin out that I have on the cable I bought.

                                  20200103_160058.jpg

                                  JKnottJ 1 Reply Last reply Reply Quote 0
                                  • jahonixJ
                                    jahonix
                                    last edited by

                                    These colors are not standardised so from viewing at it we know nothing.
                                    You must provide the pins of the RJ-45 jack from your device.

                                    1 Reply Last reply Reply Quote 0
                                    • jahonixJ
                                      jahonix @JKnott
                                      last edited by

                                      @JKnott said in Unable to access pfsense via serial cable:

                                      Actually, that should be ...

                                      And what does it help with the actual problem if it's DB or DE? We are not a micron closer to a solution.

                                      1 Reply Last reply Reply Quote 0
                                      • GertjanG
                                        Gertjan
                                        last edited by Gertjan

                                        This https://www.amazon.com/Console-Essential-Accesory-Ubiquity-Switches/dp/B01AFNBC3K/ref=sr_1_1?keywords=Moyina&qid=1578056697&sr=8-1 is the cable ( I guess - it's the same image).
                                        Pin layout is present.

                                        Couldn't find any details about the RS-232 (RJ-45 like) plug :

                                        884388c1-a01a-4e7c-8d1c-ad5fde3c8977-image.png

                                        @smrehan00 : your turn.

                                        No "help me" PM's please. Use the forum, the community will thank you.
                                        Edit : and where are the logs ??

                                        1 Reply Last reply Reply Quote 0
                                        • JKnottJ
                                          JKnott @smrehan00
                                          last edited by

                                          @smrehan00 said in Unable to access pfsense via serial cable:

                                          This is the cable pin out that I have on the cable I bought.

                                          As has been said several times, there is no standard connection. I mentioned 3 brands of equipment, which all use different configurations. For us to help you, you have to provide the connections as required by your device. We simply don't know. Is there not any documentation for that computer that tells you what's required?

                                          PfSense running on Qotom mini PC
                                          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                                          UniFi AC-Lite access point

                                          I haven't lost my mind. It's around here...somewhere...

                                          S Sergei_ShablovskyS 2 Replies Last reply Reply Quote 0
                                          • S
                                            smrehan00 @JKnott
                                            last edited by

                                            @JKnott There is nothing in the manual which shows about the pin status of console port. I will check in the system bios to see if the console port is activated via BIOS.

                                            JKnottJ 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.