![Telindus 1031 User And Reference Manual Download Page 275](http://html.mh-extra.com/html/telindus/1031/1031_user-and-reference-manual_1083538275.webp)
Telindus 1031 Router
Chapter 11
Reference manual
265
telindus1031/g703[ ]/channel[ ]/ppp/myAuthenstate
This attribute displays the authentication state of the router at this side (local side) of the link. I.e. the
state of the authenticator. Possible values are:
telindus1031/g703[ ]/channel[ ]/ppp/hisAuthenstate
This attribute displays the authentication state of the router at the other side (remote side) of the link. I.e.
the state of the peer. Possible values are:
telindus1031/g703[ ]/channel[ ]/ppp/bridging
This attribute displays the bridging status of the PPP link.
Refer to
telindus1031/lanInterface/bridging
for a detailed description of the
bridging
structure.
Value
Description
No-Authentication
The local side does not request PPP authentication or still has to start the CHAP
authentication (LCP handshake is busy).
Wait-On-Response
The local side has sent a challenge packet and is waiting for an answer.
Authen-Successful
The response packet is found to be correct. This is the state when authentication
succeeded.
Authen-Failure
The response packet is found to be incorrect. This is a transient state since the
router starts the LCP handshake again after a failing authentication.
Value
Description
No-Authentication
This is the start-up state.
Wait-On-Challenge
During the LCP handshake the authenticator already indicates it wants to authen-
ticate. From that moment on, the peer awaits a challenge packet.
Wait-On-Success
Once the peer has sent a response, it awaits a success or failure message.
Authen-Successful
The peer has received a success packet. It remains in this state during data trans-
fer.
Authen-Failure
The peer has received a failure packet. This is a transient state since the router
starts the LCP handshake again after a failing authentication.
Authen-Not-Allowed
This state only occurs when the peer does not accept the authentication request
during the LCP handshake. A possible reason might be that the peer router does
not support CHAP.
Summary of Contents for 1031
Page 11: ...Telindus 1031 Router User manual 1 User manual ...
Page 12: ...Telindus 1031 Router User manual 2 ...
Page 80: ...Telindus 1031 Router Chapter 5 User manual Basic configuration 70 ...
Page 168: ...Telindus 1031 Router Chapter 8 User manual Configuring the bridge 158 ...
Page 179: ...Telindus 1031 Router Reference manual 169 Reference manual ...
Page 180: ...Telindus 1031 Router Reference manual 170 ...
Page 308: ...Telindus 1031 Router Chapter 11 Reference manual Status attributes 298 ...
Page 336: ...Telindus 1031 Router Chapter 12 Reference manual Performance attributes 326 ...
Page 348: ...Telindus 1031 Router Chapter 13 Reference manual Alarm attributes 338 ...
Page 362: ...Telindus 1031 Router Chapter 15 Reference manual Auto installing the Telindus 1031 Router 352 ...
Page 370: ...Telindus 1031 Router Chapter 16 Reference manual Downloading software 360 ...
Page 380: ...Telindus 1031 Router Chapter 17 Reference manual Technical specifications 370 ...
Page 381: ...Telindus 1031 Router Annex 371 Annex ...
Page 382: ...Telindus 1031 Router Annex 372 ...
Page 384: ...Telindus 1031 Router Annex A Annex common TCP and UDP numbers 374 ...
Page 386: ...Telindus 1031 Router Annex B Annex product information 376 ...