1NetworkManager.conf(5) File Formats Manual NetworkManager.conf(5)
2
6 NetworkManager.conf - NetworkManager configuration file
7
9 /etc/NetworkManager/NetworkManager.conf
10 or
11 <SYSCONFDIR>/NetworkManager/NetworkManager.conf
12 where <SYSCONFDIR> depends on your distribution or build.
13
15 NetworkManager.conf is a configuration file for NetworkManager. It is
16 used to set up various aspects of NetworkManager's behavior. The loca‐
17 tion of the file may be changed through use of the "--config=" argument
18 for NetworkManager (8).
19 It is not necessary to restart NetworkManager when making changes, as
21 the configuration file is watched for changes and reloaded automati‐
22 cally when necessary.
23
25 The configuration file format is so-called key file (sort of ini-style
26 format). It consists of sections (groups) of key-value pairs. Lines
27 beginning with a '#' and blank lines are considered comments. Sections
28 are started by a header line containing the section enclosed in '[' and
29 ']', and ended implicitly by the start of the next section or the end
30 of the file. Each key-value pair must be contained in a section.
31 Minimal system settings configuration file looks like this:
32 [main]
34 plugins=keyfile
35 Description of sections and available keys follows:
37 [main]
39 This section is the only mandatory section of the configuration file.
40 plugins=plugin1,plugin2, ...
42 List system settings plugin names separated by ','. These plug‐
43 ins are used to read/write system-wide connection. When more
44 plugins are specified, the connections are read from all listed
45 plugins. When writing connections, the plugins will be asked to
46 save the connection in the order listed here. If the first plug‐
47 in cannot write out that connection type, or can't write out any
48 connections, the next plugin is tried. If none of the plugins
49 can save the connection, the error is returned to the user.
50 Available plugins:
52 keyfile
54 plugin is the generic plugin that supports all the con‐
55 nection types and capabilities that NetworkManager has.
56 It writes files out in a .ini-style format in /etc/Net‐
57 workManager/system-connections. For security, it will
58 ignore files that are readable or writeable by any user
59 or group other than root since private keys and
60 passphrases may be stored in plaintext inside the file.
61 ifcfg-rh
63 plugin is used on the Fedora and Red Hat Enterprise Linux
64 distributions to read and write configuration from the
65 standard /etc/sysconfig/network-scripts/ifcfg-* files.
66 It currently supports reading wired, WiFi, and 802.1x
67 connections, but does not yet support reading or writing
68 mobile broadband, PPPoE, or VPN connections. To allow
69 reading and writing of these add keyfile plugin to your
70 configuration as well.
71 ifupdown
73 plugin is used on the Debian and Ubuntu distributions,
74 and reads connections from /etc/network/interfaces. Since
75 it cannot write connections out (that support isn't
76 planned), it is usually paired with the keyfile plugin to
77 enable saving and editing of new connections. The ifup‐
78 down plugin supports basic wired and WiFi connections,
79 including WPA-PSK.
80 ifcfg-suse
82 plugin is only provided for simple backward compatibility
83 with SUSE and OpenSUSE configuration. Most setups should
84 be using the keyfile plugin instead. The ifcfg-suse plug‐
85 in supports reading wired and WiFi connections, but does
86 not support saving any connection types.
87 dhcp=dhclient | dhcpcd
89 This key sets up what DHCP client NetworkManager will use.
90 Presently dhclient and dhcpcd are supported. The client config‐
91 ured here should be available on your system too. If this key is
92 missing, available DHCP clients are looked for in this order:
93 dhclient, dhcpcd.
94 no-auto-default=<hwaddr>,<hwaddr>,... | *
96 Set devices for which NetworkManager shouldn't create default
97 wired connection (Auto eth0). NetworkManager creates a default
98 wired connection for any wired device that is managed and
99 doesn't have a connection configured. List a device in this
100 option to inhibit creating the default connection for the
101 device.
102 When the default wired connection is deleted or saved to a new
103 persistent connection by a plugin, the MAC address of the wired
104 device is automatically added to this list to prevent creating
105 the default connection for that device again. Devices are spec‐
106 ified by their MAC addresses, in lowercase. Multiple entries are
107 separated by commas. You can use the glob character * instead of
108 listing addresses to specify all devices.
109 Examples:
110 no-auto-default=00:22:68:5c:5d:c4,00:1e:65:ff:aa:ee
111 no-auto-default=*
112 dns=plugin1,plugin2, ...
114 List DNS plugin names separated by ','. DNS plugins are used to
115 provide local caching nameserver functionality (which speeds up
116 DNS queries) and to push DNS data to applications that use it.
117 Available plugins:
119 dnsmasq
121 this plugin uses dnsmasq to provide local caching name‐
122 server functionality.
123 [keyfile]
125 This section contains keyfile-specific options and thus only has effect
126 when using keyfile plugin.
127 hostname=<hostname>
129 Set a persistent hostname when using the keyfile plugin.
130 unmanaged-devices=mac:<hwaddr>;mac:<hwaddr>;...
132 Set devices that should be ignored by NetworkManager when using
133 the keyfile plugin. Devices are specified in the following for‐
134 mat: "mac:<hwaddr>", where <hwaddr> is MAC address of the device
135 to be ignored, in hex-digits-and-colons notation. Multiple
136 entries are separated by a semicolon. No spaces are allowed in
137 the value.
138 Example:
139 unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4
140 [ifupdown]
142 This section contains ifupdown-specific options and thus only has
143 effect when using ifupdown plugin.
144 managed=false | true
146 Controls whether interfaces listed in the 'interfaces' file are
147 managed by NetworkManager. If set to true, then interfaces
148 listed in /etc/network/interfaces are managed by NetworkManager.
149 If set to false, then any interface listed in /etc/net‐
150 work/interfaces will be ignored by NetworkManager. Remember that
151 NetworkManager controls the default route, so because the inter‐
152 face is ignored, NetworkManager may assign the default route to
153 some other interface. When the option is missing, false value
154 is taken as default.
155 [logging]
157 This section controls NetworkManager's logging. Any settings here are
158 overridden by the --log-level and --log-domains command-line options.
159 level=<level>
161 One of [ERR, WARN, INFO, DEBUG]. The ERR level logs only criti‐
162 cal errors. WARN logs warnings that may reflect operation.
163 INFO logs various informational messages that are useful for
164 tracking state and operations. DEBUG enables verbose logging
165 for debugging purposes. Subsequent levels also log all messages
166 from earlier levels; thus setting the log level to INFO also
167 logs error and warning messages.
168 domains=<domain1>,<domain2>, ...
170 The following log domains are available: [NONE, HW, RFKILL,
171 ETHER, WIFI, BT, MB, DHCP4, DHCP6, PPP, WIFI_SCAN, IP4, IP6,
172 AUTOIP4, DNS, VPN, SHARING, SUPPLICANT, USER_SET, SYS_SET, SUS‐
173 PEND, CORE, DEVICE, OLPC]. When "NONE" is given by itself, log‐
174 ging is disabled. MB = Mobile Broadband, USER_SET = user set‐
175 tings operations and communication, SYS_SET = system settings
176 service operations, OLPC = OLPC Mesh device operations, CORE =
177 core daemon operations, DEVICE = activation and general inter‐
178 face operations.
179
181 http://live.gnome.org/NetworkManager/SystemSettings
182 NetworkManager(8), nm-tool(1).
184 23 November 2010 NetworkManager.conf(5)