Logical object. This object models several Logical interface objects, each representing a different stack layer, including: {{object|Interface}}. {{object|Interface}} is a logical interface which can point to other stackable interface layers. The intention of the logical interface is to simplify the configuration management of individual {{bibref|TR-181i2}} services. Instead of configuring the individual network services with a physical interface and deal with reconfiguration problems that may arise from switching between WAN interfaces. The intention is that the network services are configured with a logical interface and that this configuration stays unchanged during the switching between WAN interfaces. The software service (For example a WAN mode manager.) responsible for handling the WAN interface changes must then only care about rewriting the LowerLayers parameter of the Logical Interface Objects. Logical interface table (a stackable interface object as described in {{bibref|TR-181i2|Section 4.2}}). This table models only logical interfaces. The textual name of the logical interface as assigned by a static configuration file or dynamically by a controller. This information SHOULD be mirrored or aggregated from the active underlying interfaces. TUN (network TUNnel) virtual interface container object. TUN interfaces are Layer 3 virtual network devices that operate at the IP packet level. They are commonly used for VPN implementations, IP tunneling, and network virtualization scenarios where applications need to handle IP packets directly without dealing with Layer 2 Ethernet framing. {{numentries}} TUN virtual interface table (a stackable interface object as described in {{bibref|TR-181i2|Section 4.2}}). Each entry represents a Layer 3 virtual network interface that handles IP packets. TAP (network tap) virtual interface container object. TAP interfaces are Layer 2 virtual network devices that operate at the Ethernet frame level. They simulate a complete Ethernet adapter and are commonly used for network bridging, virtual machine networking, and scenarios where applications need full access to Ethernet frames including Layer 2 protocols. {{numentries}} TAP virtual interface table (a stackable interface object as described in {{bibref|TR-181i2|Section 4.2}}). Each entry represents a Layer 2 virtual network interface that handles Ethernet frames. Creates a network TUN virtual interface. This command is primarily used to allow a host system to create the TUN interface on behalf of a sandboxed or containerized application that lacks the necessary privileges to do so itself. An open file descriptor for the newly created TUN interface. Packets can be read from and written to this descriptor. The path reference of the newly created TUN interface instance. Creates a network TAP virtual interface. This command is primarily used to allow the host system to create the TAP interface on behalf of a sandboxed or containerized application that lacks the necessary privileges to do so itself. An open file descriptor for the newly created TAP interface. Packets can be read from and written to this descriptor. The path reference of the newly created TAP interface instance. TUN interfaces are typically created dynamically via the {{command|#.CreateInterface()}} command and can be deleted via the {{command|Delete()}} command. Deletes this network TUN virtual interface. This command is primarily used to allow a host system to delete the TUN interface on behalf of a sandboxed or containerized application that lacks the necessary privileges to do so itself. TAP interfaces are typically created dynamically via the {{command|#.CreateInterface()}} command and can be deleted via the {{command|Delete()}} command. Deletes this network TAP virtual interface. This command is primarily used to allow a host system to delete the TAP interface on behalf of a sandboxed or containerized application that lacks the necessary privileges to do so itself.