Lantronix SLC8, Руководство пользователя для менеджера

Страница: 279 / 299

Appendix F: Protocol Glossary
SLC™ Console Manager User Guide 279

For Dial-on-Demand, the PPP connection will be established when it sees IP traffic destined
for the
Remote IP . When this occurs, the SLC console manager dials the Dial-out Number ,
and if the remote peer requests PAP or CHAP authentication, provides the Dial-out Login
and Dial-out Password as authentication tokens. Once authenticated, a PPP session will be
established using the Local IP and the Remote IP . The PPP connection will stay active until
no IP traffic for the Remote IP is sent for Modem Timeout seconds. Once the timeout has
expired, the PPP connection will be terminated and will not be reestablished for at least
Restart Delay seconds.
Dial-in/Host List —The SLC device waits for a peer to call and establishes a text (command
line) connection to the first host in a Host List that connects. A host list of a prioritized list of
SSH, Telnet or raw TCP hosts to connect to. If
Authentication is enabled for the Host List, the
user will be prompted for a login and password, and will be authenticated via the currently
enabled authentication methods (Local Users, NIS, LDAP, etc). Once authenticated, the SLC
console manager will try to connect to each host in the host list until a successful connection is
established.
Callback Control Protocol (CBCP) Server and CBCP Client —CBCP is a PPP option that
negotiates the use of callback where the server, after authenticating the client, terminates the
connection and calls the client back at a phone number that is determined by the CBCP
handshake. For more information on CBCP, see
http://technet.microsoft.com/en-us/library/
cc957979.aspx . CBCP is used primarily by Microsoft PPP peers. CBCP supports two options
for determining the number to dial on callback: the client can specify a user-defined number
for the server to dial on callback, or the client can request the server use an administrator-
defined number to dial on callback. Optionally, some servers may also allow “no callback” as
an option.

CBCP Server —The SLC device waits for a client to call the SLC console manager,
establishes a PPP connection, authenticates the user, and negotiates a dial-back number with
the client using CBCP. If the SLC device is able to determine a dial-back number to use, it
hangs up and calls the dial-back number.

When a call is received, a PPP connection is established, and the user will be authenticated
via PAP or CHAP (configured with the
Authentication setting). For PAP, the Local User list
will be used to authenticate the login and password sent by the PPP peer. For CHAP, the
CHAP Handshake Host/User Name and Secret/User Password will be used to authenticate
the login and password sent by the PPP peer. Once authenticated, the CBCP handshake with
the client determines the number to use for dial-back. The SLC console manager will present
the client with the available options: if the authenticated user is a Local User with
Allow Dial-
back enabled and a Dial-back Number defined, the administrator-defined option is allowed; if
this is not the case, the user-defined number is allowed.

Additionally, if CBCP Server Allow No Callback is enabled, the client can also select no
callback (the PPP connection established at dial-in will remain up). The client will select from
the available callback options. If the SLC device can determine a dial-back number to use, it
will hang up and wait
Dial-back Delay seconds before initiating the dial-back. The SLC
console manager will dial, and if the remote peer requests PAP or CHAP authentication,
provide the
Dial-out Login and Dial-out Password as authentication tokens. Once
authenticated, a PPP session will be established using either negotiated IP addresses or
specific IP addresses (determined by the
Negotiate IP Address setting).

CBCP Client —The SLC device will dial out to a CBCP server, establish a PPP connection,
negotiate a callback number with the server using CBCP, terminate the connection, and wait
for the server to call back. The SLC console manager dials the
Dial-out Number , and if the
remote peer requests PAP or CHAP authentication, provides the Dial-out Login and Dial-out
Password as authentication tokens. Once authenticated, the CBCP handshake with the
server determines the number to use for dial-back.