Lantronix SCS Reference Manual page 46

Console Server Features
The table below shows some examples to help you understand how the SCS handles breaks.
If
The user Telnets to a remote network host
from a local (SCS) serial port
The user issues a Connect Local command
to another serial port from a local (SCS)
serial port
The user Telnets to the SCS Local> prompt
and
issues a Connect Local command to a
serial port
The user on an SCS serial port makes an
SSH connection to a network host
At the Local> prompt, the user Telnets to
the SCS
and
receives the default AltBreak character
from template port 0
Table 3-1: Examples of Alternate Break Sequences
And
The serial port has
Break = Local
The serial port has
Break = Remote
The user's serial
port has Break =
Local
The user's serial
port has Break =
Remote
Template port has
Break = Remote
Template port 0 has
Break = Local
The serial port has
Break = Local
The serial port has
Break = Remote
Template port 0 has
Break = Local
Template port 0 has
Break = Remote
Then
The AltBreak sequence returns
the user to a local (SCS)
command prompt.
The AltBreak sequence causes
the SCS to transmit a Telnet
Break IAC sequence to the
remote host.
The AltBreak sequence returns
the user to a local (SCS)
command prompt.
The AltBreak sequence generates
a break condition to the target
port. (The target port's break
settings do not apply or affect this
situation.)
The AltBreak sequence returns
the user to a local (SCS)
command prompt.
The AltBreak sequence generates
a break condition to the target
port. (The target port's break
settings do not apply or affect this
situation.)
The AltBreak sequence returns
the user to a local (SCS)
command prompt.
Nothing happens as there is no
way to propagate a break across
an SSH connection.
The AltBreak sequence does
nothing because breaks are
ignored at the Local> prompt.
3-11
Managing the Attached Devices