2 <!DOCTYPE refentry PUBLIC
"-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
4 <!-- SPDX-License-Identifier: LGPL-2.1+ -->
6 <refentry id=
"networkctl" conditional='ENABLE_NETWORKD'
7 xmlns:
xi=
"http://www.w3.org/2001/XInclude">
10 <title>networkctl
</title>
11 <productname>systemd
</productname>
15 <refentrytitle>networkctl
</refentrytitle>
16 <manvolnum>1</manvolnum>
20 <refname>networkctl
</refname>
21 <refpurpose>Query the status of network links
</refpurpose>
26 <command>networkctl
</command>
27 <arg choice=
"opt" rep=
"repeat">OPTIONS
</arg>
28 <arg choice=
"plain">COMMAND
</arg>
29 <arg choice=
"opt" rep=
"repeat">LINK
</arg>
34 <title>Description
</title>
36 <para><command>networkctl
</command> may be used to introspect the
37 state of the network links as seen by
38 <command>systemd-networkd
</command>. Please refer to
39 <citerefentry><refentrytitle>systemd-networkd.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>
40 for an introduction to the basic concepts, functionality, and
41 configuration syntax.
</para>
45 <title>Commands
</title>
47 <para>The following commands are understood:
</para>
52 <command>list
</command>
53 <optional><replaceable>PATTERN…
</replaceable></optional>
57 <para>Show a list of existing links and their status. If one ore more
58 <replaceable>PATTERN
</replaceable>s are specified, only links matching one of them are shown.
59 If no further arguments are specified shows all links,
60 otherwise just the specified links. Produces output similar to:
62 <programlisting>IDX LINK TYPE OPERATIONAL SETUP
63 1 lo loopback carrier unmanaged
64 2 eth0 ether routable configured
65 3 virbr0 ether no-carrier unmanaged
66 4 virbr0-nic ether off unmanaged
68 4 links listed.
</programlisting></para>
70 <para>The operational status is one of the following:
75 <para>the device is powered down
</para>
79 <term>no-carrier
</term>
81 <para>the device is powered up, but it does not yet have a carrier
</para>
87 <para>the device has a carrier, but is not yet ready for normal traffic
</para>
91 <term>degraded-carrier
</term>
93 <para>for bond or bridge master, one of the bonding or bridge slave network interfaces is
94 in off, no-carrier, or dormant state
</para>
100 <para>the link has a carrier, or for bond or bridge master, all bonding or bridge slave
101 network interfaces are enslaved to the master.
</para>
105 <term>degraded
</term>
107 <para>the link has carrier and addresses valid on the local link configured
</para>
111 <term>enslaved
</term>
113 <para>the link has carrier and is enslaved to bond or bridge master network interface
</para>
117 <term>routable
</term>
119 <para>the link has carrier and routable address configured
</para>
125 <para>The setup status is one of the following:
130 <para>udev is still processing the link, we don't yet know if we will manage it
</para>
136 <para>networkd failed to manage the link
</para>
140 <term>configuring
</term>
142 <para>in the process of retrieving configuration or configuring the link
</para>
146 <term>configured
</term>
148 <para>link configured successfully
</para>
152 <term>unmanaged
</term>
154 <para>networkd is not handling the link
</para>
160 <para>the link is gone, but has not yet been dropped by networkd
</para>
170 <command>status
</command>
171 <optional><replaceable>PATTERN…
</replaceable></optional>
175 <para>Show information about the specified links: type, state, kernel module driver, hardware and
176 IP address, configured DNS servers, etc. If one ore more
<replaceable>PATTERN
</replaceable>s are
177 specified, only links matching one of them are shown.
</para>
179 <para>When no links are specified, an overall network status is shown. Also see the option
180 <option>--all
</option>.
</para>
182 <para>Produces output similar to:
185 Address:
10.193.76.5 on eth0
186 192.168.122.1 on virbr0
187 169.254.190.105 on eth0
188 fe80::
5054:aa:bbbb:cccc on eth0
189 Gateway:
10.193.11.1 (CISCO SYSTEMS, INC.) on eth0
191 8.8.4.4</programlisting></para>
198 <command>lldp
</command>
199 <optional><replaceable>PATTERN…
</replaceable></optional>
203 <para>Show discovered LLDP (Link Layer Discovery Protocol) neighbors. If one or more
204 <replaceable>PATTERN
</replaceable>s are specified only neighbors on those interfaces are shown.
205 Otherwise shows discovered neighbors on all interfaces. Note that for this feature to work,
206 <varname>LLDP=
</varname> must be turned on for the specific interface, see
207 <citerefentry><refentrytitle>systemd.network
</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
210 <para>Produces output similar to:
211 <programlisting>LINK CHASSIS ID SYSTEM NAME CAPS PORT ID PORT DESCRIPTION
212 enp0s25
00:e0:
4c:
00:
00:
00 GS1900 ..b........
2 Port #
2
215 o - Other; p - Repeater; b - Bridge; w - WLAN Access Point; r - Router;
216 t - Telephone; d - DOCSIS cable device; a - Station; c - Customer VLAN;
217 s - Service VLAN, m - Two-port MAC Relay (TPMR)
219 1 neighbors listed.
</programlisting></para>
225 <command>label
</command>
228 <listitem><para>Show numerical address labels that can be used for address selection.
229 This is the same information that
230 <citerefentry><refentrytitle>ip-addrlabel
</refentrytitle><manvolnum>8</manvolnum></citerefentry>
231 shows. See
<ulink url=
"https://tools.ietf.org/html/rfc3484">RFC
3484</ulink>
232 for a discussion of address labels.
</para>
234 <para>Produces output similar to:
235 <programlisting>Prefix/Prefixlen Label
245 ::
1/
128 0</programlisting></para>
251 <command>delete
</command>
253 <listitem><para>Deletes virtual netdevs. Takes interface name or index number.
</para></listitem>
258 <command>renew
</command>
260 <listitem><para>Renew dynamic configurations e.g. addresses received from DHCP server.
261 Takes interface name or index number.
</para></listitem>
266 <command>reconfigure
</command>
268 <listitem><para>Reconfigure network interfaces. Takes interface name or index number.
</para></listitem>
273 <command>reload
</command>
275 <listitem><para>Reload
<filename>.netdev
</filename> and
<filename>.network
</filename> files.
276 If a new
<filename>.netdev
</filename> file is found, then the corresponding netdev is created.
277 Note that even if an existing
<filename>.netdev
</filename> is modified or removed,
278 <command>systemd-networkd
</command> does not update or remove the netdev.
279 If a new, modified or removed
<filename>.network
</filename> file is found, then all interfaces
280 which match the file are reconfigured.
</para></listitem>
287 <title>Options
</title>
289 <para>The following options are understood:
</para>
295 <option>--all
</option>
299 <para>Show all links with
<command>status
</command>.
</para>
306 <option>--stats
</option>
310 <para>Show link statistics with
<command>status
</command>.
</para>
314 <xi:include href=
"standard-options.xml" xpointer=
"help" />
315 <xi:include href=
"standard-options.xml" xpointer=
"version" />
316 <xi:include href=
"standard-options.xml" xpointer=
"no-legend" />
317 <xi:include href=
"standard-options.xml" xpointer=
"no-pager" />
323 <title>Exit status
</title>
325 <para>On success,
0 is returned, a non-zero failure code otherwise.
</para>
329 <title>See Also
</title>
331 <citerefentry><refentrytitle>systemd-networkd.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
332 <citerefentry><refentrytitle>systemd.network
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
333 <citerefentry><refentrytitle>systemd.netdev
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
334 <citerefentry project='die-net'
><refentrytitle>ip
</refentrytitle><manvolnum>8</manvolnum></citerefentry>