2016-04-04 17:22:45 +00:00
|
|
|
<?xml version='1.0'?>
|
2013-04-09 20:41:00 +00:00
|
|
|
<?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>
|
|
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
|
2016-04-04 17:22:45 +00:00
|
|
|
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
|
|
|
|
<!ENTITY % entities SYSTEM "common.ent" >
|
|
|
|
%entities;
|
|
|
|
]>
|
2013-04-09 20:41:00 +00:00
|
|
|
|
|
|
|
<!--
|
2016-04-06 14:42:19 +00:00
|
|
|
NetworkManager(8) manual page
|
|
|
|
|
|
|
|
Copyright 2005 - 2016 Red Hat, Inc.
|
|
|
|
Copyright 2005 - 2009 Novell, Inc.
|
|
|
|
Copyright 2005 Robert Love
|
|
|
|
|
|
|
|
Permission is granted to copy, distribute and/or modify this document
|
|
|
|
under the terms of the GNU Free Documentation License, Version 1.1
|
|
|
|
or any later version published by the Free Software Foundation;
|
|
|
|
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
|
|
|
|
Texts. You may obtain a copy of the GNU Free Documentation License
|
|
|
|
from the Free Software Foundation by visiting their Web site or by
|
|
|
|
writing to:
|
|
|
|
|
|
|
|
Free Software Foundation, Inc.,
|
|
|
|
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
|
2013-04-09 20:41:00 +00:00
|
|
|
-->
|
|
|
|
|
|
|
|
<refentry id="NetworkManager">
|
|
|
|
<refentryinfo>
|
|
|
|
<title>NetworkManager</title>
|
2013-05-07 07:54:28 +00:00
|
|
|
<author>NetworkManager developers</author>
|
2013-04-09 20:41:00 +00:00
|
|
|
</refentryinfo>
|
|
|
|
<refmeta>
|
|
|
|
<refentrytitle>NetworkManager</refentrytitle>
|
|
|
|
<manvolnum>8</manvolnum>
|
2013-05-07 07:54:28 +00:00
|
|
|
<refmiscinfo class="source">NetworkManager</refmiscinfo>
|
|
|
|
<refmiscinfo class="manual">Network management daemons</refmiscinfo>
|
2016-04-04 17:22:45 +00:00
|
|
|
<refmiscinfo class="version">&NM_VERSION;</refmiscinfo>
|
2013-04-09 20:41:00 +00:00
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
<refname>NetworkManager</refname>
|
|
|
|
<refpurpose>network management daemon</refpurpose>
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
<cmdsynopsis>
|
|
|
|
<command>NetworkManager <arg choice="opt" rep="repeat">OPTIONS</arg></command>
|
|
|
|
</cmdsynopsis>
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Description</title>
|
|
|
|
<para>
|
|
|
|
The NetworkManager daemon attempts to make networking
|
|
|
|
configuration and operation as painless and automatic as
|
|
|
|
possible by managing the primary network connection and other
|
|
|
|
network interfaces, like Ethernet, WiFi, and Mobile Broadband
|
|
|
|
devices. NetworkManager will connect any network device when a
|
|
|
|
connection for that device becomes available, unless that
|
|
|
|
behavior is disabled. Information about networking is exported
|
|
|
|
via a D-Bus interface to any interested application, providing a
|
|
|
|
rich API with which to inspect and control network settings and
|
|
|
|
operation.
|
|
|
|
</para>
|
2014-01-27 12:08:14 +00:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Dispatcher scripts</title>
|
2013-04-09 20:41:00 +00:00
|
|
|
<para>
|
|
|
|
NetworkManager will execute scripts in the
|
2016-11-11 13:26:25 +00:00
|
|
|
<filename>/etc/NetworkManager/dispatcher.d</filename>
|
|
|
|
directory or subdirectories in
|
2014-06-02 19:07:46 +00:00
|
|
|
alphabetical order in response to network events. Each script should
|
|
|
|
be a regular executable file owned by root. Furthermore, it must not be
|
2013-04-09 20:41:00 +00:00
|
|
|
writable by group or other, and not setuid.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
Each script receives two arguments, the first being the interface name of the
|
2015-08-19 20:14:07 +00:00
|
|
|
device an operation just happened on, and second the action. For device actions,
|
|
|
|
the interface is the name of the kernel interface suitable for IP configuration.
|
|
|
|
Thus it is either VPN_IP_IFACE, DEVICE_IP_IFACE, or DEVICE_IFACE, as applicable.
|
2016-07-20 15:48:08 +00:00
|
|
|
For the <varname>hostname</varname> and <varname>connectivity-change</varname>
|
|
|
|
actions it is always "none".
|
2013-04-09 20:41:00 +00:00
|
|
|
</para>
|
2014-01-27 12:08:14 +00:00
|
|
|
<para>The actions are:</para>
|
2013-04-09 20:41:00 +00:00
|
|
|
<variablelist class="dispatcher-options">
|
2014-06-02 19:07:46 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>pre-up</varname></term>
|
|
|
|
<listitem><para>The interface is connected to the network but is not
|
|
|
|
yet fully activated. Scripts acting on this event must be placed or
|
2016-11-11 13:26:25 +00:00
|
|
|
symlinked into the <filename>/etc/NetworkManager/dispatcher.d/pre-up.d</filename>
|
|
|
|
directory, and NetworkManager will wait for script execution to complete before
|
2014-06-02 19:07:46 +00:00
|
|
|
indicating to applications that the interface is fully activated.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2013-04-09 20:41:00 +00:00
|
|
|
<varlistentry>
|
2014-01-27 12:08:14 +00:00
|
|
|
<term><varname>up</varname></term>
|
|
|
|
<listitem><para>The interface has been activated.</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
2014-06-02 19:07:46 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>pre-down</varname></term>
|
|
|
|
<listitem><para>The interface will be deactivated but has not yet been
|
|
|
|
disconnected from the network. Scripts acting on this event must be
|
2016-11-11 13:26:25 +00:00
|
|
|
placed or symlinked into the <filename>/etc/NetworkManager/dispatcher.d/pre-down.d</filename>
|
2014-06-02 19:07:46 +00:00
|
|
|
directory, and NetworkManager will wait for script execution to complete
|
|
|
|
before disconnecting the interface from its network. Note that this
|
|
|
|
event is not emitted for forced disconnections, like when carrier is
|
|
|
|
lost or a wireless signal fades. It is only emitted when there is
|
|
|
|
an opportunity to cleanly handle a network disconnection event.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2013-04-09 20:41:00 +00:00
|
|
|
<varlistentry>
|
2014-01-27 12:08:14 +00:00
|
|
|
<term><varname>down</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The interface has been deactivated.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
2014-06-02 19:07:46 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>vpn-pre-up</varname></term>
|
|
|
|
<listitem><para>The VPN is connected to the network but is not yet
|
|
|
|
fully activated. Scripts acting on this event must be placed or
|
2016-11-11 13:26:25 +00:00
|
|
|
symlinked into the <filename>/etc/NetworkManager/dispatcher.d/pre-up.d</filename>
|
|
|
|
directory, and NetworkManager will wait for script execution to complete before
|
2014-06-02 19:07:46 +00:00
|
|
|
indicating to applications that the VPN is fully activated.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2013-04-09 20:41:00 +00:00
|
|
|
<varlistentry>
|
2014-01-27 12:08:14 +00:00
|
|
|
<term><varname>vpn-up</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
A VPN connection has been activated.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
2014-06-02 19:07:46 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>vpn-pre-down</varname></term>
|
|
|
|
<listitem><para>The VPN will be deactivated but has not yet been
|
|
|
|
disconnected from the network. Scripts acting on this event must be
|
2016-11-11 13:26:25 +00:00
|
|
|
placed or symlinked into the <filename>/etc/NetworkManager/dispatcher.d/pre-down.d</filename>
|
2014-06-02 19:07:46 +00:00
|
|
|
directory, and NetworkManager will wait for script execution to complete
|
|
|
|
before disconnecting the VPN from its network. Note that this
|
|
|
|
event is not emitted for forced disconnections, like when the VPN
|
|
|
|
terminates unexpectedly or general connectivity is lost. It is only
|
|
|
|
emitted when there is an opportunity to cleanly handle a VPN
|
|
|
|
disconnection event.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2013-04-09 20:41:00 +00:00
|
|
|
<varlistentry>
|
2014-01-27 12:08:14 +00:00
|
|
|
<term><varname>vpn-down</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
A VPN connection has been deactivated.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2014-01-27 12:08:14 +00:00
|
|
|
<term><varname>hostname</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The system hostname has been updated. Use gethostname(2) to retrieve it.
|
|
|
|
The interface name (first argument) is empty and no environment variable is
|
|
|
|
set for this action.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2014-01-27 12:08:14 +00:00
|
|
|
<term><varname>dhcp4-change</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The DHCPv4 lease has changed (renewed, rebound, etc).
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2014-01-27 12:08:14 +00:00
|
|
|
<term><varname>dhcp6-change</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The DHCPv6 lease has changed (renewed, rebound, etc).
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
2016-07-20 15:48:08 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>connectivity-change</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The network connectivity state has changed (no connectivity, went online, etc).
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2013-04-09 20:41:00 +00:00
|
|
|
</variablelist>
|
2014-01-27 12:08:14 +00:00
|
|
|
<para>
|
|
|
|
The environment contains more information about the interface and the connection.
|
|
|
|
The following variables are available for the use in the dispatcher scripts:
|
|
|
|
<variablelist class="dispatcher-environment">
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>CONNECTION_UUID</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The UUID of the connection profile.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>CONNECTION_ID</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The name (ID) of the connection profile.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2014-12-18 14:06:56 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>CONNECTION_DBUS_PATH</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The NetworkManager D-Bus path of the connection.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2014-12-16 19:08:38 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>CONNECTION_FILENAME</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The backing file name of the connection profile (if any).
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2014-12-18 14:13:57 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>CONNECTION_EXTERNAL</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
If "1", this indicates that the connection describes a
|
|
|
|
network configuration created outside of NetworkManager.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2014-01-27 12:08:14 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>DEVICE_IFACE</varname></term>
|
|
|
|
<listitem><para>
|
2016-02-22 19:08:06 +00:00
|
|
|
The interface name of the control interface of the device.
|
|
|
|
Depending on the device type, this differs from
|
|
|
|
<varname>DEVICE_IP_IFACE</varname>. For example for
|
|
|
|
ADSL devices, this could be 'atm0' or for WWAN devices
|
|
|
|
it might be 'ttyUSB0'.
|
2014-01-27 12:08:14 +00:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>DEVICE_IP_IFACE</varname></term>
|
|
|
|
<listitem><para>
|
2016-02-22 19:08:06 +00:00
|
|
|
The IP interface name of the device. This is the network
|
|
|
|
interface on which IP addresses and routes will be configured.
|
2014-01-27 12:08:14 +00:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>IP4_ADDRESS_N</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The IPv4 address in the format "address/prefix gateway", where N is a number
|
2014-11-19 12:50:35 +00:00
|
|
|
from 0 to (# IPv4 addresses - 1). gateway item in this variable is deprecated,
|
2014-11-19 12:03:38 +00:00
|
|
|
use IP4_GATEWAY instead.
|
2014-01-27 12:08:14 +00:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>IP4_NUM_ADDRESSES</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The variable contains the number of IPv4 addresses the script may expect.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2014-11-19 12:03:38 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>IP4_GATEWAY</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The gateway IPv4 address in traditional numbers-and-dots notation.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2014-01-27 12:08:14 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>IP4_ROUTE_N</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The IPv4 route in the format "address/prefix next-hop metric", where N is a number
|
2014-11-19 12:50:35 +00:00
|
|
|
from 0 to (# IPv4 routes - 1).
|
2014-01-27 12:08:14 +00:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>IP4_NUM_ROUTES</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The variable contains the number of IPv4 routes the script may expect.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>IP4_NAMESERVERS</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The variable contains a space-separated list of the DNS servers.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>IP4_DOMAINS</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The variable contains a space-separated list of the search domains.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>DHCP4_<dhcp-option-name></varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
If the connection used DHCP for address configuration, the received DHCP
|
|
|
|
configuration is passed in the environment using standard DHCP
|
|
|
|
option names, prefixed with "DHCP4_", like "DHCP4_HOST_NAME=foobar".
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>IP6_<name> and DHCP6_<name></varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The same variables as for IPv4 are available for IPv6, but the prefixes are IP6_
|
|
|
|
and DHCP6_ instead.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2016-07-20 15:48:08 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><varname>CONNECTIVITY_STATE</varname></term>
|
|
|
|
<listitem><para> The network connectivity state, which can
|
|
|
|
take the values defined by the NMConnectivityState type,
|
|
|
|
from the org.freedesktop.NetworkManager D-Bus API: unknown,
|
|
|
|
none, portal, limited or full. Note: this variable will only
|
|
|
|
be set for connectivity-change actions.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2014-01-27 12:08:14 +00:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
In case of VPN, VPN_IP_IFACE is set, and IP4_*, IP6_* variables with VPN prefix are
|
|
|
|
exported too, like VPN_IP4_ADDRESS_0, VPN_IP4_NUM_ADDRESSES.
|
|
|
|
</para>
|
2014-03-31 16:57:16 +00:00
|
|
|
<para>
|
|
|
|
Dispatcher scripts are run one at a time, but asynchronously from the main
|
|
|
|
NetworkManager process, and will be killed if they run for too long. If your script
|
|
|
|
might take arbitrarily long to complete, you should spawn a child process and have the
|
2015-07-14 16:17:33 +00:00
|
|
|
parent return immediately. Scripts that are symbolic links pointing inside the
|
2016-11-11 13:26:25 +00:00
|
|
|
<filename>/etc/NetworkManager/dispatcher.d/no-wait.d/</filename>
|
|
|
|
directory are run immediately, without
|
2015-07-14 16:17:33 +00:00
|
|
|
waiting for the termination of previous scripts, and in parallel. Also beware that
|
|
|
|
once a script is queued, it will always be run, even if a later event renders it
|
|
|
|
obsolete. (Eg, if an interface goes up, and then back down again quickly, it is
|
|
|
|
possible that one or more "up" scripts will be run after the interface has gone down.)
|
2014-03-31 16:57:16 +00:00
|
|
|
</para>
|
2013-04-09 20:41:00 +00:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Options</title>
|
|
|
|
|
|
|
|
<para>The following options are understood:</para>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><option>--version</option> | <option>-V</option></term>
|
|
|
|
<listitem><para>Print the NetworkManager software version and exit.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><option>--help</option> | <option>-h</option></term>
|
|
|
|
<listitem><para>Print NetworkManager's available options and exit.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><option>--no-daemon</option> | <option>-n</option></term>
|
|
|
|
<listitem><para>Do not daemonize.
|
|
|
|
</para></listitem>
|
2013-05-17 19:18:03 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><option>--debug</option> | <option>-d</option></term>
|
|
|
|
<listitem><para>Do not daemonize, and direct log output to the
|
|
|
|
controlling terminal in addition to syslog.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><option>--pid-file</option> | <option>-p</option></term>
|
|
|
|
<listitem><para>Specify location of a PID file. The PID file
|
|
|
|
is used for storing PID of the running process and prevents
|
|
|
|
running multiple instances.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><option>--state-file</option></term>
|
|
|
|
<listitem><para>Specify file for storing state of the
|
|
|
|
NetworkManager persistently. If not specified, the default
|
2016-11-11 13:26:25 +00:00
|
|
|
value of <filename>/var/lib/NetworkManager/NetworkManager.state</filename>
|
|
|
|
is used.
|
2016-01-27 11:54:18 +00:00
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><option>--config</option></term>
|
|
|
|
<listitem><para> Specify configuration file to set up various
|
|
|
|
settings for NetworkManager. If not specified, the default
|
2016-11-11 13:26:25 +00:00
|
|
|
value of <filename>/etc/NetworkManager/NetworkManager.conf</filename>
|
|
|
|
is used with
|
2016-01-27 11:54:18 +00:00
|
|
|
a fallback to the older 'nm-system-settings.conf' if located
|
|
|
|
in the same directory. See
|
2016-05-30 18:24:32 +00:00
|
|
|
<link linkend='NetworkManager.conf'><citerefentry><refentrytitle>NetworkManager.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></link>
|
2016-01-27 11:54:18 +00:00
|
|
|
for more information on configuration file.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><option>--plugins</option></term>
|
|
|
|
<listitem><para>List plugins used to manage system-wide
|
|
|
|
connection settings. This list has preference over plugins
|
|
|
|
specified in the configuration file. Currently supported
|
|
|
|
plugins are: keyfile, <option>ifcfg-rh</option>,
|
|
|
|
<option>ifcfg-suse</option>, <option>ifupdown</option>.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><option>--log-level</option></term>
|
|
|
|
<listitem><para>
|
|
|
|
Sets how much information NetworkManager sends to the log destination (usually
|
|
|
|
syslog's "daemon" facility). By default, only informational, warning, and error
|
|
|
|
messages are logged. See the section on <literal>logging</literal> in
|
2016-05-30 18:24:32 +00:00
|
|
|
<link linkend='NetworkManager.conf'><citerefentry><refentrytitle>NetworkManager.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></link>
|
2016-01-27 11:54:18 +00:00
|
|
|
for more information.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><option>--log-domains</option></term>
|
|
|
|
<listitem><para>
|
|
|
|
A comma-separated list specifying which operations are logged to the log
|
|
|
|
destination (usually syslog). By default, most domains are logging-enabled.
|
|
|
|
See the section on <literal>logging</literal> in
|
2016-05-30 18:24:32 +00:00
|
|
|
<link linkend='NetworkManager.conf'><citerefentry><refentrytitle>NetworkManager.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></link>
|
2016-01-27 11:54:18 +00:00
|
|
|
for more information.
|
|
|
|
</para></listitem>
|
2013-04-09 20:41:00 +00:00
|
|
|
</varlistentry>
|
2015-11-20 16:52:54 +00:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--print-config</option></term>
|
|
|
|
<listitem><para>
|
2015-12-24 08:48:20 +00:00
|
|
|
Print the NetworkManager configuration to stdout and exit.
|
2015-11-20 16:52:54 +00:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
2013-04-09 20:41:00 +00:00
|
|
|
</variablelist>
|
|
|
|
</refsect1>
|
|
|
|
|
2015-01-22 15:41:15 +00:00
|
|
|
<refsect1>
|
2016-11-11 13:07:37 +00:00
|
|
|
<title>Udev Properties</title>
|
2015-01-22 15:41:15 +00:00
|
|
|
|
|
|
|
<para>
|
|
|
|
<citerefentry><refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
|
|
|
device manager is used for the network device discovery. The following
|
|
|
|
property influences how NetworkManager manages the devices:
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
2016-01-27 11:54:18 +00:00
|
|
|
<term><varname>NM_UNMANAGED</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
No default connection will be created and automatic activation
|
|
|
|
will not be attempted when this property of a device is set to a
|
|
|
|
true value ("1" or "true"). You will still be able to attach a
|
|
|
|
connection to the device manually or observe externally added
|
|
|
|
configuration such as addresses or routes.
|
|
|
|
</para><para>
|
|
|
|
Create an udev rule that sets this property to prevent NetworkManager
|
|
|
|
from interfering with virtual Ethernet device interfaces that are
|
|
|
|
managed by virtualization tools.
|
|
|
|
</para></listitem>
|
2015-01-22 15:41:15 +00:00
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</refsect1>
|
|
|
|
|
2016-01-19 10:36:07 +00:00
|
|
|
<refsect1>
|
|
|
|
<title>SIGNALS</title>
|
|
|
|
<para>
|
|
|
|
NetworkManager process handles the following signals:
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>SIGHUP</varname></term>
|
|
|
|
<listitem><para>
|
|
|
|
The signal causes a reload of NetworkManager's configuration.
|
|
|
|
Note that not all configuration parameters can be changed at
|
|
|
|
runtime and therefore some changes may be applied only after
|
2016-05-31 13:58:25 +00:00
|
|
|
the next restart of the daemon.
|
|
|
|
A SIGHUP also involves further reloading actions, like doing
|
|
|
|
a DNS update and restarting the DNS plugin. The latter can be
|
|
|
|
useful for example when using the dnsmasq plugin and changing
|
2016-11-11 13:26:25 +00:00
|
|
|
its configuration in <filename>/etc/NetworkManager/dnsmasq.d</filename>.
|
|
|
|
However, it also means this will shortly interrupt name resolution.
|
2016-05-31 13:58:25 +00:00
|
|
|
In the future, there may be further actions added.
|
|
|
|
A SIGHUP means to update NetworkManager configuration and reload
|
|
|
|
everything that is supported. Note that this does not reload
|
|
|
|
connections from disk. For that there is a D-Bus API and
|
|
|
|
nmcli's reload action
|
2016-01-19 10:36:07 +00:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>SIGUSR1</varname></term>
|
|
|
|
<listitem><para>
|
2016-05-31 13:58:25 +00:00
|
|
|
The signal forces a rewrite of DNS configuration. Contrary to
|
|
|
|
SIGHUP, this does not restart the DNS plugin and will not interrupt
|
|
|
|
name resolution.
|
|
|
|
In the future, further actions may be added. A SIGUSR1
|
|
|
|
means to write out data like resolv.conf, or refresh a cache.
|
|
|
|
It is a subset of what is done for SIGHUP without reloading
|
|
|
|
configuration from disk.
|
2016-01-19 10:36:07 +00:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><varname>SIGUSR2</varname></term>
|
|
|
|
<listitem><para>
|
2016-05-31 13:58:25 +00:00
|
|
|
The signal has no effect at the moment but is reserved for future
|
|
|
|
use.
|
2016-01-19 10:36:07 +00:00
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</para>
|
2016-05-30 14:43:39 +00:00
|
|
|
<para>
|
|
|
|
An alternative to a signal to reload configuration is the Reload D-Bus call.
|
|
|
|
It allows for more fine-grained selection of what to reload, it only returns
|
|
|
|
after the reload is complete, and it is guarded by PolicyKit.
|
|
|
|
</para>
|
2016-01-19 10:36:07 +00:00
|
|
|
</refsect1>
|
|
|
|
|
2013-04-09 20:41:00 +00:00
|
|
|
<refsect1>
|
2016-11-11 13:07:37 +00:00
|
|
|
<title>Debugging</title>
|
2013-04-09 20:41:00 +00:00
|
|
|
<para>
|
|
|
|
The following environment variables are supported to help
|
|
|
|
debugging. When used in conjunction with the
|
|
|
|
<option>--no-daemon</option> option (thus echoing PPP and DHCP
|
|
|
|
helper output to stdout) these can quickly help pinpoint the
|
|
|
|
source of connection issues. Also see the
|
|
|
|
<option>--log-level</option> and <option>--log-domains</option>
|
|
|
|
to enable debug logging inside NetworkManager itself.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
<option>NM_PPP_DEBUG</option>: When set to anything, causes
|
|
|
|
NetworkManager to turn on PPP debugging in pppd, which logs
|
|
|
|
all PPP and PPTP frames and client/server exchanges.
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
2016-11-11 13:20:46 +00:00
|
|
|
<refsect1>
|
|
|
|
<title>Bugs</title>
|
|
|
|
<para>
|
|
|
|
Please report any bugs you find in NetworkManager at the
|
|
|
|
<ulink url="https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager">NetworkManager bug tracker</ulink>.
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
2013-04-09 20:41:00 +00:00
|
|
|
<refsect1>
|
|
|
|
<title>See Also</title>
|
|
|
|
<para>
|
2016-11-11 13:20:46 +00:00
|
|
|
<ulink url="https://wiki.gnome.org/Projects/NetworkManager">NetworkManager home page</ulink>,
|
2016-05-30 18:24:32 +00:00
|
|
|
<link linkend='NetworkManager.conf'><citerefentry><refentrytitle>NetworkManager.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></link>,
|
|
|
|
<link linkend='nmcli'><citerefentry><refentrytitle>nmcli</refentrytitle><manvolnum>1</manvolnum></citerefentry></link>,
|
|
|
|
<link linkend='nmcli-examples'><citerefentry><refentrytitle>nmcli-examples</refentrytitle><manvolnum>7</manvolnum></citerefentry></link>,
|
|
|
|
<link linkend='nm-online'><citerefentry><refentrytitle>nm-online</refentrytitle><manvolnum>1</manvolnum></citerefentry></link>,
|
|
|
|
<link linkend='nm-settings'><citerefentry><refentrytitle>nm-settings</refentrytitle><manvolnum>5</manvolnum></citerefentry></link>,
|
2013-04-09 20:41:00 +00:00
|
|
|
<citerefentry><refentrytitle>nm-applet</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
2016-04-16 14:31:00 +00:00
|
|
|
<citerefentry><refentrytitle>nm-connection-editor</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
2015-01-22 15:41:15 +00:00
|
|
|
<citerefentry><refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
2013-04-09 20:41:00 +00:00
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
</refentry>
|