DLINK-3100-SSH-MIB: View SNMP OID List / Download MIB
VENDOR: D-LINK
Home | MIB: DLINK-3100-SSH-MIB | |||
---|---|---|---|---|
Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
Object Name | OID | Type | Access | Info |
rlSsh | 1.3.6.1.4.1.171.10.94.89.89.78 |
The MIB module describes the private MIB for SSH supported by DLINK-3100's software and products. |
||
rlSshMibVersion | 1.3.6.1.4.1.171.10.94.89.89.78.1 | integer | read-only |
The MIB version. The current version is 2 |
rlSshServer | 1.3.6.1.4.1.171.10.94.89.89.78.2 | |||
rlSshServerHostPublicKeyTable | 1.3.6.1.4.1.171.10.94.89.89.78.2.1 | no-access |
This table contains the router's public key. Each row in this table contains a fragment of the key, in printable binhex format. There may be up to 160 characters in every fragment, and they are all combined to form one key. The key is generated by writing to rlSshServerRegenerateHostKey. To cause clients to connect to this router without printing warning messages (and also prevent active man-in-the-middle), the router's public key must printed out and inserted into the client's authorized_keys file |
|
1.3.6.1.4.1.171.10.94.89.89.78.2.1.1 | no-access |
The row definition for this table. |
||
rlSshServerHostPublicKeyAlgorithm | 1.3.6.1.4.1.171.10.94.89.89.78.2.1.1.1 | rlsshpublickeyalgorithm | read-only |
Identifies the type of public key to be displayed. |
rlSshServerHostPublicKeyFragmentId | 1.3.6.1.4.1.171.10.94.89.89.78.2.1.1.2 | unsigned32 | read-only |
Identifies the index of this fragment in the final key. All segments must be combined to form one big key. |
rlSshServerHostPublicKeyFragmentText | 1.3.6.1.4.1.171.10.94.89.89.78.2.1.1.3 | displaystring | read-only |
A part of the readable text entry for the server's public authorzation key. |
rlSshServerHostPublicKeyFingerprintTable | 1.3.6.1.4.1.171.10.94.89.89.78.2.2 | no-access |
This table contains the fingerprint for the router's public key. |
|
1.3.6.1.4.1.171.10.94.89.89.78.2.2.1 | no-access |
The row definition for this table. |
||
rlSshServerHostPublicKeyFingerprintAlgorithm | 1.3.6.1.4.1.171.10.94.89.89.78.2.2.1.1 | rlsshpublickeyalgorithm | read-only |
Identifies the type of public key to be displayed. |
rlSshServerHostPublicKeyFingerprintDigestFormat | 1.3.6.1.4.1.171.10.94.89.89.78.2.2.1.2 | rlsshpublickeydigestformat | read-only |
Format of the digest to be displayed (OpenSSH or SSH.com). |
rlSshServerHostPublicKeyFingerprint | 1.3.6.1.4.1.171.10.94.89.89.78.2.2.1.3 | displaystring | read-only |
SECSH format fingerprint of the server's public key. To prevent man in the middle attacks, users should make sure the ssh Server's fingerprint, as printed in the connection process, is similar to the one printed here. |
rlSshServerAuthorizedUsersPublicKeyTable | 1.3.6.1.4.1.171.10.94.89.89.78.2.3 | no-access |
This table contains public keys for all users who are authorized to access the router. For a user to be able to log in using SSH, the user name must appear in this table, and the user's public key must match the one found here. |
|
1.3.6.1.4.1.171.10.94.89.89.78.2.3.1 | no-access |
The row definition for this table. |
||
rlSshServerAuthorizedUserName | 1.3.6.1.4.1.171.10.94.89.89.78.2.3.1.1 | displaystring | read-write |
Name of the user who owns this public key. Both the user name and the key bytes must match before a user is authenticated using this key. |
rlSshServerAuthorizedUserPublicKeyFragmentId | 1.3.6.1.4.1.171.10.94.89.89.78.2.3.1.2 | unsigned32 | read-write |
Identifies the index of this fragment in the final key. All segments must be combined to form one big key. |
rlSshServerAuthorizedUserPublicKeyFragmentText | 1.3.6.1.4.1.171.10.94.89.89.78.2.3.1.3 | displaystring | read-write |
A part of the readable text entry for the user's public authorzation key. |
rlSshServerAuthorizedUserPublicKeyFragmentStatus | 1.3.6.1.4.1.171.10.94.89.89.78.2.3.1.4 | rowstatus | read-write |
Create or delete a fragment of the user's public key. A user is deleted if it has no remaining fragments. |
rlSshServerAuthorizedUsersPublicKeyFingerprintTable | 1.3.6.1.4.1.171.10.94.89.89.78.2.5 | no-access |
This table contains the fingerprints of the public keys for all users who are authorized to access the router. To prevent man in the middle attacks, users should make sure the user's fingerprint, as printed in the connection process, is similar to the one printed here. |
|
1.3.6.1.4.1.171.10.94.89.89.78.2.5.1 | no-access |
The row definition for this table. |
||
rlSshServerAuthorizedUserFingerprintName | 1.3.6.1.4.1.171.10.94.89.89.78.2.5.1.1 | displaystring | read-write |
Name of the user who owns this public key. Both the user name and the key bytes must match before a user is authenticated using this key. |
rlSshServerAuthorizedUserPublicKeyFingerprintAlgorithm | 1.3.6.1.4.1.171.10.94.89.89.78.2.5.1.2 | rlsshpublickeyalgorithm | read-only |
Identifies the type of public key to be displayed. |
rlSshServerAuthorizedUserPublicKeyFingerprintDigestFormat | 1.3.6.1.4.1.171.10.94.89.89.78.2.5.1.3 | rlsshpublickeydigestformat | read-only |
Format of the digest to be displayed (OpenSSH or SSH.com). |
rlSshServerAuthorizedUserPublicKeyFingerprint | 1.3.6.1.4.1.171.10.94.89.89.78.2.5.1.4 | displaystring | read-only |
SECSH format fingerprint of the user's public key. To prevent man in the middle attacks, users should make sure their ssh fingerprint, as printed in the connection process, is similar to the one printed here. |
rlSshServerSessionTable | 1.3.6.1.4.1.171.10.94.89.89.78.2.6 | no-access |
Each row in this table corresponds to an active SSH session with the server |
|
1.3.6.1.4.1.171.10.94.89.89.78.2.6.1 | no-access |
The row definition for this table. |
||
rlSshServerSessionIdentifier | 1.3.6.1.4.1.171.10.94.89.89.78.2.6.1.1 | unsigned32 | read-only |
Identifies the connection to which this row corresponds. |
rlSshServerSessionPeerAddress | 1.3.6.1.4.1.171.10.94.89.89.78.2.6.1.2 | ipaddress | read-only |
The network address of the remote host connected to the server. |
rlSshServerSessionPeerPort | 1.3.6.1.4.1.171.10.94.89.89.78.2.6.1.3 | unsigned32 | read-only |
The source network port of the remote host connected to the server. |
rlSshServerSessionPeerVersion | 1.3.6.1.4.1.171.10.94.89.89.78.2.6.1.4 | displaystring | read-only |
The client version of the remote host connected to the server. |
rlSshServerSessionUsername | 1.3.6.1.4.1.171.10.94.89.89.78.2.6.1.5 | displaystring | read-only |
SSH authenticated name of user connected to the server. |
rlSshServerSessionCipher | 1.3.6.1.4.1.171.10.94.89.89.78.2.6.1.6 | displaystring | read-only |
Data encryption cipher used in this connection. |
rlSshServerSessionHMAC | 1.3.6.1.4.1.171.10.94.89.89.78.2.6.1.7 | displaystring | read-only |
Message authentication code used in this connection. |
rlSshServerSessionInetTable | 1.3.6.1.4.1.171.10.94.89.89.78.2.7 | no-access |
Each row in this table corresponds to an active SSH session with the server |
|
1.3.6.1.4.1.171.10.94.89.89.78.2.7.1 | no-access |
The row definition for this table. |
||
rlSshServerSessionInetIdentifier | 1.3.6.1.4.1.171.10.94.89.89.78.2.7.1.1 | unsigned32 | read-only |
Identifies the connection to which this row corresponds. |
rlSshServerSessionInetPeerAddressType | 1.3.6.1.4.1.171.10.94.89.89.78.2.7.1.2 | inetaddresstype | read-only |
The network address of the remote host connected to the server. |
rlSshServerSessionInetPeerAddress | 1.3.6.1.4.1.171.10.94.89.89.78.2.7.1.3 | inetaddress | read-only |
The network address of the remote host connected to the server. |
rlSshServerSessionInetPeerPort | 1.3.6.1.4.1.171.10.94.89.89.78.2.7.1.4 | unsigned32 | read-only |
The source network port of the remote host connected to the server. |
rlSshServerSessionInetPeerVersion | 1.3.6.1.4.1.171.10.94.89.89.78.2.7.1.5 | displaystring | read-only |
The client version of the remote host connected to the server. |
rlSshServerSessionInetUsername | 1.3.6.1.4.1.171.10.94.89.89.78.2.7.1.6 | displaystring | read-only |
SSH authenticated name of user connected to the server. |
rlSshServerSessionInetCipher | 1.3.6.1.4.1.171.10.94.89.89.78.2.7.1.7 | displaystring | read-only |
Data encryption cipher used in this connection. |
rlSshServerSessionInetHMAC | 1.3.6.1.4.1.171.10.94.89.89.78.2.7.1.8 | displaystring | read-only |
Message authentication code used in this connection. |
rlSshServerPort | 1.3.6.1.4.1.171.10.94.89.89.78.2.101 | unsigned32 | read-write |
Specifies the TCP port used by the SSH 2 Server to listen for incoming connections. |
rlSshServerEnable | 1.3.6.1.4.1.171.10.94.89.89.78.2.102 | integer | read-write |
Enables listening for incoming SSH2 connections on the port defined in rlSshServerPort. Enumeration: 'enable': 1, 'disable': 2. |
rlSshServerEnablePublicKeyAuthentication | 1.3.6.1.4.1.171.10.94.89.89.78.2.103 | integer | read-write |
If PK authentication is enabled, incoming SSH connections are authenticated using public key authentication (using rlSshServerAuthorizedUsersPublicKeyTable), before authenticating using the router's standard AAA. If disabled, SSH connections are only authorized by the router's AAA component. Enumeration: 'enable': 1, 'disable': 2. |
rlSshServerRegenerateHostKey | 1.3.6.1.4.1.171.10.94.89.89.78.2.104 | rlsshpublickeyalgorithm | read-write |
Setting to a value other than none results in the Server (Host) Key being regenerated. The key size is host-specific. |
rlSshClient | 1.3.6.1.4.1.171.10.94.89.89.78.3 | |||
rlSshClientUserName | 1.3.6.1.4.1.171.10.94.89.89.78.3.1 | displaystring | read-write |
Specifies the default user name the ssh client will use when authenticating to a remote server. |
rlSshClientRegenerateSelfKey | 1.3.6.1.4.1.171.10.94.89.89.78.3.2 | rlsshpublickeyalgorithm | read-write |
Setting to a value other than none results in the client self key being regenerated. The key size is host-specific. |
rlSshClientSelfPublicKeyTable | 1.3.6.1.4.1.171.10.94.89.89.78.3.3 | no-access |
This table contains the router's client self public key. Each row in this table contains a fragment of the key, in printable binhex format. There may be up to 160 characters in every fragment, and they are all combined to form one key. The key is generated by writing to rlSshClientRegenerateSelfKey. To cause clients to connect to this router without printing warning messages (and also prevent active man-in-the-middle), the router's public key must printed out and inserted into the client's authorized_keys file |
|
1.3.6.1.4.1.171.10.94.89.89.78.3.3.1 | no-access |
The row definition for this table. |
||
rlSshClientSelfPublicKeyFragmentId | 1.3.6.1.4.1.171.10.94.89.89.78.3.3.1.1 | unsigned32 | read-only |
Identifies the index of this fragment in the final key. All segments must be combined to form one big key. |
rlSshClientSelfPublicKeyAlgorithm | 1.3.6.1.4.1.171.10.94.89.89.78.3.3.1.2 | rlsshpublickeyalgorithm | read-only |
Identifies the type of public key to be displayed. |
rlSshClientSelfPublicKeyFragmentText | 1.3.6.1.4.1.171.10.94.89.89.78.3.3.1.3 | displaystring | read-write |
A part of the readable text entry for the router's client public authorization key. |
rlSshClientSelfPublicKeyFingerprintTable | 1.3.6.1.4.1.171.10.94.89.89.78.3.4 | no-access |
This table contains the fingerprint for the client's self key. |
|
1.3.6.1.4.1.171.10.94.89.89.78.3.4.1 | no-access |
The row definition for this table. |
||
rlSshClientSelfPublicKeyFingerprintAlgorithm | 1.3.6.1.4.1.171.10.94.89.89.78.3.4.1.1 | rlsshpublickeyalgorithm | read-only |
Identifies the type of public key to be displayed. |
rlSshClientSelfPublicKeyFingerprintDigestFormat | 1.3.6.1.4.1.171.10.94.89.89.78.3.4.1.2 | rlsshpublickeydigestformat | read-only |
Format of the digest to be displayed (OpenSSH or SSH.com). |
rlSshClientSelfPublicKeyFingerprint | 1.3.6.1.4.1.171.10.94.89.89.78.3.4.1.3 | displaystring | read-only |
SECSH format fingerprint of the client's self key. To prevent man in the middle attacks, users should make sure the ssh Server's fingerprint, as printed in the connection process, is similar to the one printed here. |