Ubuntu Manpages

NetworkManager

network management daemon

NetworkManager [--version] | [--help]

NetworkManager [--no-daemon] [--pid-file=<filename>] [--state-file=<filename>] [--config=<filename>] [--plugins=<plugin1>,plugin2>,...] [--log-level=<level>] [--log-domains=<domain1>,<domain2>,...] [--connectivity-uri=<uri>] [--connectivity-interval=<int>] [--connectivity-response=<resp>]

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.

NetworkManager will execute scripts in the /etc/NetworkManager/dispatcher.d directory in alphabetical order in response to network events. Each script should be:

(a)
a regular file
(b)
owned by root
(c)
not writable by group or other
(d)
not set-uid
(e)
and executable by the owner

Each script receives two arguments, the first being the interface name of the device just activated, and second an action.

Actions:

The interface has been activated. The environment contains more information about the interface; CONNECTION_UUID contains the UUID of the connection. Other variables are IP4_ADDRESS_N where N is a number from 0 to (# IPv4 addresses - 1), in the format "address/prefix gateway". IP4_NUM_ADDRESSES contains the number addresses the script may expect. IP4_NAMESERVERS contains a space-separated list of the DNS servers, and IP4_DOMAINS contains a space-separated list of the search domains. Routes use the format IP4_ROUTE_N where N is a number from 0 to (# IPv4 routes - 1), in the format "address/prefix next-hop metric", and IP4_NUM_ROUTES contains the number of routes to expect. 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".
The interface has been deactivated.
A VPN connection has been activated. The environment contains the connection UUID in the variable CONNECTION_UUID.
A VPN connection has been deactivated.
The system hostname has been updated. Use gethostname(2) to retrieve it.
The DHCPv4 lease has changed (renewed, rebound, etc).
The DHCPv6 lease has changed (renewed, rebound, etc).

The following options are supported:

Print the NetworkManager software version and exit.
Print NetworkManager's available options and exit.
Do not daemonize. This is useful for debugging, and directs log output to the controlling terminal in addition to syslog.
Specify location of a PID file. The PID file is used for storing PID of the running proccess and prevents running multiple instances.
Specify file for storing state of the NetworkManager persistently. If not specified, the default value of '<LOCALSTATEDIR>/lib/NetworkManager/NetworkManager.state' is used; where <LOCALSTATEDIR> is dependent on your distribution (usually it's /var).
Specify configuration file to set up various settings for NetworkManager. If not specified, the default value of '<SYSCONFDIR>/NetworkManager/NetworkManager.conf' is used with a fallback to the older 'nm-system-settings.conf' if located in the same directory; where <SYSCONFDIR> is dependent on your distribution (usually it's /etc). See NetworkManager.conf(5) for more information on configuration file.
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, ifcfg-rh, ifcfg-suse, ifupdown. See NetworkManager.conf(5) for more information on the plugins.
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 NetworkManager.conf(5) for more information on log levels and domains.
Sets which operations are logged to the log destination (usually syslog). By default, most domains are logging-enabled. See NetworkManager.conf(5) for more information on log levels and domains.
Sets the URI of a web page that will be used for connectivity checking. By default connectivity checking is disabled. See NetworkManager.conf(5) [connectivity] section for more information on connectivity checking feature.
Sets the interval (in seconds) in which connection checks for the URI are done. 0 means no checks. The default value is 300 seconds. See NetworkManager.conf(5) [connectivity] section for more information on connectivity checking feature.
If set, it controls what body content NetworkManager checks for when requesting the URI for connectivity checking. If missing, defaults to "NetworkManager is online". See NetworkManager.conf(5) [connectivity] section for more information on connectivity checking feature.

The following environment variables are supported to help debugging. When used in conjunction with the "--no-daemon" option (thus echoing PPP and DHCP helper output to stdout) these can quickly help pinpoint the source of connection issues. Also see the --log-level and --log-domains to enable debug logging inside NetworkManager itself.

When set to anything, causes NetworkManager to turn on PPP debugging in pppd, which logs all PPP and PPTP frames and client/server exchanges.

nm-tool(1), nm-online(1), nmcli(1), NetworkManager.conf(5), nm-settings(5), nm-applet(1), nm-connection-editor(1).