NETWORKMANAGER(8)					    Network management daemons						 NETWORKMANAGER(8)

NAME

       NetworkManager - network management daemon

SYNOPSIS

       NetworkManager [OPTIONS...]

DESCRIPTION

       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.

DISPATCHER SCRIPTS

       NetworkManager will execute scripts in the /etc/NetworkManager/dispatcher.d directory 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:

       up
	   The interface has been activated.

       down
	   The interface has been deactivated.

       vpn-up
	   A VPN connection has been activated.

       vpn-down
	   A VPN connection has been deactivated.

       hostname
	   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.

       dhcp4-change
	   The DHCPv4 lease has changed (renewed, rebound, etc).

       dhcp6-change
	   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:

       CONNECTION_UUID
	   The UUID of the connection profile.

       CONNECTION_ID
	   The name (ID) of the connection profile.

       DEVICE_IFACE
	   The interface name of the device.

       DEVICE_IP_IFACE
	   The IP interface name of the device.

       IP4_ADDRESS_N
	   The IPv4 address in the format "address/prefix gateway", where N is a number from 0 to (# IPv4 address - 1).

       IP4_NUM_ADDRESSES
	   The variable contains the number of IPv4 addresses the script may expect.

       IP4_ROUTE_N
	   The IPv4 route in the format "address/prefix next-hop metric", where N is a number from 0 to (# IPv4 routes - 1).

       IP4_NUM_ROUTES
	   The variable contains the number of IPv4 routes the script may expect.

       IP4_NAMESERVERS
	   The variable contains a space-separated list of the DNS servers.

       IP4_DOMAINS
	   The variable contains a space-separated list of the search domains.

       DHCP4_<dhcp-option-name>
	   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.

OPTIONS

       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.

       --state-file
	   Specify file for storing state of the NetworkManager persistently. If not specified, the default value of
	   /var/lib/NetworkManager/NetworkManager.state is used.

       --config
	   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 NetworkManager.conf(5) for more information on configuration file.

       --plugins
	   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.

       --log-level
	   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 NetworkManager.conf(5) for more information.

       --log-domains
	   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 NetworkManager.conf(5) for more information.

DEBUGGING

       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.

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

SEE ALSO

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

NetworkManager 0.9.10														 NETWORKMANAGER(8)