Can't access remote console
-
You should be able to reboot the firewall whilst connected to the console. Or even power cycle it.
The USB-serial IC is powered by the client so it will remain up even if the 3100 is powered down.You should always see the uboot output there when it is powered on.
Steve
-
@stephenw10 I don't understand. If I can't get the console to come up at all, how is it going to stay connected during a reboot when it's never connected in the first place?
It shows up as a port in Windows (COM3) but Putty is never able to connect to the SG-3100 over the port connection.
-
As I understand it the console connects, putty allows you to open the port, you just don't see any output on it?
If you reboot it whilst that console window is open you would see output from uboot even if for some reason pfSense was not using the serial console.Steve
-
@stephenw10 No that's not what's happening. I connect the console, which then shows as COM3 in Windows. I open Putty however it will not connect to the console. When I click on the Open button in putty it does not connect.
I've replaced the cable, the computer, and triple checked the COM and settings but nothing gets the console to open.
-
Ah, OK. Then I would expect Putty to show an error when you try, what does it show?
However that rules out a pfSense config issue. There is nothing you can set to make that happen.
Either it's a hardware issue with the USB-serial device or a problem on the client(s).
A hardware issue is possible but I'm not we've ever seen that on an SG-3100. A driver is far more likely but testing from two different clients makes it a lot less so.
Do you have anything else you can try to connect from?Steve
-
@stephenw10 No, there is no error from Putty. It shows nothing.
I went and got another computer. I tried to connect it as well. I tried with multiple USB cables with it too. So now I've tried three different computers and about six cables. None of them can connect to the SC-3100 console. They all do exactly the same thing.. that is, nothing but bing.
I don't see how three computers can all have failed at the same time and all those cables could have failed at the same time. This HAS to be a problem with the SG-3100 or my serial settings (115200, 8, 1, none, xon/xoff). Otherwise I don't see any possibility other than the SG-3100 console port.
-
Hmm, the 'bing' sounds like Windows complaining trying to open the port. Like a permissions error. But I would expect putty to throw an error if that was the case.
Does Windows log an error?Are you able to test with anything that isn't Windows. Boot a live Linux image?
If it really is the virtual com device that has failed and it's in warranty then open a ticket with us. The only option in that case would be to RMA it.
As I said though, I don't think I've ever seen that sort of failure on the SG-3100.Steve
-
@stephenw10 Everything we have here is Windows except for our Proxmox servers. I get lost quickly in Linux. I hate to mess with those Proxmox machines as they are mission critical to our operation.
I doubt there's a warranty on my unit as it was purchased in October 2019.
-
@cdsjerry When you say there is "no error from Putty. It shows nothing." Do you at least see a blank screen? If so, have you tried hitting return a few times at this blank screen? Ignore me if you've tried this too
-
@theonemcdonald No. I don't even see a blank screen. Normally you hit this open button and get the blank screen and can log in from there etc. In this case it's never getting that far. When you hit the open button the computer bings and that's it. There's no communication being established with the console. No window, not box. Nothing.
-
Well I would expect Windows to log an error of some sort. It does really seem like a driver or permissions error.
Otherwise I would boot a live linux image on whatever hardware you have and test from that.
Steve
-
@stephenw10 As I've said, my Linux is really poor. If I spin up a VM Linux box what commands would I need to issue to open the SSH connection?
This seems like a really long shot given that three different computers have not been able to reach it, including the one that we've always used to connect to it in the past and have never had a problem.
-
I agree it seems unlikely but we have seen Windows driver issues in the past.
If you use a VM you introduce the additional issue or passing through a USB port to it. I would just boot a live Linux USB stick on a laptop and then connect form the live session.
In Linux you can just use screen:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/connect-to-console.html#launch-a-terminal-programSteve
-
@stephenw10 I built a Debian Linux machine but I'm having trouble installing the driver due to my lack of Linux experience. I have Putty installed but not the driver so it's not able to connect yet. I don't have a tty/USB0 connection showing. Instead it says /dev/ttyS0 I'm assuming this is because there's no driver.
I have several very busy days ahead of me on other projects so it may be a bit before I can get back to this. I hadn't expected it to take this much effort just to access the console.
-
@stephenw10 My Linux skills (or rather the lack of them) are limiting me. I got a Debian machine built but I can't figure out how to create a com port nor how to install the drivers. When I try to enter the commands I find on the help pages it usually comes back as an unknown command. I'm just lost at this point.
The console is dead to Windows and my Lixux sucks.
-
You should just be able to run something Live from CD or memstick. No need to install.
What version of Debian are you using? Anything recent will have the driver in kernel already.
Try runningdmesgat the command line, then connecting the console and running it again. You should see some new messages from the USB connection.
For example on mt Linux Mint box here I see:[16678.494072] usb 2-2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [16678.494078] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [16678.494082] usb 2-2: Product: CP2104 USB to UART Bridge Controller [16678.494085] usb 2-2: Manufacturer: Silicon Labs [16678.494088] usb 2-2: SerialNumber: 01327307 [16678.495946] cp210x 2-2:1.0: cp210x converter detected [16678.498315] usb 2-2: cp210x converter now attached to ttyUSB0I can then open ttyUSB0 with
screen /dev/ttyUSB0 115200.
You may need to use sudo with that depending on your user.
To escape screen pressctl+athenkthen answery.Steve
-
@stephenw10 I already wiped out a Windows machine so I could do this. I installed Debian 4.19.194-2. When I run the dmesg the second time I do get a line just like your last line. I then open Putty and set the port to /dev/ttyUSB0, speed 15200, 8, 1, none, xon/xoff and click open.... and nothing happens. It's exactly the same as what's happened on all the other computers.
-
So it refuses to open (like in Windows) or it opens and shows no output?
No errors shown?
The current version of Debian is 10.10. That looks more like a kernel version but it's still quite old.
The driver has been in there for a long time though so it should still work. -
@stephenw10 It doesn't open at all. Exact same result as when I tried it with Windows. I click the Open button and literally nothing happens. No errors, no window, no blank window... absolutely nothing.
I wonder why my version is so old. I just downloaded the ISO from debian.org yesterday. I don't know how to make up update. I've found that yum doesn't work at all. I've done apt-get update and it insists that I put my DVD back in the drive. It doesn't seem to be getting online updates? Probably a repository error from the install but again... I don't know how to change it. This is my problem, I just don't use Linux enough to know what I'm doing.
-
If you try using screen instead of putty? Any error shown?
What are the messages actually shown in dmesg when you connect the console?
