Lines Matching full:interface

34 Sub-commands that take an INTERFACE must be passed a WireGuard interface.
39 \fBshow\fP { \fI<interface>\fP | \fIall\fP | \fIinterfaces\fP } [\fIpublic-key\fP | \fIprivate-key\…
40 Shows current WireGuard configuration and runtime information of specified \fI<interface>\fP.
41 If no \fI<interface>\fP is specified, \fI<interface>\fP defaults to \fIall\fP.
43 one per line, and quits. If no options are given after the interface
48 is the interface name. If \fPdump\fP is specified, then several lines are printed;
54 \fBshowconf\fP \fI<interface>\fP
55 Shows the current configuration of \fI<interface>\fP in the format described
58 \fBset\fP \fI<interface>\fP [\fIlisten-port\fP \fI<port>\fP] [\fIfwmark\fP \fI<fwmark>\fP] [\fIpriv…
59 Sets configuration values for the specified \fI<interface>\fP. Multiple
63 interface comes up. Both \fIprivate-key\fP and \fIpreshared-key\fP must
84 interface very rarely sends traffic, but it might at anytime receive traffic
85 from a peer, and it is behind NAT, the interface might benefit from having a
91 \fBsetconf\fP \fI<interface>\fP \fI<configuration-filename>\fP
92 Sets the current configuration of \fI<interface>\fP to the contents of
96 \fBaddconf\fP \fI<interface>\fP \fI<configuration-filename>\fP
99 to the current configuration of \fI<interface>\fP.
101 \fBsyncconf\fP \fI<interface>\fP \fI<configuration-filename>\fP
104 file and the interface. This is much less efficient than \fBsetconf\fP,
133 -- \fIInterface\fP and \fIPeer\fP. Multiple \fIPeer\fP sections may be specified, but
134 only one \fIInterface\fP section may be specified.
137 The \fIInterface\fP section may contain the following fields:
172 stateful firewall or NAT mapping valid persistently. For example, if the interface
174 and it is behind NAT, the interface might benefit from having a persistent keepalive
183     [Interface]
228 on a per-interface basis by using