]> git.proxmox.com Git - systemd.git/blame - man/systemd.network.html
projects / systemd.git / blame
? search:
summary | shortlog | log | commit | commitdiff | tree
blob | blame (incremental) | history | HEAD
Imported Upstream version 219
[systemd.git] / man / systemd.network.html
CommitLineData
60f067b4
JS		 1<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>systemd.network</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><style>
2 a.headerlink {
3 color: #c60f0f;
4 font-size: 0.8em;
5 padding: 0 4px 0 4px;
6 text-decoration: none;
7 visibility: hidden;
8 }
9
10 a.headerlink:hover {
11 background-color: #c60f0f;
12 color: white;
13 }
14
15 h1:hover > a.headerlink, h2:hover > a.headerlink, h3:hover > a.headerlink, dt:hover > a.headerlink {
16 visibility: visible;
17 }
18 </style><a href="index.html">Index </a>·
19 <a href="systemd.directives.html">Directives </a>·
20 <a href="../python-systemd/index.html">Python </a>·
21 <a href="../libudev/index.html">libudev </a>·
e735f4d4
MP		 22 <a href="../libudev/index.html">gudev </a><span style="float:right">systemd 219</span><hr><div class="refentry"><a name="systemd.network"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>systemd.network — Network configuration</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename"><em class="replaceable"><code>network</code></em>.network</code></p></div><div class="refsect1"><a name="idm140604915826704"></a><h2 id="Description">Description<a class="headerlink" title="Permalink to this headline" href="#Description">¶</a></h2><p>Network setup is performed by
23 <a href="systemd-networkd.html"><span class="citerefentry"><span class="refentrytitle">systemd-networkd</span>(8)</span></a>.
24 </p><p>Network files must have the extension
25 <code class="filename">.network</code>; other extensions are ignored.
26 Networks are applied to links whenever the links appear.</p><p>The <code class="filename">.network</code> files are read from the
27 files located in the system network directory
28 <code class="filename">/usr/lib/systemd/network</code>, the volatile
29 runtime network directory
30 <code class="filename">/run/systemd/network</code> and the local
31 administration network directory
32 <code class="filename">/etc/systemd/network</code>. All configuration files
33 are collectively sorted and processed in lexical order, regardless
34 of the directories in which they live. However, files with
35 identical filenames replace each other. Files in
36 <code class="filename">/etc</code> have the highest priority, files in
37 <code class="filename">/run</code> take precedence over files with the same
38 name in <code class="filename">/usr/lib</code>. This can be used to
39 override a system-supplied configuration file with a local file if
40 needed; a symlink in <code class="filename">/etc</code> with the same name
41 as a configuration file in <code class="filename">/usr/lib</code>, pointing
42 to <code class="filename">/dev/null</code>, disables the configuration file
43 entirely.</p></div><div class="refsect1"><a name="idm140604915693056"></a><h2 id="[Match] Section Options">[Match] Section Options<a class="headerlink" title="Permalink to this headline" href="#%5BMatch%5D%20Section%20Options">¶</a></h2><p>The network file contains a "<code class="literal">[Match]</code>"
44 section, which determines if a given network file may be applied
45 to a given device; and a "<code class="literal">[Network]</code>" section
46 specifying how the device should be configured. The first (in
47 lexical order) of the network files that matches a given device
48 is applied.</p><p>A network file is said to match a device if each of the
49 entries in the "<code class="literal">[Match]</code>" section matches, or if
50 the section is empty. The following keys are accepted:</p><div class="variablelist"><dl class="variablelist"><dt id="MACAddress="><span class="term"><code class="varname">MACAddress=</code></span><a class="headerlink" title="Permalink to this term" href="#MACAddress=">¶</a></dt><dd><p>The hardware address.</p></dd><dt id="Path="><span class="term"><code class="varname">Path=</code></span><a class="headerlink" title="Permalink to this term" href="#Path=">¶</a></dt><dd><p>A whitespace-separated list of shell-style globs
51 matching the persistent path, as exposed by the udev
52 property "<code class="literal">ID_PATH</code>".</p></dd><dt id="Driver="><span class="term"><code class="varname">Driver=</code></span><a class="headerlink" title="Permalink to this term" href="#Driver=">¶</a></dt><dd><p>A whitespace-separated list of shell-style globs
53 matching the driver currently bound to the device, as
54 exposed by the udev property "<code class="literal">DRIVER</code>"
55 of its parent device, or if that is not set the driver
56 as exposed by "<code class="literal">ethtool -i</code>" of the
57 device itself.</p></dd><dt id="Type="><span class="term"><code class="varname">Type=</code></span><a class="headerlink" title="Permalink to this term" href="#Type=">¶</a></dt><dd><p>A whitespace-separated list of shell-style globs
58 matching the device type, as exposed by the udev property
59 "<code class="literal">DEVTYPE</code>".</p></dd><dt id="Name="><span class="term"><code class="varname">Name=</code></span><a class="headerlink" title="Permalink to this term" href="#Name=">¶</a></dt><dd><p>A whitespace-separated list of shell-style globs
60 matching the device name, as exposed by the udev property
61 "<code class="literal">INTERFACE</code>".</p></dd><dt id="Host="><span class="term"><code class="varname">Host=</code></span><a class="headerlink" title="Permalink to this term" href="#Host=">¶</a></dt><dd><p>Matches against the hostname or machine ID of the
62 host. See "<code class="literal">ConditionHost=</code>" in
63 <a href="systemd.unit.html"><span class="citerefentry"><span class="refentrytitle">systemd.unit</span>(5)</span></a>
64 for details.
65 </p></dd><dt id="Virtualization="><span class="term"><code class="varname">Virtualization=</code></span><a class="headerlink" title="Permalink to this term" href="#Virtualization=">¶</a></dt><dd><p>Checks whether the system is executed in a virtualized
66 environment and optionally test whether it is a specific
67 implementation. See "<code class="literal">ConditionVirtualization=</code>" in
68 <a href="systemd.unit.html"><span class="citerefentry"><span class="refentrytitle">systemd.unit</span>(5)</span></a>
69 for details.
70 </p></dd><dt id="KernelCommandLine="><span class="term"><code class="varname">KernelCommandLine=</code></span><a class="headerlink" title="Permalink to this term" href="#KernelCommandLine=">¶</a></dt><dd><p>Checks whether a specific kernel command line option is
71 set (or if prefixed with the exclamation mark unset). See
72 "<code class="literal">ConditionKernelCommandLine=</code>" in
73 <a href="systemd.unit.html"><span class="citerefentry"><span class="refentrytitle">systemd.unit</span>(5)</span></a>
74 for details.
75 </p></dd><dt id="Architecture="><span class="term"><code class="varname">Architecture=</code></span><a class="headerlink" title="Permalink to this term" href="#Architecture=">¶</a></dt><dd><p>Checks whether the system is running on a specific
76 architecture. See "<code class="literal">ConditionArchitecture=</code>" in
77 <a href="systemd.unit.html"><span class="citerefentry"><span class="refentrytitle">systemd.unit</span>(5)</span></a>
78 for details.
79 </p></dd></dl></div></div><div class="refsect1"><a name="idm140604915854128"></a><h2 id="[Link] Section Options">[Link] Section Options<a class="headerlink" title="Permalink to this headline" href="#%5BLink%5D%20Section%20Options">¶</a></h2><p> The "<code class="literal">[Link]</code>" section accepts the following keys:</p><div class="variablelist"><dl class="variablelist"><dt id="MACAddress="><span class="term"><code class="varname">MACAddress=</code></span><a class="headerlink" title="Permalink to this term" href="#MACAddress=">¶</a></dt><dd><p>The hardware address.</p></dd><dt id="MTUBytes="><span class="term"><code class="varname">MTUBytes=</code></span><a class="headerlink" title="Permalink to this term" href="#MTUBytes=">¶</a></dt><dd><p>The maximum transmission unit in bytes to set for the
80 device. The usual suffixes K, M, G, are supported and are
81 understood to the base of 1024.</p></dd></dl></div></div><div class="refsect1"><a name="idm140604915847920"></a><h2 id="[Network] Section Options">[Network] Section Options<a class="headerlink" title="Permalink to this headline" href="#%5BNetwork%5D%20Section%20Options">¶</a></h2><p>The "<code class="literal">[Network]</code>" section accepts the following keys:</p><div class="variablelist"><dl class="variablelist"><dt id="Description="><span class="term"><code class="varname">Description=</code></span><a class="headerlink" title="Permalink to this term" href="#Description=">¶</a></dt><dd><p>A description of the device. This is only used for
82 presentation purposes.</p></dd><dt id="DHCP="><span class="term"><code class="varname">DHCP=</code></span><a class="headerlink" title="Permalink to this term" href="#DHCP=">¶</a></dt><dd><p>Enables DHCPv4 and/or DHCPv6 support. Accepts
83 "<code class="literal">yes</code>", "<code class="literal">no</code>",
84 "<code class="literal">ipv4</code>", or "<code class="literal">ipv6</code>".</p></dd><dt id="DHCPServer="><span class="term"><code class="varname">DHCPServer=</code></span><a class="headerlink" title="Permalink to this term" href="#DHCPServer=">¶</a></dt><dd><p>A boolean. Enables a basic DHCPv4 server on the
85 device. Mostly useful for handing out leases to container
86 instances.</p></dd><dt id="LinkLocalAddressing="><span class="term"><code class="varname">LinkLocalAddressing=</code></span><a class="headerlink" title="Permalink to this term" href="#LinkLocalAddressing=">¶</a></dt><dd><p>Enables link-local address autoconfiguration. Accepts
87 "<code class="literal">yes</code>", "<code class="literal">no</code>",
88 "<code class="literal">ipv4</code>", or "<code class="literal">ipv6</code>". Defaults to
89 "<code class="literal">ipv6</code>".</p></dd><dt id="IPv4LLRoute="><span class="term"><code class="varname">IPv4LLRoute=</code></span><a class="headerlink" title="Permalink to this term" href="#IPv4LLRoute=">¶</a></dt><dd><p>A boolean. When true, sets up the route needed for
90 non-IPv4LL hosts to communicate with IPv4LL-only hosts. Defaults
91 to false.
92 </p></dd><dt id="IPv6Token="><span class="term"><code class="varname">IPv6Token=</code></span><a class="headerlink" title="Permalink to this term" href="#IPv6Token=">¶</a></dt><dd><p>An IPv6 address with the top 64 bits unset. When set, indicates the
93 64 bits interface part of SLAAC IPv6 addresses for this link. By default
94 it is autogenerated.</p></dd><dt id="LLMNR="><span class="term"><code class="varname">LLMNR=</code></span><a class="headerlink" title="Permalink to this term" href="#LLMNR=">¶</a></dt><dd><p>A boolean or "<code class="literal">resolve</code>". When true, enables
95 Link-Local Multicast Name Resolution on the link, when set to
96 "<code class="literal">resolve</code>" only resolution is enabled, but not
97 announcement. Defaults to true.</p></dd><dt id="LLDP="><span class="term"><code class="varname">LLDP=</code></span><a class="headerlink" title="Permalink to this term" href="#LLDP=">¶</a></dt><dd><p>A boolean. When true, enables LLDP link receive support.
98 </p></dd><dt id="Address="><span class="term"><code class="varname">Address=</code></span><a class="headerlink" title="Permalink to this term" href="#Address=">¶</a></dt><dd><p>A static IPv4 or IPv6 address and its prefix length,
99 separated by a "<code class="literal">/</code>" character. Specify
100 this key more than once to configure several addresses.
101 The format of the address must be as described in
102 <a href="inet_pton.html"><span class="citerefentry"><span class="refentrytitle">inet_pton</span>(3)</span></a>.
103 This is a short-hand for an [Address] section only
104 containing an Address key (see below). This option may be
105 specified more than once.
106 </p><p>If the specified address is 0.0.0.0 (for IPv4) or
107 [::] (for IPv6), a new address range of the requested size
108 is automatically allocated from a system-wide pool of
109 unused ranges. The allocated range is checked against all
110 current network interfaces and all known network
111 configuration files to avoid address range conflicts. The
112 default system-wide pool consists of 192.168.0.0/16,
113 172.16.0.0/12 and 10.0.0.0/8 for IPv4, and fc00::/7 for
114 IPv6. This functionality is useful to manage a large
115 number of dynamically created network interfaces with the
116 same network configuration and automatic address range
117 assignment.</p></dd><dt id="Gateway="><span class="term"><code class="varname">Gateway=</code></span><a class="headerlink" title="Permalink to this term" href="#Gateway=">¶</a></dt><dd><p>The gateway address, which must be in the format
118 described in
119 <a href="inet_pton.html"><span class="citerefentry"><span class="refentrytitle">inet_pton</span>(3)</span></a>.
120 This is a short-hand for a [Route] section only containing
121 a Gateway key. This option may be specified more than
122 once.</p></dd><dt id="DNS="><span class="term"><code class="varname">DNS=</code></span><a class="headerlink" title="Permalink to this term" href="#DNS=">¶</a></dt><dd><p>A DNS server address, which must be in the format
123 described in
124 <a href="inet_pton.html"><span class="citerefentry"><span class="refentrytitle">inet_pton</span>(3)</span></a>.
125 This option may be specified more than once.</p></dd><dt id="Domains="><span class="term"><code class="varname">Domains=</code></span><a class="headerlink" title="Permalink to this term" href="#Domains=">¶</a></dt><dd><p>The domains used for DNS resolution over this link.</p></dd><dt id="NTP="><span class="term"><code class="varname">NTP=</code></span><a class="headerlink" title="Permalink to this term" href="#NTP=">¶</a></dt><dd><p>An NTP server address. This option may be specified more than once.</p></dd><dt id="IPForward="><span class="term"><code class="varname">IPForward=</code></span><a class="headerlink" title="Permalink to this term" href="#IPForward=">¶</a></dt><dd><p>Configures IP forwarding for the network
126 interface. If enabled incoming packets on the network
127 interface will be forwarded to other interfaces according to
128 the routing table. Takes either a boolean argument, or the
129 values "<code class="literal">ipv4</code>" or "<code class="literal">ipv6</code>",
130 which only enables IP forwarding for the specified address
131 family.</p></dd><dt id="IPMasquerade="><span class="term"><code class="varname">IPMasquerade=</code></span><a class="headerlink" title="Permalink to this term" href="#IPMasquerade=">¶</a></dt><dd><p>Configures IP masquerading for the network
132 interface. If enabled packets forwarded from the network
133 interface will be appear as coming from the local host.
134 Takes a boolean argument. Implies
135 <code class="varname">IPForward=yes</code>.</p></dd><dt id="Bridge="><span class="term"><code class="varname">Bridge=</code></span><a class="headerlink" title="Permalink to this term" href="#Bridge=">¶</a></dt><dd><p>The name of the bridge to add the link to.</p></dd><dt id="Bond="><span class="term"><code class="varname">Bond=</code></span><a class="headerlink" title="Permalink to this term" href="#Bond=">¶</a></dt><dd><p>The name of the bond to add the link to.</p></dd><dt id="VLAN="><span class="term"><code class="varname">VLAN=</code></span><a class="headerlink" title="Permalink to this term" href="#VLAN=">¶</a></dt><dd><p>The name of a VLAN to create on the link. This
136 option may be specified more than once.</p></dd><dt id="MACVLAN="><span class="term"><code class="varname">MACVLAN=</code></span><a class="headerlink" title="Permalink to this term" href="#MACVLAN=">¶</a></dt><dd><p>The name of a MACVLAN to create on the link. This
137 option may be specified more than once.</p></dd><dt id="VXLAN="><span class="term"><code class="varname">VXLAN=</code></span><a class="headerlink" title="Permalink to this term" href="#VXLAN=">¶</a></dt><dd><p>The name of a VXLAN to create on the link. This
138 option may be specified more than once.</p></dd><dt id="Tunnel="><span class="term"><code class="varname">Tunnel=</code></span><a class="headerlink" title="Permalink to this term" href="#Tunnel=">¶</a></dt><dd><p>The name of a Tunnel to create on the link. This
139 option may be specified more than once.</p></dd></dl></div></div><div class="refsect1"><a name="idm140604910876848"></a><h2 id="[Address] Section Options">[Address] Section Options<a class="headerlink" title="Permalink to this headline" href="#%5BAddress%5D%20Section%20Options">¶</a></h2><p>An "<code class="literal">[Address]</code>" section accepts the
140 following keys. Specify several "<code class="literal">[Address]</code>"
141 sections to configure several addresses.</p><div class="variablelist"><dl class="variablelist"><dt id="Address="><span class="term"><code class="varname">Address=</code></span><a class="headerlink" title="Permalink to this term" href="#Address=">¶</a></dt><dd><p>As in the "<code class="literal">[Network]</code>" section. This
142 key is mandatory.</p></dd><dt id="Peer="><span class="term"><code class="varname">Peer=</code></span><a class="headerlink" title="Permalink to this term" href="#Peer=">¶</a></dt><dd><p>The peer address in a point-to-point connection.
143 Accepts the same format as the "<code class="literal">Address</code>"
144 key.</p></dd><dt id="Broadcast="><span class="term"><code class="varname">Broadcast=</code></span><a class="headerlink" title="Permalink to this term" href="#Broadcast=">¶</a></dt><dd><p>The broadcast address, which must be in the format
145 described in
146 <a href="inet_pton.html"><span class="citerefentry"><span class="refentrytitle">inet_pton</span>(3)</span></a>.
147 This key only applies to IPv4 addresses. If it is not
148 given, it is derived from the "<code class="literal">Address</code>"
149 key.</p></dd><dt id="Label="><span class="term"><code class="varname">Label=</code></span><a class="headerlink" title="Permalink to this term" href="#Label=">¶</a></dt><dd><p>An address label.</p></dd></dl></div></div><div class="refsect1"><a name="idm140604910864176"></a><h2 id="[Route] Section Options">[Route] Section Options<a class="headerlink" title="Permalink to this headline" href="#%5BRoute%5D%20Section%20Options">¶</a></h2><p>The "<code class="literal">[Route]</code>" section accepts the
150 following keys. Specify several "<code class="literal">[Route]</code>"
151 sections to configure several routes.</p><div class="variablelist"><dl class="variablelist"><dt id="Gateway="><span class="term"><code class="varname">Gateway=</code></span><a class="headerlink" title="Permalink to this term" href="#Gateway=">¶</a></dt><dd><p>As in the "<code class="literal">[Network]</code>" section.</p></dd><dt id="Destination="><span class="term"><code class="varname">Destination=</code></span><a class="headerlink" title="Permalink to this term" href="#Destination=">¶</a></dt><dd><p>The destination prefix of the route. Possibly
152 followed by a slash and the prefixlength. If omitted, a
153 full-length host route is assumed.</p></dd><dt id="Source="><span class="term"><code class="varname">Source=</code></span><a class="headerlink" title="Permalink to this term" href="#Source=">¶</a></dt><dd><p>The source prefix of the route. Possibly followed by
154 a slash and the prefixlength. If omitted, a full-length
155 host route is assumed.</p></dd><dt id="Metric="><span class="term"><code class="varname">Metric=</code></span><a class="headerlink" title="Permalink to this term" href="#Metric=">¶</a></dt><dd><p>The metric of the route. An unsigned integer</p></dd><dt id="Scope="><span class="term"><code class="varname">Scope=</code></span><a class="headerlink" title="Permalink to this term" href="#Scope=">¶</a></dt><dd><p>The scope of the route. One of the values "<code class="literal">global</code>",
156 "<code class="literal">link</code>" or "<code class="literal">host</code>". Defaults to
157 "<code class="literal">global</code>".</p></dd></dl></div></div><div class="refsect1"><a name="idm140604910849360"></a><h2 id="[DHCP] Section Options">[DHCP] Section Options<a class="headerlink" title="Permalink to this headline" href="#%5BDHCP%5D%20Section%20Options">¶</a></h2><p>The "<code class="literal">[DHCP]</code>" section accepts the following keys:</p><div class="variablelist"><dl class="variablelist"><dt id="UseDNS="><span class="term"><code class="varname">UseDNS=</code></span><a class="headerlink" title="Permalink to this term" href="#UseDNS=">¶</a></dt><dd><p>When true (the default), the DNS servers received
158 from the DHCP server will be used and take precedence over
159 any statically configured ones.</p></dd><dt id="UseMTU="><span class="term"><code class="varname">UseMTU=</code></span><a class="headerlink" title="Permalink to this term" href="#UseMTU=">¶</a></dt><dd><p>When true, the interface maximum transmission unit
160 from the DHCP server will be used on the current link.
161 Defaults to false.</p></dd><dt id="SendHostname="><span class="term"><code class="varname">SendHostname=</code></span><a class="headerlink" title="Permalink to this term" href="#SendHostname=">¶</a></dt><dd><p>When true (the default), the machine's hostname will be sent to the DHCP
162 server</p></dd><dt id="UseHostname="><span class="term"><code class="varname">UseHostname=</code></span><a class="headerlink" title="Permalink to this term" href="#UseHostname=">¶</a></dt><dd><p>When true (the default), the hostname received from
163 the DHCP server will be used as the transient
164 hostname.</p></dd><dt id="UseDomains="><span class="term"><code class="varname">UseDomains=</code></span><a class="headerlink" title="Permalink to this term" href="#UseDomains=">¶</a></dt><dd><p>When true (not the default), the domain name
165 received from the DHCP server will be used for DNS
166 resolution over this link.</p></dd><dt id="UseRoutes="><span class="term"><code class="varname">UseRoutes=</code></span><a class="headerlink" title="Permalink to this term" href="#UseRoutes=">¶</a></dt><dd><p>When true (the default), the static routes will be
167 requested from the DHCP server and added to the routing
168 table with metric of 1024.</p></dd><dt id="CriticalConnection="><span class="term"><code class="varname">CriticalConnection=</code></span><a class="headerlink" title="Permalink to this term" href="#CriticalConnection=">¶</a></dt><dd><p>When true, the connection will never be torn down
169 even if the DHCP lease expires. This is contrary to the
170 DHCP specification, but may be the best choice if, say,
171 the root filesystem relies on this connection. Defaults to
172 false.</p></dd><dt id="VendorClassIdentifier="><span class="term"><code class="varname">VendorClassIdentifier=</code></span><a class="headerlink" title="Permalink to this term" href="#VendorClassIdentifier=">¶</a></dt><dd><p>The vendor class identifier used to identify vendor
173 type and configuration.</p></dd><dt id="RequestBroadcast="><span class="term"><code class="varname">RequestBroadcast=</code></span><a class="headerlink" title="Permalink to this term" href="#RequestBroadcast=">¶</a></dt><dd><p>Request the server to use broadcast messages before
174 the IP address has been configured. This is necessary for
175 devices that cannot receive RAW packets, or that cannot
176 receive packets at all before an IP address has been
177 configured. On the other hand, this must not be enabled on
178 networks where broadcasts are filtered out.</p></dd><dt id="RouteMetric="><span class="term"><code class="varname">RouteMetric=</code></span><a class="headerlink" title="Permalink to this term" href="#RouteMetric=">¶</a></dt><dd><p>Set the routing metric for routes specified by the
179 DHCP server.</p></dd></dl></div></div><div class="refsect1"><a name="idm140604910828512"></a><h2 id="[Bridge] Section Options">[Bridge] Section Options<a class="headerlink" title="Permalink to this headline" href="#%5BBridge%5D%20Section%20Options">¶</a></h2><p>The "<code class="literal">[Bridge]</code>" section accepts the
180 following keys.</p><div class="variablelist"><dl class="variablelist"><dt id="Cost="><span class="term"><code class="varname">Cost=</code></span><a class="headerlink" title="Permalink to this term" href="#Cost=">¶</a></dt><dd><p>Each port in a bridge may have different speed. Cost
181 is used to decide which link to use. Faster interfaces
182 should have lower costs</p></dd></dl></div></div><div class="refsect1"><a name="idm140604910824272"></a><h2 id="[BridgeFDB] Section Options">[BridgeFDB] Section Options<a class="headerlink" title="Permalink to this headline" href="#%5BBridgeFDB%5D%20Section%20Options">¶</a></h2><p>The "<code class="literal">[BridgeFDB]</code>" section manages the
183 forwarding database table of a port and accepts the following
184 keys. Specify several "<code class="literal">[BridgeFDB]</code>" sections to
185 configure several static MAC table entries.</p><div class="variablelist"><dl class="variablelist"><dt id="MACAddress="><span class="term"><code class="varname">MACAddress=</code></span><a class="headerlink" title="Permalink to this term" href="#MACAddress=">¶</a></dt><dd><p>As in the "<code class="literal">[Network]</code>" section. This
186 key is mandatory.</p></dd><dt id="VLANId="><span class="term"><code class="varname">VLANId=</code></span><a class="headerlink" title="Permalink to this term" href="#VLANId=">¶</a></dt><dd><p>The VLAN Id for the new static MAC table entry. If
187 omitted, no VLAN Id info is appended to the new static MAC
188 table entry.</p></dd></dl></div></div><div class="refsect1"><a name="idm140604910817008"></a><h2 id="Example">Example<a class="headerlink" title="Permalink to this headline" href="#Example">¶</a></h2><div class="example"><a name="idm140604910816368"></a><p class="title"><b>Example 1. /etc/systemd/network/50-static.network</b></p><div class="example-contents"><pre class="programlisting">[Match]
60f067b4
JS		 189Name=enp2s0
190
191[Network]
192Address=192.168.0.15/24
e735f4d4 193Gateway=192.168.0.1</pre></div></div><br class="example-break"><div class="example"><a name="idm140604910814880"></a><p class="title"><b>Example 2. /etc/systemd/network/80-dhcp.network</b></p><div class="example-contents"><pre class="programlisting">[Match]
60f067b4
JS		 194Name=en*
195
196[Network]
e735f4d4 197DHCP=both</pre></div></div><br class="example-break"><div class="example"><a name="idm140604910813488"></a><p class="title"><b>Example 3. /etc/systemd/network/bridge-static.network</b></p><div class="example-contents"><pre class="programlisting">[Match]
60f067b4
JS		 198Name=bridge0
199
200[Network]
201Address=192.168.0.15/24
202Gateway=192.168.0.1
e735f4d4 203DNS=192.168.0.1</pre></div></div><br class="example-break"><div class="example"><a name="idm140604910811984"></a><p class="title"><b>Example 4. /etc/systemd/network/bridge-slave-interface.network</b></p><div class="example-contents"><pre class="programlisting">[Match]
60f067b4
JS		 204Name=enp2s0
205
206[Network]
e735f4d4 207Bridge=bridge0</pre></div></div><br class="example-break"><div class="example"><a name="idm140604910810592"></a><p class="title"><b>Example 5. /etc/systemd/network/ipip.network</b></p><div class="example-contents"><pre class="programlisting">[Match]
e842803a
MB		 208Name=em1
209
210[Network]
e735f4d4 211Tunnel=ipip-tun</pre></div></div><br class="example-break"><div class="example"><a name="idm140604910809200"></a><p class="title"><b>Example 6. /etc/systemd/network/sit.network</b></p><div class="example-contents"><pre class="programlisting">[Match]
e842803a
MB		 212Name=em1
213
214[Network]
e735f4d4 215Tunnel=sit-tun</pre></div></div><br class="example-break"><div class="example"><a name="idm140604910807808"></a><p class="title"><b>Example 7. /etc/systemd/network/gre.network</b></p><div class="example-contents"><pre class="programlisting">[Match]
e842803a
MB		 216Name=em1
217
218[Network]
e735f4d4 219Tunnel=gre-tun</pre></div></div><br class="example-break"><div class="example"><a name="idm140604910806416"></a><p class="title"><b>Example 8. /etc/systemd/network/vti.network</b></p><div class="example-contents"><pre class="programlisting">[Match]
e842803a
MB		 220Name=em1
221
222[Network]
e735f4d4
MP		 223Tunnel=vti-tun</pre></div></div><br class="example-break"></div><div class="refsect1"><a name="idm140604910804896"></a><h2 id="See Also">See Also<a class="headerlink" title="Permalink to this headline" href="#See%20Also">¶</a></h2><p>
224 <a href="systemd.html"><span class="citerefentry"><span class="refentrytitle">systemd</span>(1)</span></a>,
225 <a href="systemd-networkd.html"><span class="citerefentry"><span class="refentrytitle">systemd-networkd</span>(8)</span></a>,
226 <a href="systemd.link.html"><span class="citerefentry"><span class="refentrytitle">systemd.link</span>(5)</span></a>,
227 <a href="systemd.netdev.html"><span class="citerefentry"><span class="refentrytitle">systemd.netdev</span>(5)</span></a>
228 </p></div></div></body></html>
systemd for Proxmox projects