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
21 The configuration file format is so-called key file (sort of ini-style
22 format). It consists of sections (groups) of key-value pairs. Lines
23 beginning with a '#' and blank lines are considered comments. Sections
24 are started by a header line containing the section enclosed in '[' and
25 ']', and ended implicitly by the start of the next section or the end
26 of the file. Each key-value pair must be contained in a section.
27 Minimal system settings configuration file looks like this:
28 [main]
30 plugins=keyfile
31 Description of sections and available keys follows:
33 [main]
35 This section is the only mandatory section of the configuration file.
36 plugins=plugin1,plugin2, ...
38 List plugin names separated by ','. Plugins are used to
39 read/write system-wide connection. When more plugins are speci‐
40 fied, the connections are read from all listed plugins. When
41 writing connections, the plugins will be asked to save the con‐
42 nection in the order listed here. If the first plugin cannot
43 write out that connection type, or can't write out any connec‐
44 tions, the next plugin is tried. If none of the plugins can
45 save the connection, the error is returned to the user.
46 Available plugins:
48 keyfile
50 plugin is the generic plugin that supports all the con‐
51 nection types and capabilities that NetworkManager has.
52 It writes files out in a .ini-style format in /etc/Net‐
53 workManager/system-connections. For security, it will
54 ignore files that are readable or writeable by any user
55 or group other than root since private keys and
56 passphrases may be stored in plaintext inside the file.
57 ifcfg-rh
59 plugin is used on the Fedora and Red Hat Enterprise Linux
60 distributions to read and write configuration from the
61 standard /etc/sysconfig/network-scripts/ifcfg-* files.
62 It currently supports reading wired, WiFi, and 802.1x
63 connections, but does not yet support reading or writing
64 mobile broadband, PPPoE, or VPN connections. To allow
65 reading and writing of these add keyfile plugin to your
66 configuration as well.
67 ifupdown
69 plugin is used on the Debian and Ubuntu distributions,
70 and reads connections from /etc/network/interfaces. Since
71 it cannot write connections out (that support isn't
72 planned), it is usually paired with the keyfile plugin to
73 enable saving and editing of new connections. The ifup‐
74 down plugin supports basic wired and WiFi connections,
75 including WPA-PSK.
76 ifcfg-suse
78 plugin is only provided for simple backward compatibility
79 with SUSE and OpenSUSE configuration. Most setups should
80 be using the keyfile plugin instead. The ifcfg-suse plug‐
81 in supports reading wired and WiFi connections, but does
82 not support saving any connection types.
83 dhcp=dhclient | dhcpcd
85 This key sets up what DHCP client NetworkManager will use.
86 Presently dhclient and dhcpcd are supported. The client config‐
87 ured here should be available on your system too. If this key is
88 missing, available DHCP clients are looked for in this order:
89 dhclient, dhcpcd.
90 no-auto-default=<hwaddr>,<hwaddr>,...
92 Set devices for which NetworkManager shouldn't create default
93 wired connection (Auto eth0). NetworkManager creates a default
94 wired connection for any wired device that is managed and
95 doesn't have a connection configured. List a device in this
96 option to inhibit creating the default connection for the
97 device.
98 When the default wired connection is deleted or saved to a new
99 persistent connection by a plugin, the MAC address of the wired
100 device is automatically added to this list to prevent creating
101 the default connection for that device again. Devices are spec‐
102 ified by their MAC addresses, in lowercase. Multiple entries are
103 separated by commas.
104 Example:
105 no-auto-default=00:22:68:5c:5d:c4,00:1e:65:ff:aa:ee
106 wifi-wext-only=false | true
108 This option controls NetworkManager's interaction with wpa_sup‐
109 plicant (8). When false (default), 'nl80211' supplicant driver
110 and background scanning are used. This enables seamless connec‐
111 tion and roaming in RSA token-enabled Wi-Fi networks. If you
112 encounter any problems with 'nl80211' (e.g. due to bad drivers),
113 you can switch back to 'wext' supplicant driver by setting this
114 option to true. Missing option or an unrecognized value is
115 regarded as false.
116 dns=default | none
118 When set to default, NetworkManager updates system DNS configu‐
119 ration by writing to /etc/resolv.conf. If set to none Network‐
120 Manager does not update DNS configuration. Missing option or an
121 unrecognized value is regarded as default.
122 [keyfile]
124 This section contains keyfile-specific options and thus only has effect
125 when using keyfile plugin.
126 hostname=<hostname>
128 Set a persistent hostname when using the keyfile plugin.
129 unmanaged-devices=mac:<hwaddr>;mac:<hwaddr>;...
131 Set devices that should be ignored by NetworkManager when using
132 the keyfile plugin. Devices are specified in the following for‐
133 mat: "mac:<hwaddr>", where <hwaddr> is MAC address of the device
134 to be ignored, in lowercase. Multiple entries are separated by a
135 semicolon. Example:
136 unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1e:65:30:d1:c4
137 [ifupdown]
139 This section contains ifupdown-specific options and thus only has
140 effect when using ifupdown plugin.
141 managed=false | true
143 Controls whether interfaces listed in the 'interfaces' file are
144 managed by NetworkManager. If set to true, then interfaces
145 listed in /etc/network/interfaces are managed by NetworkManager.
146 If set to false, then any interface listed in /etc/net‐
147 work/interfaces will be ignored by NetworkManager. Remember that
148 NetworkManager controls the default route, so because the inter‐
149 face is ignored, NetworkManager may assign the default route to
150 some other interface. When the option is missing, false value
151 is taken as default.
152 [logging]
154 This section controls NetworkManager's logging. Any settings here are
155 overridden by the --log-level and --log-domains command-line options.
156 level=<level>
158 One of [ERR, WARN, INFO, DEBUG]. The ERR level logs only criti‐
159 cal errors. WARN logs warnings that may reflect operation.
160 INFO logs various informational messages that are useful for
161 tracking state and operations. DEBUG enables verbose logging
162 for debugging purposes. Subsequent levels also log all messages
163 from earlier levels; thus setting the log level to INFO also
164 logs error and warning messages.
165 domains=<domain1>,<domain2>, ...
167 The following log domains are available: [NONE, HW, RFKILL,
168 ETHER, WIFI, BT, MB, DHCP4, DHCP6, PPP, WIFI_SCAN, IP4, IP6,
169 AUTOIP4, DNS, VPN, SHARING, SUPPLICANT, USER_SET, SYS_SET, SUS‐
170 PEND, CORE, DEVICE, OLPC]. When "NONE" is given by itself, log‐
171 ging is disabled. MB = Mobile Broadband, USER_SET = user set‐
172 tings operations and communication, SYS_SET = system settings
173 service operations, OLPC = OLPC Mesh device operations, CORE =
174 core daemon operations, DEVICE = activation and general inter‐
175 face operations.
176
178 http://live.gnome.org/NetworkManager/SystemSettings
179 NetworkManager(8), nm-tool(1), nmcli(1).
181 26 July 2011 NetworkManager.conf(5)