1connman.conf(5) File Formats Manual connman.conf(5)
2
6 main.conf - ConnMan configuration file
7
9 /etc/connman/main.conf
10
12 main.conf is a configuration file for ConnMan. The configuration file
13 is optional but it can be used to set up various aspects of ConnMan's
14 behavior. The location of the file may be changed through use of the
15 --config= argument for connman(8).
16
18 The configuration file format is key file format. It consists of sec‐
19 tions (groups) of key-value pairs. Lines beginning with a '#' and
20 blank lines are considered comments. Sections are started by a header
21 line containing the section enclosed in '[' and ']', and ended implic‐
22 itly by the start of the next section or the end of the file. Each key-
23 value pair must be contained in a section.
24 Description of sections and available keys follows:
26 [General]
28 This section is the only mandatory section of the configuration file.
29 InputRequestTimeout=secs
31 Set input request timeout. Default is 120 seconds The request
32 for inputs like passphrase will timeout after certain amount of
33 time. Use this setting to increase the value in case of differ‐
34 ent user interface designs.
35 BrowserLaunchTimeout=secs
37 Set browser launch timeout. Default is 300 seconds The request
38 for launching a browser for portal pages will timeout after cer‐
39 tain amount of time. Use this setting to increase the value in
40 case of different user interface designs.
41 BackgroundScanning=true | false
43 Enable background scanning. Default is true. Background scan‐
44 ning will start every 5 minutes unless the scan list is empty.
45 In that case, a simple backoff mechanism starting from 10s up to
46 5 minutes will run.
47 FallbackTimeservers=server[,...]
49 List of Fallback timeservers separated by ",". These time‐
50 servers are used for NTP sync when there are no timeserver set
51 by the user or by the service. These can contain mixed combina‐
52 tion of fully qualified domain names, IPv4 and IPv6 addresses.
53 FallbackNameservers=server[,...]
55 List of fallback nameservers separated by "," appended to the
56 list of nameservers given by the service. The nameserver entries
57 must be in numeric format, host names are ignored.
58 DefaultAutoConnectTechnologies=technology[,...]
60 List of technologies that are marked autoconnectable by default,
61 separated by commas ",". The default value for this entry when
62 empty is ethernet,wifi,cellular. Services that are automati‐
63 cally connected must have been set up and saved to storage
64 beforehand.
65 AlwaysConnectedTechnologies=technology[,...]
67 List of technoolgies which are always connected regardless of
68 PreferredTechnologies setting (AutoConnect = true). The default
69 value is empty and this feature is disabled unless explicitely
70 enabled in the config file.
71 PreferredTechnologies=technology[,...]
73 List of preferred technologies from the most preferred one to
74 the least preferred one separated by commas ",". Services of
75 the listed technology type will be tried one by one in the order
76 given, until one of them gets connected or they are all tried. A
77 service of a preferred technology type in state 'ready' will get
78 the default route when compared to another preferred type fur‐
79 ther down the list with state 'ready' or with a non-preferred
80 type; a service of a preferred technology type in state 'online'
81 will get the default route when compared to either a non-pre‐
82 ferred type or a preferred type further down in the list.
83 NetworkInterfaceBlacklist=interface[,...]
85 List of blacklisted network interfaces separated by ",". Found
86 interfaces will be compared to the list and will not be handled
87 by connman, if their first characters match any of the list
88 entries. Default value is vmnet,vboxnet,virbr,ifb.
89 AllowHostnameUpdates=true | false
91 Allow connman to change the system hostname. This can happen for
92 example if we receive DHCP hostname option. Default value is
93 true.
94 SingleConnectedTechnology=true | false
96 Keep only a single connected technology at any time. When a new
97 service is connected by the user or a better one is found
98 according to PreferredTechnologies, the new service is kept con‐
99 nected and all the other previously connected services are dis‐
100 connected. With this setting it does not matter whether the pre‐
101 viously connected services are in 'online' or 'ready' states,
102 the newly connected service is the only one that will be kept
103 connected. A service connected by the user will be used until
104 going out of network coverage. With this setting enabled appli‐
105 cations will notice more network breaks than normal. Default
106 value is false.
107 TetheringTechnologies=technology[,...]
109 List of technologies that are allowed to enable tethering sepa‐
110 rated by ",". The default value is wifi,bluetooth,gadget. Only
111 those technologies listed here are used for tethering. If one
112 wants to tether ethernet, then add "ethernet" in the list. NOTE
113 that if ethernet tethering is enabled, then a DHCP server is
114 started on all ethernet interfaces. Tethered ethernet should
115 never be connected to corporate or home network as it will dis‐
116 rupt normal operation of these networks. Due to this ethernet is
117 not tethered by default. Do not activate ethernet tethering
118 unless you really know what you are doing.
119 PersistentTetheringMode=true | false
121 Restore earlier tethering status when returning from offline
122 mode, re-enabling a technology, and after restarts and reboots.
123 Default value is false.
124 Enable6to4=true | false
126 Automatically enable Anycast 6to4 if possible. This is not rec‐
127 ommended, as the use of 6to4 will generally lead to a severe
128 degradation of connection quality. See RFC6343. Default value
129 is false (as recommended by RFC6343 section 4.1).
130 VendorClassID=string
132 Set DHCP option 60 (Vendor Class ID) to the given string. This
133 option can be used by DHCP servers to identify specific clients
134 without having to rely on MAC address ranges, etc
135 EnableOnlineCheck=true | false
137 Enable or disable use of HTTP GET as an online status check.
138 When a service is in a READY state, and is selected as default,
139 ConnMan will issue an HTTP GET request to verify that end-to-end
140 connectivity is successful. Only then the service will be tran‐
141 sitioned to ONLINE state. If this setting is false, the default
142 service will remain in READY state. Default value is true.
143
145 The following example configuration disables hostname updates and
146 enables ethernet tethering.
147 [General]
149 AllowHostnameUpdates = false
150 TetheringTechnologies = ethernet,wifi,bluetooth,gadget
151
153 connman(8)
154 2015-10-15 connman.conf(5)