ELTEX-TUNNEL-MIB: View SNMP OID List / Download MIB

The MIB module for management of WiFi Tunnels, independent of the specific encapsulation scheme in use.

The (conceptual) table containing information on configured Wi-Fi tunnels. This table can be used to map a set of WiFi tunnel endpoints to the associated ifIndex value. It can also be used for row creation. Note that every row in the tunnelIfTable with a fixed IPv4 destination address should have a corresponding row in the tunnelWiFiConfigTable, regardless of whether it was created via SNMP. This table does not support IPv6.

An entry (conceptual row) containing the information on a particular configured tunnel.

The type of address in the corresponding tunnelWiFiConfigLocalAddress.

The address of the local endpoint of the Wi-Fi tunnel, or 0.0.0.0 if the device is free to choose any of its addresses at Wi-Fi tunnel establishment time.

The type of address in the corresponding tunnelWiFiConfigRemoteAddress.

The address of the remote endpoint of the Wi-Fi tunnel.

The encapsulation method used by the Wi-Fi tunnel.

An identifier used to distinguish between multiple Wi-Fi tunnels of the same encapsulation method, with the same endpoints. If the encapsulation protocol only allows one tunnel per set of endpoint addresses (such as for GRE or IP-in-IP), the value of this object is 1. For encapsulation methods (such as L2F) which allow multiple parallel tunnels, the manager is responsible for choosing any ID which does not conflict with an existing row, such as choosing a random number.

If the value of tunnelWiFiConfigStatus for this row is active, then this object contains the value of ifIndex corresponding to the Wi-Fi tunnel interface. A value of 0 is not legal in the active state, and means that the interface index has not yet been assigned.

The status of this row, by which new entries may be created, or old entries deleted from this table. The agent need not support setting this object to createAndWait or notInService since there are no other writable objects in this table, and writable objects in rows of corresponding tables such as the tunnelIfTable may be modified while this row is active. To create a row in this table for an encapsulation method which does not support multiple parallel tunnels with the same endpoints, the management station should simply use a tunnelWiFiConfigID of 1, and set tunnelWiFiConfigStatus to createAndGo. For encapsulation methods such as L2F which allow multiple parallel tunnels, the management station may select a pseudo-random number to use as the tunnelConfigID and set tunnelConfigStatus to createAndGo. In the event that this ID is already in use and an inconsistentValue is returned in response to the set operation, the management station should simply select a new pseudo-random number and retry the operation. Creating a row in this table will cause an interface index to be assigned by the agent in an implementation-dependent manner, and corresponding rows will be instantiated in the ifTable and the tunnelIfTable. The status of this row will become active as soon as the agent assigns the interface index, regardless of whether the interface is operationally up. Deleting a row in this table will likewise delete the corresponding row in the ifTable and in the tunnelIfTable.

Type of Wi-Fi tunnel: notConfigured(0), management(1), data(2). Enumeration: 'management': 1, 'data': 2, 'notConfigured': 0.

If an instance of this object has the value true, this tunnel is a template for create other tunnels and has ip address 0.0.0.0