Lantronix SLC 32 Lantronix SLC - User Guide - Page 277

Appendix F: Protocol Glossary, LDAP Lightweight Directory Access Protocol

Page 277 highlights

Appendix F: Protocol Glossary BOOTP (Bootstrap Protocol) Similar to DHCP, but for smaller networks. Automatically assigns the IP address for a specific duration of time. CHAP (Challenge Handshake Authentication Protocol) A secure protocol for connecting to a system; it is more secure than the PAP. DHCP (Dynamic Host Configuration Protocol) Internet protocol for automating the configuration of computers that use TCP/IP. DNS (Domain Name Servers) A system that allows a network name server to translate text host names into numeric IP addresses. Kerberos A network authentication protocol that provides strong authentication for client/server applications by using secret-key cryptography. LDAP (Lightweight Directory Access Protocol) A protocol for accessing directory information. Modem State Parameters Dial-in-The SLC console manager waits for a peer to call the SLC unit to establish a text (command line) or PPP connection.  For text connections, the user will be prompted for a login and password, and will be authenticated via the currently the currently enabled authentication methods (Local Users, NIS, LDAP, etc). Once authenticated, a CLI session will be initiated, and the user will remain connected to the SLC console manager until they either logout of the CLI session, or (if Timeout Logins is enabled) the CLI session is terminated if it has been idle.  For PPP connections, 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, a PPP session will be established using either negotiated IP addresses or specific IP addresses (determined by the Negotiate IP Address setting). Dial-out-The SLC console manager dials a remote peer to establish a PPP connection. The SLC device 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 either negotiated IP addresses or specific IP addresses (determined by the Negotiate IP Address setting). Dial-back-The SLC console manager waits for a peer to call the SLC device, establishes a text (command line) or PPP connection, authenticates the user, and if the SLC console manager is able to determine a dial-back number to use, hangs up and calls the dial-back number to establish either a text or PPP connection.  For text connections, the user will be prompted for a login and password, and will be authenticated via the currently the currently enabled authentication methods (Local Users, NIS, LDAP, etc). Once authenticated, the SLC device will use the Dial-back Number SLC™ Console Manager User Guide 277

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299

SLC™ Console Manager User Guide
277
Appendix F:
Protocol Glossary
BOOTP (Bootstrap Protocol)
Similar to DHCP, but for smaller networks. Automatically assigns the IP address for a specific
duration of time.
CHAP (Challenge Handshake Authentication Protocol)
A secure protocol for connecting to a system; it is more secure than the PAP.
DHCP (Dynamic Host Configuration Protocol)
Internet protocol for automating the configuration of computers that use TCP/IP.
DNS (Domain Name Servers)
A system that allows a network name server to translate text host names into
numeric IP
addresses.
Kerberos
A network authentication protocol that provides strong authentication for client/server applications
by using secret-key cryptography.
LDAP (Lightweight Directory Access Protocol)
A protocol for accessing directory information.
Modem State Parameters
Dial-in
—The SLC console manager waits for a peer to call the SLC unit to establish a text
(command line) or PPP connection.
For text connections, the user will be prompted for a login and password, and will be
authenticated via the currently the currently enabled authentication methods (Local Users,
NIS, LDAP, etc). Once authenticated, a CLI session will be initiated, and the user will remain
connected to the SLC console manager until they either logout of the CLI session, or (if
Timeout Logins
is enabled) the CLI session is terminated if it has been idle.
For PPP connections, 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, a PPP session will be established using either negotiated IP
addresses or specific IP addresses (determined by the
Negotiate IP Address
setting).
Dial-out
—The SLC console manager dials a remote peer to establish a PPP connection. The
SLC device 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 either negotiated IP addresses
or specific IP addresses (determined by the
Negotiate IP Address
setting).
Dial-back
—The SLC console manager waits for a peer to call the SLC device, establishes a text
(command line) or PPP connection, authenticates the user, and if the SLC console manager is
able to determine a dial-back number to use, hangs up and calls the dial-back number to establish
either a text or PPP connection.
For text connections, the user will be prompted for a login and password, and will be
authenticated via the currently the currently enabled authentication methods (Local Users,
NIS, LDAP, etc). Once authenticated, the SLC device will use the
Dial-back Number