Unable to access pfsense via serial cable

Gertjan

?? You actually bought a device with very needed peripherals that are not documented (and probably not standard) .... it's time to contact their support.
Was the device sold with an optional console cable ? Your next best choice : get this cable.

JKnott

@smrehan00

Well, then you'll just have to start checking to see where what is. The Cisco connection is a good starting point. Years ago, we used to use something called a "breakout box", which made it easy to test individual pins or make appropriate connections, etc.. If you have a volt meter, you can probe the pins to see which ones have voltage on them. The transmit data will be a few volts and the receive line may have a fraction of a volt on it. You can also do a continuity test, to see which wires are ground. This is something that I have done, on many occasions, to test unknown connections. You can make your own "breakout box" with a couple of RJ45 to screw terminal blocks.

Does the manufacturer of that computer have any support available? I have been browsing the Pondesk site and don't see your computer.

JKnott

@JKnott

I just noticed the Pondesk site has live chat available. You can go there and ask about that console cable.

Sergei_Shablovsky

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

@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?

Let's to put my 5 cents in discussion:

At the first You need really well engendered USB-to-serial DB9 converter: Prolific PL2303 (or it’s advanced version PL2303ta).

“Well engendered” mean “compatible with most hardware serial interfaces which hardware manufacturer used”, no matter Cisco, Juniper, or some crappy no name router.

Only after that a You need to make next step forward.

JKnott

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

At the first You need really well engendered USB-to-serial DB9 converter:

That box requires an RJ45 connector, not DE-9. If he had a DE-9, he'd then need a DE-9 to RJ45 cable. What he absolutely must do is find out the correct connection for that box. He can do that by contacting the manufacturer, as I mentioned.

We can't be expected to guess what that box requires, when there's so much variation in those cables.

Sergei_Shablovsky

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

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

At the first You need really well engendered USB-to-serial DB9 converter:

That box requires an RJ45 connector, not DE-9. If he had a DE-9, he'd then need a DE-9 to RJ45 cable. What he absolutely must do is find out the correct connection for that box. He can do that by contacting the manufacturer, as I mentioned.

We can't be expected to guess what that box requires, when there's so much variation in those cables.

Of course, You need additional DB-9 to RJ-45 extender cable.

And mostly because only a few USB-to-Serial converters have a cable more than 0.8-1m long. Admins confirm to You that common length 1.5-2.5 m would be comfort in any situation.

JKnott

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

Of course, You need additional DB-9 to RJ-45 extender cable.

Why does he need a DE-9 (yes, that is DE-9, not DB-9) anywhere? He has a USB port on a a computer and that box needs an RJ45, with some serial connection. Hopefully, it will be Cisco compatible, as that is what his cable appears to be.

I have an adapter with a DE-9 and I then have to use another cable to connect to Cisco gear. I needed a different cable for Adtran and yet another for Ciena. That's what makes this so much "fun".

However, until the OP contacts the manufacturer to find out what's needed, we are only guessing. As he mentioned, there might also be some configuration needed to even make the console work.

jimp

Not to mention it may (or may not) need a null modem adapter in the mix depending on the pinout of that port, and depending on the cable connected to that port. Far too many variables that only the OEM (or testing every combination) can verify.

JKnott

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

need a null modem adapter in the mix depending on the pinout of that port

Not likely. That's one way things are pretty much standard. The only exception would be on routers, where there's both console and aux ports. The console port connects to a computer and the aux to a modem, for dial in access.

Incidentally, there's something called a Yost cable, which can be used to connect anything to anything. Cisco is similar to it.

Sergei_Shablovsky

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

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

need a null modem adapter in the mix depending on the pinout of that port

Not likely. That's one way things are pretty much standard. The only exception would be on routers, where there's both console and aux ports. The console port connects to a computer and the aux to a modem, for dial in access.

Incidentally, there's something called a Yost cable, which can be used to connect anything to anything. Cisco is similar to it.

Anyway, better to start with something that are standard and working without any problems on most appliances (I mean Prolific :)

Derelict

Making a serial cable requires the serial pin-outs for that specific port.

To make a serial connection there you probably only need TXD, RXD, and signal ground - three pins.

There are 120 combinations of 3 out of the 8 pins in any order so have fun guessing. With a multi-meter or oscilloscope you might be able to eliminate some of those.

Documented pinouts is far easier.

If a "cisco" console cable didn't work, the manufacturer needs to provide the pinouts and cable diagrams.

If they don't have the required documentation, I would return it.

Bottom line, this is not a problem for the pfSense firewall software to solve.

jahonix

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

Not likely. That's one way things are pretty much standard. The only exception ...

I used a KTI industrial switch in the past where TX/RX were reversed as compared to Cisco's pinout. Not funny.

Just checked, they still do this on current products. From manual:
Console Port: RS-232, DTE type
1,2,7,8 NC
3 RxD IN
6 TxD OUT
4,5 GND

smrehan00

@jahonix
Thanks guys. I will report back once I achieve connectivity.

JKnott

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

I used a KTI industrial switch in the past where TX/RX were reversed as compared to Cisco's pinout. Not funny.

I guess I should have clarified a bit more. With serial ports, there is the DCE or modem and DTE or terminal. Those console ports tend to be DCE, with routers having both DCE and DTE ports. The console cable connects to the DCE and a modem connects to the DTE.

Regardless, those RJ45 serial ports have no real standard, though those Yost cables are an attempt.

Sergei_Shablovsky

Hi, folks!

Please look on whole situation:
Operating System -> Device Driver -> USB-2-COM Adapter -> COM port in a target device.

On each point possible be fault or wrong working order.
So, the solution are simply moving forward from one poling to next to determine what exactly not working well.

I just suggest to start from “is my usb-2-com really working” and not wasting time on something other. Another reason are -> many cheaper China-made usb-2-com adapters just piece of crap and not working properly.

Heathy65

@smrehan00
Hi, did you ever resolve the serial connection issue? I have a MNHO-073 and like you tried a Cisco cable to no avail. Did you ever work out the pinout for the serial RJ45 port?

stephenw10

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

MNHO-073

That device has an hdmi output, does that work as a console?

It may have been installed without a serial console enabled, who installed it? What image was used?

Steve