4 Copyright (C) 2007-2010 Intel Corporation. All rights reserved.
7 Functionality and features
8 ==========================
10 The following features are built-in into Connection Manager:
11 - Generic plugin infrastructure
12 - Device and network abstraction (with basic storage support)
13 - IPv4, routing and DNS configuration
15 Various plugins can be enabled for networking support:
17 - WiFi plugin with WEP40/WEP128 and WPA/WPA2 (personal only) support
20 Also plugins with additional features are available:
21 - DHCP plugins (uDHCP and dhclient)
22 - Resolver plugin (DNS proxy)
27 Compilation and installation
28 ============================
30 In order to compile Connection Manager you need following software packages:
34 - udev library (optional)
35 - PolicyKit (optional)
38 ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
40 Configure automatically searches for all required components and packages.
42 To compile and install run:
46 Configuration and options
47 =========================
49 For a working system, certain configuration options need to be enabled:
53 Enable support for Ethernet network cards
57 Enable support for WiFi devices (requires wpa_supplicant)
62 Enable support for Bluetooth devices (requires BlueZ)
66 Enable DHCP client support for BusyBox based systems
68 The location of the udhcpc binary is auto-detected, but it
69 can be overwritten via --with-udhcpc=<path-to-binary>.
73 Enable DHCP client support for ISC dhclient based systems
75 The location of the dhclient binary is auto-detected, but it
76 can be overwritten via --with-dhclient=<path-to-binary>.
78 At least one DHCP client option should be selected. It is
79 possible to select both and then uDHCP will be tried first
80 before falling back to dhclient.
84 Enable DNS proxy support for /etc/resolv.conf abstraction
86 The best solution for multiple connections and proper DNS
87 handling is a DNS proxy server. This binds a DNS proxy
88 server to port 53 on the loopback interface (127.0.0.1).
90 The /etc/resolv.conf file needs a "nameserver 127.0.0.1"
91 entry, but can now set the immutable bit or be on a read-only
92 filesystem. No further modification to that file will be made.
94 It is important that this is not used together with other
95 DNS proxy solution like dnsmasq.
99 Enable setup of loopback device
101 For distributions with a really minimal init system and no
102 networking scripts this can take care of setting up the
103 loopback device and enabling it.
105 It is safe to select this option even if networking scripts
106 are in place. It detects an already configured loopback
107 device and leaves it as it is.
111 Enable support for PolicyKit authorization
113 This allows to check every D-Bus access against a security
114 policy and so restrict access to certain functionality.