blob: c1ca75cca5e5b0e57b7042536d71b1e51571ba68 [file] [log] [blame]
.\" connman.conf(5) manual page
.\" Copyright (C) 2012 Intel Corporation
.TH "connman.conf" "5" "21 August 2012" ""
main.conf \- ConnMan configuration file
where <SYSCONFDIR> depends on your distribution or build.
.I main.conf
is a configuration file for ConnMan. The configuration file is
optional but it can be used to set up various aspects of ConnMan's
behavior. The location of the file may be changed through use of
the "\-\-config=" argument for \fBconnman\fP (8).
The configuration file format is key file format.
It consists of sections (groups) of key-value pairs.
Lines beginning with a '#' and blank lines are considered comments.
Sections are started by a header line containing the section enclosed
in '[' and ']', and ended implicitly by the start of the next section
or the end of the file. Each key-value pair must be contained in a section.
Description of sections and available keys follows:
.SS [General]
This section is the only mandatory section of the configuration file.
.B InputRequestTimeout=\fPsecs\fP
Set input request timeout. Default is 120 seconds
The request for inputs like passphrase will timeout
after certain amount of time. Use this setting to
increase the value in case of different user
interface designs.
.B BrowserLaunchTimeout=\fPsecs\fP
Set browser launch timeout. Default is 300 seconds
The request for launching a browser for portal pages
will timeout after certain amount of time. Use this
setting to increase the value in case of different
user interface designs.
.B BackgroundScanning=\fPtrue|false\fP
Enable background scanning. Default is true.
Background scanning will start every 5 minutes unless
the scan list is empty. In that case, a simple backoff
mechanism starting from 10s up to 5 minutes will run.
.B FallbackTimeservers=\fPserver1,server2,...\fP
List of Fallback timeservers separated by ",".
These timeservers are used for NTP sync when there are
no timeserver set by the user or by the service.
These can contain mixed combination of fully qualified
domain names, IPv4 and IPv6 addresses.
.B FallbackNameservers=\fPserver1,server2,...\fP
List of fallback nameservers separated by "," appended
to the list of nameservers given by the service. The
nameserver entries must be in numeric format, host
names are ignored.
.B DefaultAutoConnectTechnologies=\fPtechnology1,technology2,...\fP
List of technologies that are marked autoconnectable
by default, separated by commas ",". The default value
for this entry when empty is ethernet,wifi,cellular.
Services that are automatically connected must have been
set up and saved to storage beforehand.
.B PreferredTechnologies=\fPtechnology1,technology2,...\fP
List of preferred technologies from the most preferred
one to the least preferred one separated by commas ",".
Services of the listed technology type will be tried one
by one in the order given, until one of them gets connected
or they are all tried. A service of a preferred technology
type in state 'ready' will get the default route when
compared to another preferred type further down the list
with state 'ready' or with a non-preferred type; a service
of a preferred technology type in state 'online' will get
the default route when compared to either a non-preferred
type or a preferred type further down in the list.
.B NetworkInterfaceBlacklist=\fPinterface1,interface2,...\fP
List of blacklisted network interfaces separated by ",".
Found interfaces will be compared to the list and will
not be handled by connman, if their first characters
match any of the list entries. Default value is
.B AllowHostnameUpdates=\fPtrue|false\fP
Allow connman to change the system hostname. This can
happen for example if we receive DHCP hostname option.
Default value is true.
.B SingleConnectedTechnology=\fPtrue|false\fP
Keep only a single connected technology at any time. When a new
service is connected by the user or a better one is found according
to PreferredTechnologies, the new service is kept connected and all
the other previously connected services are disconnected. With this
setting it does not matter whether the previously connected services
are in 'online' or 'ready' states, the newly connected service is
the only one that will be kept connected. A service connected by the
user will be used until going out of network coverage. With this
setting enabled applications will notice more network breaks than
normal. Default value is false.
.B TetheringTechnologies=\fPtechnology1,technology2,...\fP
List of technologies that are allowed to enable tethering separated by ",".
The default value is wifi,bluetooth,gadget. Only those technologies listed
here are used for tethering. If one wants to tether ethernet,
then add "ethernet" in the list.
NOTE that if ethernet tethering is enabled, then a DHCP server is
started on all ethernet interfaces. Tethered ethernet should
never be connected to corporate or home network as it will disrupt
normal operation of these networks. Due to this ethernet is not
tethered by default. Do not activate ethernet tethering unless you
really know what you are doing.
.B PersistentTetheringMode=\fPtrue|false\fP
Restore earlier tethering status when returning from offline mode,
re-enabling a technology, and after restarts and reboots.
Default value is false.
.B Enable6to4=\fPtrue|false\fP
Automatically enable Anycast 6to4 if possible. This is not recommended, as the
use of 6to4 will generally lead to a severe degradation of connection quality.
See RFC6343. Default value is false (as recommended by RFC6343 section 4.1).
.BR Connman (8)