Section: Network management daemons (8)
- 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 or subdirectories in alphabetical order in response to network events. Each script should be a regular executable file owned by root. Furthermore, it must not be writable by group or other, and not setuid.
Each script receives two arguments, the first being the interface name of the device an operation just happened on, and second the action.
The actions are:
- The interface is connected to the network but is not yet fully activated. Scripts acting on this event must be placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-up.d directory, and NetworkManager will wait for script execution to complete before indicating to applications that the interface is fully activated.
- The interface has been activated.
- The interface will be deactivated but has not yet been disconnected from the network. Scripts acting on this event must be placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-down.d 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.
- The interface has been deactivated.
- The VPN is connected to the network but is not yet fully activated. Scripts acting on this event must be placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-up.d directory, and NetworkManager will wait for script execution to complete before indicating to applications that the VPN is fully activated.
- A VPN connection has been activated.
- The VPN will be deactivated but has not yet been disconnected from the network. Scripts acting on this event must be placed or symlinked into the /etc/NetworkManager/dispatcher.d/pre-down.d 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.
- A VPN connection has been deactivated.
- 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.
- The DHCPv4 lease has changed (renewed, rebound, etc).
- The DHCPv6 lease has changed (renewed, rebound, etc).
The environment contains more information about the interface and the connection. The following variables are available for the use in the dispatcher scripts:
- The UUID of the connection profile.
- The name (ID) of the connection profile.
- The interface name of the device.
- The IP interface name of the device.
- The IPv4 address in the format "address/prefix gateway", where N is a number from 0 to (# IPv4 address \- 1).
- The variable contains the number of IPv4 addresses the script may expect.
- The IPv4 route in the format "address/prefix next-hop metric", where N is a number from 0 to (# IPv4 routes \- 1).
- The variable contains the number of IPv4 routes the script may expect.
- The variable contains a space-separated list of the DNS servers.
- The variable contains a space-separated list of the search domains.
- 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".
IP6_<name> and DHCP6_<name>
- The same variables as for IPv4 are available for IPv6, but the prefixes are IP6_ and DHCP6_ instead.
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.
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 parent return immediately. 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.)
The following options are understood:
--version | -V
- Print the NetworkManager software version and exit.
--help | -h
- Print NetworkManager's available options and exit.
--no-daemon | -n
- Do not daemonize.
--debug | -d
- Do not daemonize, and direct log output to the controlling terminal in addition to syslog.
--pid-file | -p
- 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 /var/lib/NetworkManager/NetworkManager.state is used.
- Specify configuration file to set up various settings for NetworkManager. If not specified, the default value of /etc/NetworkManager/NetworkManager.conf is used with a fallback to the older 'nm\-system\-settings.conf' if located in the same directory. See (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.:
- 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 logging in (5) for more information.
- 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 logging in (5) for more information.
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.