BIANCA-BRICK-PPP-MIB: View SNMP OID List / Download MIB

The biboPPPTable contains configuration information for the PPP interfaces. Each time a new entry is made here, a corresponding entry is made in the ifTable. Creating entries: Entries are created by assigning a value to the biboPPPType object. Deleting entries: Entries are removed by setting an entry's biboPPPEncapsulation object to 'delete'.

Correlating PPP interface index. This value is assigned automatically by the system.

The type of link. A new dialup link is created when this field is set to the value isdn-dialup(1), dialin-only(3) or multiuser(5). The maximum number of dialup links is limited by system memory. Each dialup link should have at least one corresponding entry in the biboDialTable to configure the remote ISDN telephone number(s). A leased line link, can not be created by setting this field to leased(2), but is automatically established when the IsdnChType field is set to either 'leased-dte' or 'leased-dce' (which doesn't make a difference for PPP, but must be set correctly for other encapsulation methods). Naturally, when the IsdnChType field is set to any other value, the biboPPPTable entry is removed. In both cases, a new entry in the biboPPPTable creates corre- corresponding entries in the ifTable (a new interface) and in the biboPPPStatTable (PPP statistics). Setting this object to multiuser(5), up to biboPPPMaxConn matching incoming connections (see biboPPPAuthentication, biboPPPAuthSecret, biboPPPAuthIdent) from different dialin partners will be accepted. Enumeration: 'multiuser': 5, 'leased': 2, 'isdn-dialup': 1, 'isdn-dialin-only': 3.

The layer 2 encapsulation of the link. The use of ppp(1) as described in RFC 1661 is the preferred encapsulation for point-to-point links. The encapsulation is set to x25(2) for X.25-only links and to x25-ppp(3) for concurrent use of X.25 and PPP. Mpr-lapb(7) and mpr-hdlc(8) are popular proprietary encapsulations. They both use the ethertype number for protocol multiplexing. The former is used when error correction or data compression (v42bis) is desired. The latter (mpr-hdlc) is compatible to Cisco's HDLC encapsulation. On IP-only links it is also possible to use the ISO LAPB protocol (ip-lapb(4)), also known as X.75, or raw hdlc framing (ip-hdlc(6)). The x75-ppp encapsulation provides a proprietary solution for using PPP encapsulation over X.75 (LAPB) framing, x75btx-ppp provides PPP over T.70 and LAPB framing including a BTX protocol header to access BTX services over ISDN links. The x25-nosig(13) encapsulation is used to establish X.25 connections over dialup links without specific signalling on the D-channel (pure data call). The x25-ppp-opt encapsulation provides a special kind of the x25-ppp encapsulation. Dialin partner will be authenticated either outband to establish an X.25 connection via ISDN or optional inband by using the point-to-point protocol (PPP). Concurrent use of X.25 and PPP encapsulation is excluded. The x25-noconfig(16) and x25-noconfig-nosig(17) encapsulations provide a solution fr establishing X.25 connections via ISDN. The dial number will be derived from X.25 destination address by using special rules. V42bis data compression can be enabled on LAPB links only, because v42bis requires an error free connection. Dialup links can be removed by setting this field to delete(5). This has no effect on permanent links. Enumeration: 'ip-hdlc': 6, 'x75-ppp': 11, 'x25-ppp': 3, 'x25-pad': 15, 'x25-nosig': 13, 'x25-noconfig': 16, 'frame-relay': 9, 'x25-noconfig-nosig': 17, 'x75btx-ppp': 12, 'x31-bchan': 10, 'x25-ppp-opt': 14, 'ppp': 1, 'ip-lapb': 4, 'x25': 2, 'mpr-lapb': 7, 'mpr-hdlc': 8, 'delete': 5.

When set to on(1), keepalive packets are sent in regular intervals during the connection. Keepalive packets can not be sent using the ip-lapb or x25 encapsulation. Enumeration: 'on': 1, 'off': 2.

The number of milliseconds waiting before retransmitting a PPP configure packet.

The throughput can be enhanced up to factor three using the V42bis compression method or the Stac LZS compression algorithm. V42bis is currently supported with the ip-lapb and mpr-lapb encapsulation. Stac LZS compression algorithm is provided using PPP encapsulated links, stac(3) indicates support of Sequence checking, ms-stac(4) indicates support of Extended mode which is prefered by Microsoft. Both check modes are implemented according RFC 1974. When set to mppc(5), the Microsoft Point-to-Point Compression (MPPC) Protocol according RFC 2118 is negotiated. MPPC uses an LZ based algorithm with a sliding window history buffer. Enumeration: 'v42bis': 2, 'mppc': 5, 'none': 1, 'ms-stac': 4, 'stac': 3.

The type of authentication used on the point-to-point link as described in RFC 1334. The authentication protocol supports pap(2) (Password Authentication Protocol), chap(3) (Challenge Handshake Authentication Protocol), or both(4). When set to both(4), the link must be successfully authenticated by either CHAP or PAP. The type ms-chap(6) and ms-chapv2(8) are Microsofts proprietary CHAP authentication procedures (using MD4 and DES encryption instead of MD5 encryption algorithm), all(7) includes PAP, CHAP and MS-CHAP. Another way to authenticate dial-in users is by using RADIUS (remote authentication dial in user service). Users can authenticate themselves either using PAP or CHAP (excluding MS-CHAP). In general the system creates PPP interfaces with this authentication itself, but it's also possible to take advance of the RADIUS dial-in services with pre-configured interfaces. See biboAdmRadiusServer for further details. Enumeration: 'pap': 2, 'both': 4, 'none': 1, 'ms-chap': 6, 'all': 7, 'chap': 3, 'radius': 5, 'ms-chapv2': 8.

The remote authentication identification string. The local authentication identification string is taken from the contents of the sysName field, up to the appearance of the first dot (e.g., the remote name would be `brick' if the content of the sysName field was `brick.bintec.de').

The authentication secret, which is used symmetrically for both local and remote sides of the PPP link.

The IP control protocol as described in RFC1332 has a means of negotiating IP-addresses. When this option is set to dynamic-server(2), an available IP-address found in biboPPPIpAddrTable is assigned as the remote IP-address and a temporary route is created during the uptime of the interface. When set to dynamic-client(3), the remote system is asked to tell us our own IP-address. A host route will be created during the uptime of the interface. In most cases this option will be set automatically by the network address translation option. In static(1) mode, address-negotiation is not forced. Enumeration: 'dynamic-server': 2, 'static': 1, 'dynamic-client': 3.

Time in seconds to wait before retrying a call; currently not used.

Time in seconds to wait after a connection failure (e.g. the number of biboPPPMaxRetries calls failed). When set to zero, the interface state is never set to blocked.

The number of dialup retries before changing to the blocked state.

The time in seconds to wait, once the channel is silent, (that is, no data is being received or transmitted) before terminating the link. When set to zero the short hold mode is disabled, when set to -1 the short hold mode is disabled and the link will be reconnected when connection was lost.

The number of channels to initially set up for this interface.

The maximum number of channels bundled for this interface.

The minimum number of channels bundled for this interface.

If this object is enabled(1), and the call is recognized by the dialed number then calls are never accepted, and a callback is forced for incoming calls at once. The callback can be delayed for biboPPPRetryTime seconds by setting this entry to delayed(5). If the call is recognized by inband authentication (PAP or CHAP) then the actual connection is closed and a callback is performed at once. Setting this value to ppp-offered(4) allows a called peer to call back the calling site if offered by PPP negotiation. For PABX dialout a dialprefix is added to the number, if offered by the calling site (see isdnStkTable). If this object is set to expected(3), only one initial outgoing call is made expecting a callback. If this object is set to ppp-callback-optional(6), 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. Enumeration: 'ppp-callback-optional': 6, 'enabled': 1, 'ppp-offered': 4, 'delayed': 5, 'disabled': 2, 'expected': 3.

This entry is used to select the layer 1 protocol settings for this partner. Normally the correct entry is hdlc-64. Enumeration: 'v110-4800': 7, 'v110-38400': 11, 'data-56k': 2, 'v110-9600': 8, 'data-64k': 1, 'aodi': 22, 'pppoe': 21, 'v110-19200': 10, 'pptp-pac': 23, 'v110-1200': 5, 'v110-14400': 9, 'dovb': 4, 'v110-2400': 6, 'modem-profile-6': 17, 'modem-profile-7': 18, 'modem-profile-4': 15, 'modem-profile-5': 16, 'modem-profile-2': 13, 'modem-profile-3': 14, 'pptp-pns': 20, 'modem-profile-1': 12, 'modem': 3, 'modem-profile-8': 19.

A textual string containing a login sequence (script) composed of fields in the format [expect send], comparable to chat scripts commonly used on other sytems. This script is required i.e. to establish an asynchronus PPP dialup connection to CompuServe.

This entry is used to enable Van Jacobsen TCP/IP header compression, which reduces the size of TCP/IP packet headers and increases the efficiency of line utilization. Enumeration: 'disabled': 2, 'enabled': 1.

This object specifies the layer 2 mode to be used for a connection. It is only relevant, if the Encapsulation involves an LAPB protocol. This is the case for x25, x25-ppp, ip-lapb, lapb, x31-bchan, x75-ppp, x75btx-ppp, x25-nosig. The Default value of this object is auto. For dialup connection, the layer 2 mode will than be DTE, on the calling side and DCE on the called side. For permanent connections, the layer 2 mode is set at lower layers (for example isdnChType in the isdnChTable). When this object is set to dte or dce, the layer 2 mode will always be DTE or DCE, regardless of the call direction or the settings at the lower layer. Enumeration: 'auto': 1, 'dce': 3, 'dte': 2.

Optimizes idle time disconnects depending on the charging information received during the connection. This value specifies the minimum inactivity time (channel is silent) in percents of the current charging interval length and is only used for outgoing connections. Incoming connections are disconnected after idle time according to the value biboPPPShortHold. Please note that this only works if your ISDN port has the AOCD service enabled (advice of charging during the call). For instance in Germany this is an extra paid service. (Even the 'Komfortanschluss' does only include AOCE [advice of charge at the end of the call], so AOCD has to be ordered and paid extra.)

This is the local identification string used for PPP authentication(PAP/CHAP). If this entry is empty the variable biboAdmLocalPPPIdent will be used.

The IP control protocol extensions as described in RFC 1877 has a means of negotiating primary and secondary Domain Name System (DNS) server addresses. When this option is disabled(1), no DNS negotiation will be performed. If enabled(2), DNS negotiation behavier depends on biboPPPIpAddress switch (client or server mode). Setting to dynamic-client(3), the remote system is asked to tell us the IP-address(es) of primary and/or secondary DNS. Setting to dynamic_server(4), primary and/or secondary DNS IP-address(es) found in biboAdmNameServer or biboAdmNameServ2, if asked, will be send to remote. Enumeration: 'disabled': 1, 'dynamic-server': 4, 'enabled': 2, 'dynamic-client': 3.

This field specifies the data encryption scheme for en(de)crypting PPP encapsulated multi-protocol datagrams. Setting to mppe-40(2), mppe-128(3) or mppe-56(7) the Microsoft Point to Point Encryption Protocol (MPPE) will be enabled, using a 40 bit, 128 bit respectively 56 bit session key for initializing encryption tables. Setting to mppev2-40(8), mppev2-56(9) or mppev2-128(10) the Microsoft Point to Point Encryption Protocol (MPPE) 'stateless mode' will be enabled, using a 40 bit, 56 bit respectively 128 bit session key. Enumeration: 'mppe-40': 2, 'triple-des-168': 5, 'none': 1, 'mppe-56': 7, 'mppev2-56': 9, 'des-56': 4, 'mppe-128': 3, 'blowfish-56': 11, 'mppev2-128': 10, 'blowfish-168': 6, 'mppev2-40': 8.

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 used in LCP negotiation. If LQM is acknowledged by peer link quality reports will be generated and send periodically. Enumeration: 'on': 2, 'off': 1.

Pool ID value to select an IP address pool for dynamic IP address assignment via IPCP. See also PPPIpAssignTable for further details.

Maximum number of seconds before termination the established PPP session, regardless there is any data throughput on the corresponding link(s). When set to 0, there no limit for the duration of the PPP session.

The biboPPPStatTable contains statistical connection- specific information. Only the system can add or delete entries to this table. Creating entries: Entries are created by the system each time a new PPP interface is created in the biboPPPTable. Deleting entries: Entries are removed by the system when the corresponding PPP interface is removed.

Correlating PPP interface index.

The actual number of bundled channels.

The bitwise ORed protocols successfully negotiated on this connection; currently the following protocols are supported: tcp/ip(1), ipx(2), bridge(4), bpdu(8), x25(16). These protocol values are most likely to change in future software releases.

The physical state of the link. This field is obsolete and will not be supported in a future release. Enumeration: 'outgoing': 3, 'incoming': 2, 'dataxfer': 5, 'idle': 1, 'connected': 4, 'disconnect': 6.

The current link duration on this interface in seconds.

The current costs on this interface for all member links.

The octets transmitted on this interface since its last change to the 'up' state.

The octets received since its last change to the `up' state.

The number of outgoing calls on this interface since its last change to the 'up' state.

The number of outgoing call failures on this interface since its last change to the 'up' state.

The number of incoming calls on this interface since its last change to the up state.

The number of incoming call failures on this interface since its last change to the up state.

The total link duration in seconds.

The total costs on this interface for all member links.

The total amount of octets transmitted.

The total amount of octets received.

The total number of outgoing calls.

The total number of outgoing call failures.

The total number of incoming calls.

The total number of incoming call failures.

The actual thoughput of the interface; updated every 5 seconds.

This object describes wether data compression is active for this interface. 42bis or Stac LZS compression algorithm can be enabled in the biboPPPTable. Enumeration: 'active': 2, 'inactive': 1.

Describes the measured interval between charging info elements received from the ISDN network.

The currently measured connection inactivity time (channel is silent).

The current charge on this interface as 1/1000 of the respective currency.

The total charge on this interface as 1/1000 of the respective currency.

The biboPPPLinkTable contains statistical information for each current PPP link on the system. Only the system can add or delete entries to this table. Creating entries: Entries are created by the system each time a new PPP interface is created in the biboPPPTable. Deleting entries: Entries are removed by the system when the corresponding PPP interface is removed.

Correlating PPP interface index.

Time when the link was established.

Direction of link, incoming(1) or outgoing(2). In case of permanent links, the meaning is dce(1) or dte(2). Enumeration: 'outgoing-dte': 2, 'incoming-dce': 1.

The bitwise ORed protocols successfully negotiated on this link; currently the following protocols are supported: tcp/ip(1), ipx(2), bridge(4), bpdu(8), x25(16). These protocol values are most likely to change in future software releases.

The actual state of each link in a bundle. The link is fully operational in the up(1) state, and not operational in the down(2) state. The starting(3) state is an inter- mediate state when the link is physically established but PPP or other link negotation has not finished yet. The loopbacked(4) state is entered when the PPP keepalive mechanism detects a loopbacked link. The dialing(5) state shows that a dialup link is in its link establishment phase, dialing. If there is no answer to the call, the link enters the retry-wait(6) state for biboPPPRetryTime seconds. After waiting that time either a call retry will occur, or the ifOperStatus will enter the blocked state, depending on the amount of retries already done (biboPPPLinkRetries) and the value of the biboPPPMaxRetries field. Enumeration: 'retry-wait': 6, 'up': 1, 'down': 2, 'loopbacked': 4, 'starting': 3, 'dialing': 5.

The costs for this link in units.

The amount of retries taken to establish the link.

The amount of keepalive packets sent on the link.

The amount of keepalive answer packets waiting for since the last occurance of an echo reply packet.

The underlying link device index.

The speed of the link.

The stack number of the dialup link, correlating to the isdnStkNumber field in the isdnCallTable.

The call type of the dialup link, correlating to the isdnCallType field in the isdnCallTable. Enumeration: 'outgoing': 2, 'undef': 3, 'incoming': 1.

The call reference of the dialup link, correlating to the isdnCallReference field in the isdnCallTable.

The costs for this link as 1/1000 of the respective currency.

.

Indicates the successful negotiation of the Link Quality Protocol (LQM). Enumeration: 'none': 1, 'negotiated': 2.

Address- and Protocol-Field compression. Enumeration: 'both': 4, 'none': 1, 'prot': 3, 'addr': 2.

Local LCP multilink endpoint discriminator.

Peer's LCP multilink endpoint discriminator.

The biboPPPIpAssignTable contains IP addresses used when dynamically assigning IP addresses; i.e. when the biboPPPIpAddress field is set to `dynamic'. Creating entries: Entries are created by assigning a value (IP address) to the biboPPPIpAssignAddress object. Deleting entries: An entry (address) can be removed by assigning the value `delete' to its biboPPPIpAssignState.

Pool of IP addresses for dynamic IP address assignment via IPCP. See the biboPPPIpAddress field for further explanation.

First IP address of this range.

If an entry is currently in use, the state is set to as- signed(1). Otherwise it is set to unused(2). You may also delete this entry by changing it to delete(3). Enumeration: 'unused': 1, 'assigned': 2, 'delete': 3.

Pool ID value.

Number of IP addresses that will be assigned starting from biboPPPIpAssignAddress. A range of 0 will disable this entry

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.

The name of the PPP profile. Three profiles are available. Enumeration: 'profile-1': 1, 'profile-3': 3, 'profile-2': 2.

The type of authentication used on the point-to-point link as described in RFC 1334. See biboPPPAuthentication for further details. Enumeration: 'pap': 2, 'both': 4, 'none': 1, 'ms-chap': 6, 'all': 7, 'chap': 3, 'ms-chapv2': 8.

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). Enumeration: 'both': 4, 'none': 1, 'radius-only': 5, 'outband': 3, 'inband': 2.

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. Enumeration: 'on': 2, 'off': 1.

Specifies the device to be used for PPP over Ethernet (PPPoE) according RFC 2516.

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. Enumeration: 'disabled': 1, 'enabled': 2, 'cbcp-optional': 3.

The pppLqmTable contains statistical information for each current PPP link on the system. Only the system can add or delete entries to this table. Creating entries: Entries are created by the system each time a new PPP link was established and LQM negotiated successful. Deleting entries: Entries are removed by the system when the corresponding PPP link is disconnected.

Correlating PPP interface index.

The call reference of the dialup link, correlating to the isdnCallReference field in the isdnCallTable.

The LQMReportingPeriod field indicates the maximum time in hundredths of seconds between transmission of Link Quality Reports (LQR). The peer may transmit packets at a faster rate than that which was negotiated.

Number of transmitted Link Quality Reports (LQR) on this link.

Number of transmitted Packets on this link.

Number of transmitted Octets on this link, including framing data.

Number of Link Quality Reports (LQR) received on this link.

Number of Packets reveived on this link.

Number of Octets reveived on this link, including framing data.

Number of Packets received on this link, but discarded.

Number of errorneous Packets received on this link.

Number of Link Quality Reports (LQR) transmitted by remote on this link.

Number of Packets transmitted by remote on this link.

Number of Octets transmitted by remote on this link, including framing data.

Number of Link Quality Reports (LQR) received by remote on this link.

Number of Packets reveived by remote on this link.

Number of Octets reveived by remote on this link, including framing data.

Number of Packets received by remote on this link, but discarded.

Number of errorneous Packets received by remote on this link.

Number of lost Link Quality Reports (LQR) transmitted on this link.

Number of lost Packets transmitted on this link.

Number of lost Octets transmitted on this link.

Number of lost Link Quality Reports (LQR) transmitted by remote on this link.

Number of lost Packets transmitted by remote on this link.

Number of lost Octets transmitted by remote on this link.

The pppIpUseTable contains dynamically assigned IP addresses.

assigned IP address

Unique IP address pool ID

Unique interface index

The remote authentication identification string.

If an IP address is currently assigned, the state of this entry is set to assigned(1). Otherwise, after disconnect, it is set to reserved(2) until the same peer reconnects or this entry expires (see pppIpInUseAge). Enumeration: 'assigned': 1, 'reserved': 2.

This object specifies the age of the entry after creation or after changing into state reserved(2). After expiration the IP address (see pppIpInUseAddress) is no longer reserved for peer specified by pppIpInUseIdent and this entry will be deleted.

The pppExtIfTable contains extended configuration and information related to the PPP interfaces on the system. Entries are optional for each interface and can be added or deleted by the user. Deleting entries: Entries are removed by setting an entry's pppExtIfBodMode object to 'delete'.

Correlating PPP interface index.

Enables bandwidth on demand (BOD) mode for leased line and dialup interfaces when setting to bod-active (3) respectively bod-passive (4) or backup only mode for leased line connections like X.21. When set to disabled (1), neither bandwidth on demand (as specified by the pppExtIfTable) or backup mode is enabled. Four modes (bap-active (5), bap-passive (6), bap-both(7) and bap-first (8)) are available for BAP (Bandwidth Allocation Protocol) support to specify wether BAP Call-Requests and BAP Callback-Requests should be initiated and/or accepted. Enumeration: 'bod-active': 3, 'bap-first': 9, 'bap-active': 5, 'bod-passive': 4, 'disabled': 1, 'bap-both': 8, 'backup': 2, 'bap-passive': 6, 'delete': 7.

The algorithm to use for weighting line utilization. Line utilization is determined by calculating the average load for each interface. When set to equal (1) all samples taken over the time interval (defined in pppExtIfInterval) will be given equal weight, when set to proportional (2) the weighting disproportional to the age of the sample. Enumeration: 'proportional': 2, 'equal': 1.

The time interval (in seconds) to use for sampling and calculating of the average throughput of the interface. See also: pppExtIfLoad.

The actual throughput (in percent) of the total bandwidth of this interface (load). This value is updated once every second.

The multilink PPP fragmentation mode. When set to proportional (1) packets will be divided into fragments proportional to the transmission rate of each link, when set to equal (2) packets will be divided into multiple equal fragments (equal to MlpFragSize) such that the number sent on each link is proportional to the transmission rate. When set to interleave (3), large datagrams will be fragmentated (maximum size determined by MlpFragSize) to reduce transmission delay of high-priority traffic on slower links. Enumeration: 'proportional': 1, 'equal': 2, 'interleave': 3.

The multilink PPP fragment size. If MlpFragmentation is set to proportional (1) this value specifies the minimum size of the fragment in bytes. If MlpFragmentation is set to equal (2) this value specifies the maximum fragment size in bytes.

The PPPoE (PPP over Ethernet, RFC 2516) service name which indicates the requested service during PPPoE discovery stage. Examples of the use of the service name are to indicate an ISP name or a class or a quality of service.

The PPPoE (PPP over Ethernet, RFC 2516) AC-Server name which determines the access concentrator during PPPoE discovery stage.

This variable defines the specification of shared secrets (encryption keys) between the sender and receiver of encrypted data. If set to static (1), the keys specified in 'pppExtIfEncTxKey' and 'pppExtIfEncRxKey' will be used, if set to authentication (2), the key derivation is based on PPP authentication via CHAP or MS-CHAP. Enumeration: 'authentication': 2, 'static': 1.

Static (encryption) key used for transmission of encrypted data via PPP. It's size depends on the used encryption algorithm and the corresponding key length, e.g. 'des_56' or 'blowfish_168'.

Static (decryption) key used for decryption of encrypted data received on PPP connections. It's size depends on the used encryption algorithm and the corresponding key length, e.g. 'des_56' or 'blowfish_168'.

Gear up threshold for invoking current bandwidth. The measured throughput (in percent of the total bandwidth) of this interface (see pppExtIfLoad) is compared with this value once per second. If exceeded longer than 5 seconds an additional B-channel will be requested.

Gear down threshold for decreasing current bandwidth. The expected throughput (in percent of the total bandwidth) of this interface (see pppExtIfLoad) after dropping a B-channel is compared with this threshold value once per second. If the needed bandwidth falls below this threshold longer than 10 seconds, exactly one B-channel will be dropped.

Upper threshold for the amount of data (in octets) waiting to be sent across the 9.6Kbit/sec D-channel. If exceeded, additional bandwidth will be invoked at once.

Lower threshold for the amount of data in bits per second to be sent across the 64Kbit/sec B-channel. If the measured throughput becomes smaller than this value over a period of pppExtIfGearDownPersistance seconds, the remaining B-channel will be dropped.

Gear up persistence interval for invoking current bandwidth. The measured throughput (in percent of the total bandwidth) of this interface (see pppExtIfLoad) is compared with the current value of the variable pppExtIfGearUpThreshold once per second. If exceeded longer than pppExtIfGearUpPersistance seconds an additional B-channel will be requested.

Gear down persistence interval for decreasing current bandwidth. The measured throughput (in percent of the total bandwidth) of this interface (see pppExtIfLoad) is compared with the current value of pppExtIfGearDownThreshold once per second. If exceeded longer than pppExtIfGearDownPersistance seconds, exactly one B-channel will be dropped.

This object contains the interface's nominal bandwidth in bits per second. Please note that this parameter may not represent the real available transmission rate. The current purpose is only informational for example for PPTP or PPPoE interfaces where no accurate information from the underlaying network is available.

Current time in seconds to wait before retrying a call when the smart retry algorithm is implemented.

Maximum time in seconds to wait before retrying a call when the smart retry algorithm is implemented. When set to zero this algorithm is disabled.

Determines size of the largest datagram which can be sent on the interface, specified in octets (see ifMtu). When set to zero (default), the value of the variable ifMtu depends on the received LCP MRU/MRRU option.

The maximum length for the PPP information field, including padding, but not including the protocol field, is termed the Maximum Receive Unit (MRU).

This object enables mutual PPP authentication between the peers. Enumeration: 'disabled': 1, 'enabled': 2.

The pppSessionTable contains statistical information for the PPP protocol. Only the system can add or delete entries to this table. Creating entries: Entries are created by the system each time a new PPP connection is created. Deleting entries: Entries are removed by the system when the corresponding PPP connection is terminated.

Correlating PPP interface index.

Indicates negotiation of Multilink PPP. Enumeration: 'none': 1, 'negotiated': 2.

Peer's MRU/MRRU LCP option.

Callback option inside LCP negotiation. Enumeration: 'none': 1, 'cbcp': 3, 'lcp': 2.

The negotiated PPP authentication protocol. Enumeration: 'pap': 2, 'none': 1, 'chap': 3, 'ms-chapv2': 5, 'ms-chapv1': 4.

The negotiated CCP compression mode. Enumeration: 'mppc': 4, 'none': 1, 'ms-stac': 3, 'stac': 2.

The negotiated CCP encryption mode. Enumeration: 'mppe-40': 2, 'triple-des-168': 5, 'none': 1, 'mppe-56': 7, 'mppev2-56': 9, 'des-56': 4, 'mppe-128': 3, 'blowfish-56': 11, 'mppev2-128': 10, 'blowfish-168': 6, 'mppev2-40': 8.

The negotiated Callback Control Protocol (CBCP) mode. Enumeration: 'no-callback': 2, 'none': 1, 'user-specified': 3, 'pre-specified': 4.

The negotiated (CBCP) callback delay in seconds.

The negotiated local IP Address.

The negotiated remote IP Address.

The negotiated first name server IP address.

The negotiated second name server IP address.

The negotiated first NetBIOS name server (WINS) IP address.

The negotiated second NetBIOS name server (WINS) IP address.

The negotiation of Van Jacobsen TCP/IP header compression option (IPCP). Enumeration: 'none': 1, 'negotiated': 2.

Unique IPX Node Id dynamically assigned the client.

The result of the BACP Favored-Peer negotiation. Enumeration: 'remote': 3, 'none': 1, 'local': 2.

The biboDialTable contains configuration information for incoming and outgoing ISDN telephone numbers. Creating entries: Entries are created by assigning a value to the biboDialIfIndex object. Deleting entries: An entry can be removed by assigning the value `delete' to its biboDialType object.

The correlating PPP interface index.

The dialup type can be set to plain isdn(1), isdn-spv(2) semi-permanent links used by the German 1TR6 D-channel protocol, or to delete(3) to delete a biboDialTable entry. The types ppp-callback(4) and ppp-negotiated(5) are used for the LCP callback option. Enumeration: 'isdn-spv': 2, 'x25-dialout': 6, 'ip': 7, 'ppp-callback': 4, 'ppp-negotiated': 5, 'x25': 8, 'isdn': 1, 'delete': 3.

The allowed dial direction is either incoming(1), outgoing(2), or both(3) calls. No call is ever set up when set to incoming(1). Incoming calls will not be identified when set to outoing(2). Furthermore, once PPP authentication succeeds and there is at least one incoming number defined but for which none matches, the call will not be accepted for security reasons. Enumeration: 'both': 3, 'outgoing': 2, 'incoming': 1.

The defined dialing number. Used for either dialing or comparing to incoming calls or both, depending on the content of the biboDialDirection field. The wildcards '*', '?', '[', ']', '{', '}' may be used.

The defined dial subaddress, if any. Also, see the biboDialNumber field.

The defined closed user group, if any. Also, see the biboDialNumber field.

The defined stack mask. Each value of IsdnStkNumber represents a bit in this bitmask. A mask of 0 disables dialup completely, while a mask of -1 enables dialup on all available ISDN stacks.

The screening indicator of the biboDialNumber. The biboDialScreening field can be used to gauge the `trustworthiness' of the biboDialNumber field. (See isdnCallScreening) Indicators are ordered from highest to lowest as follows: indicator: CPN assigned: verification: `network' by network none `user-verified' by user verification successful `user' by user none `user-failed' by user verification failed Set this field to `dont-care' to accept all calls. Otherwise calls are accepted only if the screening indicator matches or is higher than the set value. Enumeration: 'dont-care': 5, 'user-failed': 3, 'user-verified': 2, 'user': 1, 'network': 4.

The defined calling dial subaddress, if any. Also, see the biboDialNumber field.

The type of calling party subaddress. Enumeration: 'nsap': 1, 'reserved': 3, 'user-specified': 2.

The type of called party subaddress. Enumeration: 'nsap': 1, 'reserved': 3, 'user-specified': 2.