

| +- RouterStatusEntryBridgeV2 - Entry for a bridge flavored v2 document |- RouterStatusEntryV2 - Entry for a network status v2 document 20 correspond to the TX statistics, in Byte, of LAN, WAN1, and WAN2, respectively.RouterStatusEntry - Common parent for router status entries You can also SNMP Get ifInOctects (.1.3.6.1.2.1.2.2.1.10.19) to obtain the RX bytes of WAN1. 20 correspond to the RX statistics, in Byte, of LAN, WAN1, and WAN2 (linked down), respectively.

You can also directly SNMP Get ifOperStatus.19 (.1.3.6.1.2.1.2.2.1.8.19) to obtain the link status of WAN1. As shown in the figure below, WAN1 is linked up, WAN2 is linked down. You already know that 17, 19, and 20 corresponds to LAN, WAN1, and WAN2, respectively. If you are using a router with more WAN ports, you can check the VLAN ID of each port, then you will know the correspondence. Then “ifDescr.19 = eth0.10” indicates the children OID for WAN1 is 19, and that for WAN2 is 20. If you go to the router page – Network – VLAN, you will find the VLAN IDs of WAN1 and WAN2 are 10 and 20, respectively. Among them, “ifDescr.17 = br-lan” indicates that 17 is the children OID for LAN. Most of the interfaces are for internal communication, and no need to be concerned. The OIDs of the dual-wan router is obtained via the tool named Snmpwalk, as shown below. SNMP Walk ifDescr (.1.3.6.1.2.1.2.2.1.2) to display the children's OIDs of the interfaces. To check the link status and traffic statistics, the OID ifEntry (.1.3.6.1.2.1.2.2.1) and its children OIDs are used.ġ.Check the children's OID for WAN or LAN interfaces.

TP-Link SMB routers support SNMP with public OIDs.
