Indicates the PPP authentication protocol that the
device will require a remote peer to use to
authenticate itself when the device receives an
incoming call from the remote peer. (The device
never requires a remote peer to authenticate itself
when the device initiates an outgoing call to a
remote peer.)
If the value of the ansProfConnProfRequired object
is 'connProfNotRequired(2)', the device ignores the
actual value of this object and behaves as if it has
the value 'authNone(1)'.
If the value of this object is 'authNone(1)', the
device will not request the use of an authentication
protocol during the Link Establishment phase of PPP
link establishment, and the remote peer will not be
required to authenticate itself. The device will
attempt to match the remote peer's IP address with
an instance of the connProfRemIpAddr object. If it
successfully matches a connProfileTable entry, the
connection will be governed by the parameters
specified by the connProfileTable entry. If the
device is unable to match a connProfileTable entry,
the connection will be governed by a temporary
connection profile created from the values of the
following objects:
ansProfIsdnBandwidth
ansProfRxRip
ansProfTxRip
ansProfFilterSetIndex
ansProfIdleSeconds
ansProfPppMaxRecvUnit
ansProfPppLinkCompression
ansProfIsdnInForce56K
If the value of this object is 'authPAP(2)', and the
value of the ansProfConnProfRequired object
is 'connProfRequired(1)', the device
will require the remote peer to authenticate itself
using the Password Authentication Protocol (PAP)
described in RFC 1334. The device will attempt to
match the Peer-ID and Password sent by the remote
peer in its PAP Authenticate-Request packet to the
connProfPppRecvAuthName and connProfPppRecvAuthSecret
objects, respectively, in a connProfileTable entry. If
the device successfully matches a connProfileTable
entry, the call will be accepted, and the connection
will be governed by the parameters specified by
the connProfileTable entry. If the device is unable
to match a connProfileTable entry, the call will
be rejected.
If the value of this object is 'authCHAP(3)', and the
value of the ansProfConnProfRequired object
is 'connProfRequired(1)', the device will require
the remote peer to authenticate
itself using the Challenge-Handshake Authentication
Protocol (CHAP) described in RFC 1334. During the
Authentication phase of PPP link establishment, the
device will send a CHAP Challenge packet to, and expect
a CHAP Response packet from, the remote peer. The
ansProfChapChallengeName object indicates the Name
that the device will send in its CHAP Challenge packet. The
device will attempt to match the Name sent by the
remote peer in its CHAP Response packet to the
connProfPppRecvAuthName object in a connProfileTable
entry. The device use the connProfPppRecvAuthSecret
value in each matching connProfileTable entry to
attempt to verify the Response Value in the remote
peer's CHAP Response packet. If the device successfully
matches a connProfileTable entry, the call will be
accepted, and the connection will be governed by the
parameters specified by the connProfileTable entry. If
the device is unable to match a connProfileTable
entry, the call will be rejected.
Parsed from file netopia-mib.txt
Company: None
Module: NETOPIA-MIB
Indicates the PPP authentication protocol that the
device will require a remote peer to use to
authenticate itself when the device receives an
incoming call from the remote peer. (The device
never requires a remote peer to authenticate itself
when the device initiates an outgoing call to a
remote peer.)
If the value of the ansProfConnProfRequired object
is 'connProfNotRequired(2)', the device ignores the
actual value of this object and behaves as if it has
the value 'authNone(1)'.
If the value of this object is 'authNone(1)', the
device will not request the use of an authentication
protocol during the Link Establishment phase of PPP
link establishment, and the remote peer will not be
required to authenticate itself. The device will
attempt to match the remote peer's IP address with
an instance of the connProfRemIpAddr object. If it
successfully matches a connProfileTable entry, the
connection will be governed by the parameters
specified by the connProfileTable entry. If the
device is unable to match a connProfileTable entry,
the connection will be governed by a temporary
connection profile created from the values of the
following objects:
ansProfIsdnBandwidth
ansProfRxRip
ansProfTxRip
ansProfFilterSetIndex
ansProfIdleSeconds
ansProfPppMaxRecvUnit
ansProfPppLinkCompression
ansProfIsdnInForce56K
If the value of this object is 'authPAP(2)', and the
value of the ansProfConnProfRequired object
is 'connProfRequired(1)', the device
will require the remote peer to authenticate itself
using the Password Authentication Protocol (PAP)
described in RFC 1334. The device will attempt to
match the Peer-ID and Password sent by the remote
peer in its PAP Authenticate-Request packet to the
connProfPppRecvAuthName and connProfPppRecvAuthSecret
objects, respectively, in a connProfileTable entry. If
the device successfully matches a connProfileTable
entry, the call will be accepted, and the connection
will be governed by the parameters specified by
the connProfileTable entry. If the device is unable
to match a connProfileTable entry, the call will
be rejected.
If the value of this object is 'authCHAP(3)', and the
value of the ansProfConnProfRequired object
is 'connProfRequired(1)', the device will require
the remote peer to authenticate
itself using the Challenge-Handshake Authentication
Protocol (CHAP) described in RFC 1334. During the
Authentication phase of PPP link establishment, the
device will send a CHAP Challenge packet to, and expect
a CHAP Response packet from, the remote peer. The
ansProfChapChallengeName object indicates the Name
that the device will send in its CHAP Challenge packet. The
device will attempt to match the Name sent by the
remote peer in its CHAP Response packet to the
connProfPppRecvAuthName object in a connProfileTable
entry. The device use the connProfPppRecvAuthSecret
value in each matching connProfileTable entry to
attempt to verify the Response Value in the remote
peer's CHAP Response packet. If the device successfully
matches a connProfileTable entry, the call will be
accepted, and the connection will be governed by the
parameters specified by the connProfileTable entry. If
the device is unable to match a connProfileTable
entry, the call will be rejected.
Parsed from file NETOPIA-MIB.mib
Module: NETOPIA-MIB
Vendor: Farallon Computing, Inc.
Module: NETOPIA-MIB
[Automatically extracted from oidview.com]
ansProfPppRecvAuthProt OBJECT-TYPE SYNTAX INTEGER { authNone(1), authPAP(2), authCHAP(3) } ACCESS read-write STATUS mandatory DESCRIPTION "Indicates the PPP authentication protocol that the device will require a remote peer to use to authenticate itself when the device receives an incoming call from the remote peer. (The device never requires a remote peer to authenticate itself when the device initiates an outgoing call to a remote peer.) If the value of the ansProfConnProfRequired object is 'connProfNotRequired(2)', the device ignores the actual value of this object and behaves as if it has the value 'authNone(1)'. If the value of this object is 'authNone(1)', the device will not request the use of an authentication protocol during the Link Establishment phase of PPP link establishment, and the remote peer will not be required to authenticate itself. The device will attempt to match the remote peer's IP address with an instance of the connProfRemIpAddr object. If it successfully matches a connProfileTable entry, the connection will be governed by the parameters specified by the connProfileTable entry. If the device is unable to match a connProfileTable entry, the connection will be governed by a temporary connection profile created from the values of the following objects: ansProfIsdnBandwidth ansProfRxRip ansProfTxRip ansProfFilterSetIndex ansProfIdleSeconds ansProfPppMaxRecvUnit ansProfPppLinkCompression ansProfIsdnInForce56K If the value of this object is 'authPAP(2)', and the value of the ansProfConnProfRequired object is 'connProfRequired(1)', the device will require the remote peer to authenticate itself using the Password Authentication Protocol (PAP) described in RFC 1334. The device will attempt to match the Peer-ID and Password sent by the remote peer in its PAP Authenticate-Request packet to the connProfPppRecvAuthName and connProfPppRecvAuthSecret objects, respectively, in a connProfileTable entry. If the device successfully matches a connProfileTable entry, the call will be accepted, and the connection will be governed by the parameters specified by the connProfileTable entry. If the device is unable to match a connProfileTable entry, the call will be rejected. If the value of this object is 'authCHAP(3)', and the value of the ansProfConnProfRequired object is 'connProfRequired(1)', the device will require the remote peer to authenticate itself using the Challenge-Handshake Authentication Protocol (CHAP) described in RFC 1334. During the Authentication phase of PPP link establishment, the device will send a CHAP Challenge packet to, and expect a CHAP Response packet from, the remote peer. The ansProfChapChallengeName object indicates the Name that the device will send in its CHAP Challenge packet. The device will attempt to match the Name sent by the remote peer in its CHAP Response packet to the connProfPppRecvAuthName object in a connProfileTable entry. The device use the connProfPppRecvAuthSecret value in each matching connProfileTable entry to attempt to verify the Response Value in the remote peer's CHAP Response packet. If the device successfully matches a connProfileTable entry, the call will be accepted, and the connection will be governed by the parameters specified by the connProfileTable entry. If the device is unable to match a connProfileTable entry, the call will be rejected." REFERENCE "PPP Authentication Protocols, RFC 1334" ::= { isdnParams 16 }
ansProfPppRecvAuthProt OBJECT-TYPE SYNTAX INTEGER { authNone(1), authPAP(2), authCHAP(3) } ACCESS read-write STATUS mandatory DESCRIPTION "Indicates the PPP authentication protocol that the device will require a remote peer to use to authenticate itself when the device receives an incoming call from the remote peer. (The device never requires a remote peer to authenticate itself when the device initiates an outgoing call to a remote peer.) If the value of the ansProfConnProfRequired object is 'connProfNotRequired(2)', the device ignores the actual value of this object and behaves as if it has the value 'authNone(1)'. If the value of this object is 'authNone(1)', the device will not request the use of an authentication protocol during the Link Establishment phase of PPP link establishment, and the remote peer will not be required to authenticate itself. The device will attempt to match the remote peer's IP address with an instance of the connProfRemIpAddr object. If it successfully matches a connProfileTable entry, the connection will be governed by the parameters specified by the connProfileTable entry. If the device is unable to match a connProfileTable entry, the connection will be governed by a temporary connection profile created from the values of the following objects: ansProfIsdnBandwidth ansProfRxRip ansProfTxRip ansProfFilterSetIndex ansProfIdleSeconds ansProfPppMaxRecvUnit ansProfPppLinkCompression ansProfIsdnInForce56K If the value of this object is 'authPAP(2)', and the value of the ansProfConnProfRequired object is 'connProfRequired(1)', the device will require the remote peer to authenticate itself using the Password Authentication Protocol (PAP) described in RFC 1334. The device will attempt to match the Peer-ID and Password sent by the remote peer in its PAP Authenticate-Request packet to the connProfPppRecvAuthName and connProfPppRecvAuthSecret objects, respectively, in a connProfileTable entry. If the device successfully matches a connProfileTable entry, the call will be accepted, and the connection will be governed by the parameters specified by the connProfileTable entry. If the device is unable to match a connProfileTable entry, the call will be rejected. If the value of this object is 'authCHAP(3)', and the value of the ansProfConnProfRequired object is 'connProfRequired(1)', the device will require the remote peer to authenticate itself using the Challenge-Handshake Authentication Protocol (CHAP) described in RFC 1334. During the Authentication phase of PPP link establishment, the device will send a CHAP Challenge packet to, and expect a CHAP Response packet from, the remote peer. The ansProfChapChallengeName object indicates the Name that the device will send in its CHAP Challenge packet. The device will attempt to match the Name sent by the remote peer in its CHAP Response packet to the connProfPppRecvAuthName object in a connProfileTable entry. The device use the connProfPppRecvAuthSecret value in each matching connProfileTable entry to attempt to verify the Response Value in the remote peer's CHAP Response packet. If the device successfully matches a connProfileTable entry, the call will be accepted, and the connection will be governed by the parameters specified by the connProfileTable entry. If the device is unable to match a connProfileTable entry, the call will be rejected." REFERENCE "PPP Authentication Protocols, RFC 1334" ::= { isdnParams 16 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.304.1.3.1.12.16.0 | ansProfPppRecvAuthProt | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.304.1.3.1.12.1 | isdnSwitchType | 1 | 1 | isdnSwitchtype |
| 1.3.6.1.4.1.304.1.3.1.12.2 | isdnDirNum1 | 1 | 1 | The device's primary ISDN directory number. |
| 1.3.6.1.4.1.304.1.3.1.12.3 | isdnSpid1 | 1 | 1 | The device's primary service profile identifier (SPID). |
| 1.3.6.1.4.1.304.1.3.1.12.4 | isdnDirNum2 | 1 | 1 | The device's secondary ISDN directory number. |
| 1.3.6.1.4.1.304.1.3.1.12.5 | isdnSpid2 | 1 | 1 | The device's secondary service profile identifier (SPID). |
| 1.3.6.1.4.1.304.1.3.1.12.6 | connProfileTable | 1 | 25 | A list of entries providing configuration information for the device's possible on-demand WAN connections to remote peers via ISD… |
| 1.3.6.1.4.1.304.1.3.1.12.7 | ansProfConnProfRequired | 1 | 1 | Indicates whether or not an incoming call must match a connection profile entry in the connProfileTable. If the value of this obj… |
| 1.3.6.1.4.1.304.1.3.1.12.8 | ansProfIsdnBandwidth | 1 | 1 | The number of ISDN B-channels the device will use for incoming calls from remote peers not matching a connection profile in the c… |
| 1.3.6.1.4.1.304.1.3.1.12.9 | ansProfIsdnInForce56K | 1 | 1 | Indicates whether or not the device will ignore the data rate indicated in incoming ISDN calls and assume a data rate of 56K. If t… |
| 1.3.6.1.4.1.304.1.3.1.12.10 | ansProfRxRip | 1 | 1 | Indicates whether or not the device will receive RIP packets over a WAN connection from a remote peer established for an incoming… |
| 1.3.6.1.4.1.304.1.3.1.12.11 | ansProfTxRip | 1 | 1 | ansProftxRip |
| 1.3.6.1.4.1.304.1.3.1.12.12 | ansProfFilterSetIndex | 1 | 1 | Indicates the set of filters to be used to filter packets received and transmitted over the WAN connection to a remote peer not m… |
| 1.3.6.1.4.1.304.1.3.1.12.13 | ansProfIdleSeconds | 1 | 1 | Indicates the number of seconds during which there must be no outbound traffic over a WAN connection to a remote peer not matchin… |
| 1.3.6.1.4.1.304.1.3.1.12.14 | ansProfPppMaxRecvUnit | 1 | 1 | Indicates the size of the largest PPP packet that can be received over a WAN connection with a remote peer established for an inc… |
| 1.3.6.1.4.1.304.1.3.1.12.15 | ansProfPppLinkCompression | 1 | 1 | Indicates whether or not the device will attempt to negotiate PPP link compression for a WAN connection with a remote peer establ… |
| 1.3.6.1.4.1.304.1.3.1.12.17 | ansProfChapChallengeName | 1 | 1 | If the value of the ansProfConnProfRequired object is 'connProfRequired(1)', and the value of the ansProfPppRecvAuthProt object i… |
| 1.3.6.1.4.1.304.1.3.1.12.18 | schedConnTable | 1 | 8 | A list of entries describing automatic, scheduled establishment of connections to the device's remote peers. This table supports … |