1NETWORKMANAGER(8) System Manager's Manual NETWORKMANAGER(8)
2
6 NetworkManager - network management daemon
7
9 NetworkManager [--no-daemon] [--pid-file=<filename>]
10 [--state-file=<filename>] [--config=<filename>] [--plugins=<plug‐
11 in1>,plugin2>,...] [--log-level=<level>]
12 [--log-domains=<domain1>,<domain2>,...]
13
15 The NetworkManager daemon attempts to make networking configuration
16 and operation as painless and automatic as possible by managing the
17 primary network connection and other network interfaces, like Ethernet,
18 WiFi, and Mobile Broadband devices. NetworkManager will connect any
19 network device when a connection for that device becomes available,
20 unless that behavior is disabled. Information about networking is
21 exported via a D-Bus interface to any interested application, providing
22 a rich API with which to inspect and control network settings and oper‐
23 ation.
24 NetworkManager will execute scripts in the /etc/NetworkManager/dis‐
26 patcher.d directory in alphabetical order in response to network
27 events. Each script should be (a) a regular file, (b) owned by root,
28 (c) not writable by group or other, (d) not set-uid, (e) and executable
29 by the owner. Each script receives two arguments, the first being the
30 interface name of the device just activated, and second an action.
31 up The interface has been activated. The environment contains more
33 information about the interface; CONNECTION_UUID contains the
34 UUID of the connection. Other variables are IP4_ADDRESS_N where
35 N is a number from 0 to (# IPv4 addresses - 1), in the format
36 "address/prefix gateway". IP4_NUM_ADDRESSES contains the number
37 addresses the script may expect. IP4_NAMESERVERS contains a
38 space-separated list of the DNS servers, and IP4_DOMAINS con‐
39 tains a space-separated list of the search domains. Routes use
40 the format IP4_ROUTE_N where N is a number from 0 to (# IPv4
41 routes - 1), in the format "address/prefix next-hop metric", and
42 IP4_NUM_ROUTES contains the number of routes to expect. If the
43 connection used DHCP for address configuration, the received
44 DHCP configuration is passed in the environment using standard
45 DHCP option names, prefixed with "DHCP4_", like
46 "DHCP4_HOST_NAME=foobar".
47 down The interface has been deactivated.
49 vpn-up A VPN connection has been activated. The environment contains
51 the connection UUID in the variable CONNECTION_UUID.
52 vpn-down
54 A VPN connection has been deactivated.
55 hostname
57 The system hostname has been updated. Use gethostname(2) to
58 retrieve it.
59 dhcp4-change
61 The DHCPv4 lease has changed (renewed, rebound, etc).
62 dhcp6-change
64 The DHCPv6 lease has changed (renewed, rebound, etc).
65
67 The following options are supported:
68 --no-daemon
70 Do not daemonize. This is useful for debugging, and directs log
71 output to the controlling terminal in addition to syslog.
72 --pid-file=<filename>
74 Specify location of a PID file. The PID file is used for stor‐
75 ing PID of the running proccess and prevents running multiple
76 instances.
77 --state-file=<filename>
79 Specify file for storing state of the NetworkManager persis‐
80 tently. If not specified, the default value of '<LOCALSTATE‐
81 DIR>/lib/NetworkManager/NetworkManager.state' is used; where
82 <LOCALSTATEDIR> is dependent on your distribution (usually it's
83 /var).
84 --config=<filename>
86 Specify configuration file to set up various settings for Net‐
87 workManager. If not specified, the default value of
88 '<SYSCONFDIR>/NetworkManager/NetworkManager.conf' is used with a
89 fallback to the older 'nm-system-settings.conf' if located in
90 the same directory; where <SYSCONFDIR> is dependent on your dis‐
91 tribution (usually it's /etc). See NetworkManager.conf(5) for
92 more information on configuration file.
93 --plugins=<plugin1>,<plugin2>, ...
95 List plugins used to manage system-wide connection settings.
96 This list has preference over plugins specified in the configu‐
97 ration file. Currently supported plugins are: keyfile,
98 ifcfg-rh, ifcfg-suse, ifupdown. See NetworkManager.conf(5) for
99 more information on the plugins.
100 --log-level=<level>
102 Sets how much information NetworkManager sends to the log desti‐
103 nation (usually syslog's "daemon" facility). By default, only
104 informational, warning, and error messages are logged. See Net‐
105 workManager.conf(5) for more information on log levels and
106 domains.
107 --log-domains=<domain1>,<domain2>, ...
109 Sets which operations are logged to the log destination (usually
110 syslog). By default, most domains are logging-enabled. See
111 NetworkManager.conf(5) for more information on log levels and
112 domains.
113
115 The following environment variables are supported to help debugging.
116 When used in conjunction with the "--no-daemon" option (thus echoing
117 PPP and DHCP helper output to stdout) these can quickly help pinpoint
118 the source of connection issues. Also see the --log-level and
119 --log-domains to enable debug logging inside NetworkManager itself.
120 NM_PPP_DEBUG
122 When set to anything, causes NetworkManager to turn on PPP
123 debugging in pppd, which logs all PPP and PPTP frames and
124 client/server exchanges.
125
127 nm-tool(1), NetworkManager.conf(5).
128 January 29, 2010 NETWORKMANAGER(8)