test: Remove handling of no longer existing properties

[framework/connectivity/connman.git] / README

diff --git a/README b/README
index 989198c..532e327 100644 (file)
--- a/README
+++ b/README
@@ -1,7 +1,26 @@
 Connection Manager
 ******************
 
-Copyright (C) 2007-2009  Intel Corporation. All rights reserved.
+Copyright (C) 2007-2010  Intel Corporation. All rights reserved.
+
+
+Functionality and features
+==========================
+
+The following features are built-in into Connection Manager:
+       - Generic plugin infrastructure
+       - Device and network abstraction (with basic storage support)
+       - IPv4, routing and DNS configuration
+       - DNS Proxy
+
+Various plugins can be enabled for networking support:
+       - Ethernet plugin
+       - WiFi plugin with WEP40/WEP128 and WPA/WPA2 (personal only) support
+       - Bluetooth plugin
+
+Also plugins with additional features are available:
+       - Loopback setup
+       - PolicyKit support
 
 
 Compilation and installation
@@ -11,9 +30,7 @@ In order to compile Connection Manager you need following software packages:
        - GCC compiler
        - GLib library
        - D-Bus library
-       - udev library (optional)
        - PolicyKit (optional)
-       - PPP support (optional)
 
 To configure run:
        ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
@@ -24,6 +41,21 @@ To compile and install run:
        make && make install
 
 
+VPN
+===
+
+In order to compile pptp and l2tp VPN plugins, you need ppp development
+package.
+
+To run l2tp you will need
+       - xl2tpd, http://www.xelerance.com/services/software/xl2tpd
+
+To run pptp you will need
+       - pptp client, http://pptpclient.sourceforge.net
+
+Both l2tp and pptp also need pppd.
+
+
 Configuration and options
 =========================
 
@@ -42,60 +74,6 @@ For a working system, certain configuration options need to be enabled:
 
                Enable support for Bluetooth devices (requires BlueZ)
 
-       --enable-ppp
-
-               Enable PPP support for dialup connections (requires pppd)
-
-               The location of the pppd binary is auto-detected, but it
-               can be overwritten via --with-pppd=<path-to-binary>.
-
-       --enable-udhcp
-
-               Enable DHCP client support for BusyBox based systems
-
-               The location of the udhcpc binary is auto-detected, but it
-               can be overwritten via --with-udhcpc=<path-to-binary>.
-
-       --enable-dhclient
-
-               Enable DHCP client support for ISC dhclient based systems
-
-               The location of the dhclient binary is auto-detected, but it
-               can be overwritten via --with-dhclient=<path-to-binary>.
-
-               At least one DHCP client option should be selected. It is
-               possible to select both and then uDHCP will be tried first
-               before falling back to dhclient.
-
-       --enable-dnsproxy
-
-               Enable DNS proxy support for /etc/resolv.conf abstraction
-
-               The best solution for multiple connections and proper DNS
-               handling is a DNS proxy server. This binds a DNS proxy
-               server to port 53 on the loopback interface (127.0.0.1).
-
-               The /etc/resolv.conf file needs a "nameserver 127.0.0.1"
-               entry, but can now set the immutable bit or be on a read-only
-               filesystem. No further modification to that file will be made.
-
-               It is important that this is not used together with other
-               DNS proxy solution like dnsmasq.
-
-       --enable-resolvconf
-
-               Enable resolvconf support for Debian/Ubuntu based systems
-
-               The resolvconf package from Debian can be used to handle
-               configuration of the /etc/resolv.conf file.
-
-               It is safe to select this option even when resolvconf is not
-               installed. A missing resolvconf will be detected and in that
-               case it falls back to modifying /etc/resolv.conf directly.
-
-               The location of the resolvconf binary is auto-detected, but it
-               can be overwritten via --with-resolvconf=<path-to-binary>.
-
        --enable-loopback
 
                Enable setup of loopback device
@@ -108,14 +86,6 @@ For a working system, certain configuration options need to be enabled:
                are in place. It detects an already configured loopback
                device and leaves it as it is.
 
-       --enable-udev
-
-               Enable device detection support via udev
-
-               Network devices are by default detected via the builtin RTNL
-               functionality. This allows to detect TTY based modem devices
-               via udev.
-
        --enable-polkit
 
                Enable support for PolicyKit authorization