UPDATE: Re: Question regarding SSH via Lantronix SCS100

I played with it and here is what happened. So I configured the SCS100
to do SSH and to authenticate the SSH connection with a local
username/password. When I SSH to the address I gave the SCS100 It
authenticates me and then in PuTTY (my SSH client) it states 'server
unexpectedly closed connection'. This is not the same message that I
get if the credentials are incorrect. So I am getting authenticated
but just not getting to the router.

What I need is to understand; (1) do I need to send this to the
CONSOLE or AUX port on the router, or does it matter, and (2) what
configuration needs to be on the router line to allow it to talk? It
appears from the statistics on the SCS100 that it is sending data out
the serial port just not receiving any back, in other words the router
refuses to answer. I have been trying using the CONSOLE port, and
usually when you do this kind of thing to to the AUX port you have to
configure modem controls, i.e. Modem InOut or ModemDialin but you
can't configure modem controls on the CONSOLE port.

Any suggestions?

Robert B. Phillips, II

On Thu, 18 May 2006 00:58:47 -0400, "Randal T. Rioux"
<randy@xxxxxxxxxxxxxxx> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Robert B. Phillips, II wrote:
I have been tasked with implementing SSH authentication to our Cisco
1751-V routers via a Lantronix SCS100. The Lantronix SCS100 is an
external secure console server that handles SSH authentication. The
box has an ethernet interface and a DB-25 interface, from what I have
ascertained, you give the box an IP, you connect ethernet to the
ethernet on your router and you connect the serial to the console
port.

Here are my questiona; First, does anyone have any experience with
this product or implementing one like it? Second, how would one
configure the console port to accept this connection, the installation
guide gives no clues.

Any feedback that migh help would be greatly appreciated.

I use an SCS820, I'm not sure how similar they are, but here is the
general premise.

Connect the serial ports on the SCS to the systems. The wiring can be
special, so if you don't have the correct pinouts/adapters you will have
strange results. I use a patch panel between the SCS and servers, with
my own special wiring.

Configure the SCS for SSH access. Once into the system, you connect to
the port number connected to your target server. On the SCS820 for
example, to connect to port 2 (9600 8N1 to, oh maybe a PIX 515e) you type:

scs820> direct 2

Smack enter and you should see what you would if directly connected.

Download the manual at lantronix.com. They have wiring guides too.

....I just checked - yours is a one port direct box. This all may be
completely useless to you. But there it is :-)
.

Relevant Pages

  • Re: SSH options re: NAT
    ... No, SSH is two-fold, a call to it on the client side results in a call ... port, meaning that any connections that come into that port are answered ... programming practice for daemons) Once the connection is established, ... don't want to execute a command on the remote side and you use -N. ...
    (comp.security.ssh)
  • Re: OpenSSH remote port forwarding
    ... use an outgoing SSH connection from here to the Internet... ... Incoming SSH it is possible and it is working. ... > I read many docs on the OpenSSH port forwarding, ... > (this command should open an ssh connection to public-machine and there, ...
    (comp.security.ssh)
  • Re: SFTP
    ... > avoid port transient net devices dropping port 22 ... Port 21 is allocated for FTP, not SSH. ... SSH connection. ... Do not get it mixed up with FTPS. ...
    (SSH)
  • Re: SSH tunneling/port forwarding and stateful packet inspection
    ... > have reconfigured SSH to run over port 443 the trace shows it as SSL ... Your packet trace identifies the TCP connection as ...
    (comp.security.ssh)
  • Re: how to re-use existing session?
    ... but I had to authenticate to forward the port. ... a session running, although it's in the background. ... I can also remove the -N switch to the initial SSH command, ...
    (comp.security.ssh)