>> MIB - Management Information Base

>> Table: biboPPPProfileTable - (.1.3.6.1.4.1.272.4.3.5.1)

Description: The biboPPPProfileTable contains PPP default parameters used for PPP negotiation with unknown dialin partners. For PPP connections, PPP profiles are asigned to incoming connections via the isdnDispatchTable. Currently no entries can be created or deleted by user.

biboPPPProfileTable
OIDNameTypeAccess
.1NameENUMR
.2AuthProtocolENUMRW
.3AuthRadiusENUMRW
.4LQMonitoringENUMRW
.5PPPoEDevIfIndexINTEGERRW
.7CallbackNegotiationENUMRW

Name
The name of the PPP profile. Three profiles are available.

Enumerations:

  • profile-1 (1)
  • profile-2 (2)
  • profile-3 (3)
AuthProtocol
The type of authentication used on the point-to-point link as described in RFC 1334. See biboPPPAuthentication for further details.

Enumerations:

  • none (1)
  • pap (2)
  • chap (3)
  • both (4)
  • ms-chap (6)
  • all (7)
  • ms-chapv2 (8)
AuthRadius
This entry is used to configure possible RADIUS authentication on incoming calls. The default value is inband(2), only inband RADIUS requests (PAP, CHAP) are sent to the defined RADIUS server. Outband requests (CALLERID) are sent in outband(3) mode. If set to both(3), both requests are sent. To disable RADIUS requests in the profile set this value to none(1). To disable authentication attempts via the local data base set this value to radius-only(5).

Enumerations:

  • none (1)
  • inband (2)
  • outband (3)
  • both (4)
  • radius-only (5)
LQMonitoring
This parameter enables (2) or disables (1) PPP Link Quality Monitoring (LQM) according RFC 1989. When set to on(2) LQM is added to the list of parameters acknowledged in LCP negotiation. Link quality reports (LQR) will be generated and send periodically.

Enumerations:

  • off (1)
  • on (2)
PPPoEDevIfIndex
Specifies the device to be used for PPP over Ethernet (PPPoE) according RFC 2516.
CallbackNegotiation
Specifies wether callback negotiation (LCP/CBCP) is allowed or not. If set to disabled(1), no callback negotiation will be performed or accepted. If set to enabled(2), PPP callback negotation will be accepted on demand. If this object is set to cbcp-optional(3), the CBCP option 'no callback' is also offered to the Windows client so that the user can decide wether he wants to be called back or not.

Enumerations:

  • disabled (1)
  • enabled (2)
  • cbcp-optional (3)


MIB Reference to Software Version 10.2.12 generated on 2023/08/29. Provided by webmaster@bintec-elmeg.com
Copyright ©2023 by bintec elmeg GmbH