RJ45 Console access

smcgowan

Oh, and your documentation is vague at best. It'd be great if you offered full pinout information for both ends of the cable, maybe even suggested cables to purchase (possibly even through Netgate, since some of your devices COME with the appropriate cable), etc..

chrismacmahon

Like this: https://store.netgate.com/Serial-NULL-Modem-RS232-Cable-Kit-P2165.aspx

smcgowan

Ah, but then I get to go buy a DB9 to RJ45 conversion as well. Just suffice to say there's a little more that could be done with your documentation. Like, for instance, pointing out that you DO have that cable for sale ;-)

Anyway, I sense a flamewar starting over something trivial. I'm running on three hour's sleep and not a happy camper, but I'm going to step away now.

JKnott

@smcgowan said in RJ45 Console access:

I purchased an RJ45 <-> USB cable from Amazon after a short discussion on the Netgate/pfSense forum. I connected the device (COM port settings show in image 1), fired up putty (serial connection settings shown in image 2), started the terminal, powered on the FW-7551, and waited to see something on the terminal screen... I got nothing... a black screen, even after the device powered off by itself and then powered back on (by itself again), just a blank terminal...

Many, many years ago, I used to use something called a "breakout box", which was inserted between serial ports. With it, I could ensure the signals were on the correct pins etc. My first question is are you sure that USB adapter has the correct pin out? You may have to do some testing to determine that.

smcgowan

@JKnott, that was what I was worried about, and why it'd be nice if I knew what the correct pinout was for a USB to RJ45 rollover console cable was. Google has turned up many different offerings, and Netgate does not have (that I could find) documentation on the actual cable type I'm trying to use. Just the DB9 port diagram. Also, IIRC from my earlier dive into that manual that was linked earlier on the mfgr's site, the pinout doesn't match, but that might just be my sleep deprivation...speaking of which...

I'm going to catch 2 hour's sleep before I have to get back to working

JKnott

@smcgowan said in RJ45 Console access:

@JKnott, that was what I was worried about, and why it'd be nice if I knew what the correct pinout was for a USB to RJ45 rollover console cable was.

Here's what someone posted as the pin out for Netgear:

LNRTSA# - RTS
LNDTRA# - DTR
LNSOUTA - TXD
GND - GND
GND - GND
LNSINA - RXD
LNDSRA# - DSR
LNCTSA# - CTS

However, the item you bought is apparently for Cisco. Here's their pinout:
https://www.cisco.com/c/en/us/td/docs/wireless/access_point/1240/installation/guide/1240hig5/124h_e.pdf

One difference I see it there's no provision for the handshaking signals. I don't know if that's a factor with that device, but years ago, it was common to loop back RTS - CTS and DSR - DTR. What happens if you loop back TXD - RXD? You should see the characters echo back, as you type

Do you have any other serial devices you can test with? Use can use an RJ-45 jack as a breakout box.

smcgowan

Thanks for the further info @JKnott, you're extremely helpful! I might cut off the RJ45 end and crimp a new end with a new pinout. I'm almost sure that's the issue, unless the hardware is literally just that |=(_)(|<3|).

I did have one other thought, maybe someone can help me with this... This particular board has a "Golden Finger" (PCI-e expansion connector) on it. Can this be utilized in some way to connect a graphics card for video output so that I can still possibly salvage this unit?

JKnott

@smcgowan said in RJ45 Console access:

I might cut off the RJ45 end and crimp a new end with a new pinout.

If I'm not mistaken, the pin out listed earlier has the same TXD and RXD as the Cisco, so it should work. So, please verify what you have before you cut. If I had it here, it wouldn't take me long to check it, but it's difficult to explain the process here.

stephenw10

Yes that cable should work. The pinout is the same as listed for the FW-7551:
http://www.lannerinc.com/phocadownload/user-manuals/x86-network-appliances/FW-7551_manual_v1.3_20170509.pdf

It seems like either a bad cable or bad terminal setting somehow. Are you sure it's com5?

The 3 minute period for the reboot seems a lot like a filesystem panic in which case it probably can be escaped or at least reinstalled with a working console.

Do you know if it's running Nano from a CF card or full install from an SSD? Both were options when purchased.
If it's Nano you can always reflash the last available Nano image to it without needing a console at all. Though it really should be running a full install of 2.4.4 at this point even it that's from CF.

Steve

smcgowan

@jknott said in RJ45 Console access:

@smcgowan said in RJ45 Console access:

I might cut off the RJ45 end and crimp a new end with a new pinout.

If I'm not mistaken, the pin out listed earlier has the same TXD and RXD as the Cisco, so it should work. So, please verify what you have before you cut. If I had it here, it wouldn't take me long to check it, but it's difficult to explain the process here.

You're absolutely right, it matches the manual's console pinout (both Netgate and Lanner Inc). Here are two pictures of the RJ45 end, with the color of each wire viewable:

@stephenw10 said in RJ45 Console access:

Yes that cable should work. The pinout is the same as listed for the FW-7551:
http://www.lannerinc.com/phocadownload/user-manuals/x86-network-appliances/FW-7551_manual_v1.3_20170509.pdf

It seems like either a bad cable or bad terminal setting somehow. Are you sure it's com5?

Yes. Device Manager shows COM5 as the "USB Serial Port"

The 3 minute period for the reboot seems a lot like a filesystem panic in which case it probably can be escaped or at least reinstalled with a working console.

Excellent! If I can eventually get into the console.

Do you know if it's running Nano from a CF card or full install from an SSD? Both were options when purchased.
If it's Nano you can always reflash the last available Nano image to it without needing a console at all. Though it really should be running a full install of 2.4.4 at this point even it that's from CF.

It's a CF. I don't know what version is currently installed, because I only have to access that router every once in a great while when they contact me with an issue. Typically, the router isn't even the issue, but I always go in and check to make sure and to make them feel better.

I'll do some digging into reflashing the device, thanks Steve :)

Oh and Colin Wu over at Lanner Inc was very helpful. The Lannerinc.com's site has an automated chatbot that pops up to see if you have questions. I had sent this question last night: "My only question is if you have an RJ45 to USB console cable you'd recommend for this device? I currently have a client with one and it reboots after about 3 minutes so I need to access the console.". Colin was notified of a missed chat message at some point today and he sent me an email in which he told me to try the following cable: https://www.amazon.com/Console-Essential-Accesory-Ubiquity-Switches/dp/B01AFNBC3K. By all appearances, that cable matches the one I bought in terms of pinout. That is, it does on the RJ45 side. The linked product above includes pin layout for the USB side in it's product pictures on Amazon.

Alright guys, I'm off to go eat and walk by friggin' large dogs (85lbs and 121lbs!!!).
Have a good evening,
Sherwood

mikeisfly

If someone has the correct console cable they can do a continuity check to pinout the cable and post the pinout here. The so called cisco admin cable is a "rollover" cable. Sometime I cut the RJ45 connector off and flip the connector to make it work. Really what you want to do is make sure that the following pins go to each other.

RXD - TXD
RTS - CTS
DTR - DSR
GND - GND
and it should be this way on both sides of the cable on the RJ45 and DB9 sides.

mikeisfly

Here is the pinout for a RS-232 port for a PC

1 CD «— Carrier Detect
2 RXD «— Receive Data
3 TXD —» Transmit Data
4 DTR —» Data Terminal Ready
5 GND System Ground
6 DSR «— Data Set Ready
7 RTS —» Request to Send
8 CTS «— Clear to Send
9 RI «— Ring Indicator

mikeisfly

Your cable should look like this:

RJ45 ------ DB9
1 RTS -> CTS 8
2 DTR -> DSR 6
3 TXD -> RXD 2
4 GND -> GND 5
5 GND -> GND 5
6 RXD -> TXD 3
7 DSR -> DTR 4
8 CTS -> RTS 7
***********N/A 9
*Pin 4 on the RJ45 side is probably not used

I do not have the cable or the firewall that you have but using a multi-meter set to the diode test (make sure it's set to audio) you can verify your pinout. This should be the cable pinout if someone can confirm. While the cisco admin cable matches the pins it doesn't have all the pins and I'm not sure which signal the box actually uses.

mikeisfly

Just thought of something you might want to try to turn your flow control to off. Using putty the default is XON/XOFF

JKnott

BTW, as I mentioned in another thread, it's DE-9, not DB-9.

D-subminiature

A lot of people get this wrong.

mikeisfly

Thanks for the clarification/Correction.

stephenw10

The default flow control setting is off, yes. It looked like it was set to off in putty in the previous screenshots though.

It is possible to disable console redirection entirely in the BIOS. If you still see nothing at all it might be worth a cmos reset to bring back the default bios values.

Steve

smcgowan

@jknott said in RJ45 Console access:

BTW, as I mentioned in another thread, it's DE-9, not DB-9.

So funny, I make that mistake all the time. Even the mfgrs list this wrong on Amazon

smcgowan

@stephenw10 said in RJ45 Console access:

The default flow control setting is off, yes. It looked like it was set to off in putty in the previous screenshots though.

I modified the various settings into various matching combinations. Still no dice.

It is possible to disable console redirection entirely in the BIOS. If you still see nothing at all it might be worth a cmos reset to bring back the default bios values.

What jumper needs changed to accomplish a bios reset?

Thanks again everyone, this is helping. Soooo much more info than the manual gives

stephenw10

Hmm, seems like there might not be one amazingly, or at least I can't see one in the manual.

You could just pull the battery for a few minutes instead.

Edit: There is a jumper next to the battery labelled JBAT1 which I would guess will clear it.

Steve