OID reference
1.3.6.1.4.1.3955.2.4.1.1.4
Select the local LAN user(s) behind the router that can use this VPN tunnel. This may be a single IP address, a Sub-network or a range of addresses. Notice that the Local Secure Group must match the other router's Remote Secure Group.
Identification
{1 3 6 1 4 1 3955 2 4 1 1 4}
| Value | Name |
|---|---|
| 0 | ip |
| 1 | subnet |
| 2 | range |
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In LINKSYS-MODEL-MIB, the row index vpnTunnelIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.3955.2.4.1.1.4.<vpnTunnelIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
Published row index: vpnTunnelIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.3955.2.4.1.1.4
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
vpnLocalIdType OBJECT-TYPE
SYNTAX INTEGER { ip(0), subnet(1), range(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Select the local LAN user(s) behind the router
that can use this VPN tunnel. This may be a single
IP address, a Sub-network or a range of addresses.
Notice that the Local Secure Group must match the
other router's Remote Secure Group."
::= { vpnIpsecEntry 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Select the local LAN user(s) behind the router that can use this VPN tunnel. This may be a single IP address, a Sub-network or a range of addresses. Notice that the Local Secure Group must match the other router's Remote Secure Group.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: vpnLocalIdType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vpnLocalIdType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"ip",
"(",
"0",
")",
",",
"subnet",
"(",
"1",
")",
",",
"range",
"(",
"2",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Select the local LAN user(s) behind the router that can use this VPN tunnel. This may be a single IP address, a Sub-network or a range of addresses. Notice that the Local Secure Group must match the other router's Remote Secure Group.\"",
"::=",
"{",
"vpnIpsecEntry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"ip",
0
],
[
"subnet",
1
],
[
"range",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Select the local LAN user(s) behind the router that can use this VPN tunnel. This may be a single IP address, a Sub-network or a range of addresses. Notice that the Local Secure Group must match the other router's Remote Secure Group."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: LINKSYS-MODEL-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises', 'IpAddress'], 'RFC1213-MIB': ['DisplayString', 'PhysAddress']}Related source files and packages:
Registration