This object contains configuration and status for the WireGuard subsystem. The WireGuard subsystem is used to create secure tunnels between devices using the WireGuard protocol. {{numentries}} {{numentries}} WireGuard Tunnel table, models the WireGuard Tunnel instance and represents the entry point and exit point of the tunnel in relation to the WAN interface. A {{object}} object has one or more {{object|Interface}} objects that further define the sessions or flows within the tunnel. Enables or disables the tunnel. The current operational state of the tunnel. The private key for this WireGuard tunnel. The public key for this WireGuard tunnel, corresponding to the {{param|PrivateKey}}. The port on which this WireGuard tunnel will listen for incoming connections. If set to 0, a random port will be chosen by the device. Each element represents a reference to the peers associated with this {{object}} entry. Statistics for this WireGuard tunnel, i.e. all traffic that has passed through the tunnel. The device MUST reset the tunnel's Stats parameters (unless otherwise stated in individual object or parameter descriptions) either when the tunnel becomes operationally down due to a previous administrative down (i.e., Status parameter transitions to a disabled state after the tunnel has been disabled) or when the tunnel becomes administratively up (i.e. the Enable parameter transitioned from {{false}} to {{true}}). The total number of {{units}} sent by the tunnel. The total number of {{units}} received by the tunnel. The total number of {{units}} sent by the tunnel. The total number of {{units}} received by the tunnel. The total number of {{units}} discarded by the tunnel due to any error. This can include packets dropped due to a lack of transmit buffers. The total number of {{units}} received by the tunnel that contained errors preventing them from being delivered to a higher-layer protocol. WireGuard Interface table (a stackable interface object as described in {{bibref|TR-181i2|Section 4.2}}). The {{object}} object provides a way to discriminate how sessions or flows are encapsulated within the WireGuard Tunnel. In addition the {{object}} object represents the entry point and exit point of the tunnel in relation to the LAN interface. Compared to other tunnel protocols, WireGuard does not have a concept of multiple interfaces within a tunnel. Therefore, a WireGuard Tunnel will only have one {{object}} instance. WireGuard Peer table, an entry in this table represents a WireGuard peer. Enables or disables this Peer configuration. Public key of the peer. The pre-shared key for this WireGuard Peer. When {{empty}} is provided, no pre-shared key is used. Each item represents an IPv4/v6 subnets in CIDR notation from which incoming traffic is allowed and to which outgoing traffic is directed for this peer. '0.0.0.0/0' maybe specified for matching all IPv4 addresses and '::/0' for matching all IPv6 addresses. When {{empty}} is provided, no traffic is routed to this peer. The remote network address (IP or hostname) of the peer. {{empty}} indicates that the endpoint address is not used. The UDP port of the remote peer. A value of `-1` indicates that the endpoint port is not used. An interval in {{units}} to send an authenticated empty packet to the peer. This is useful for keeping NAT mappings alive. A value of `0` disables this feature. The amount of time in {{units}} since the last handshake was sent with this peer.