Release 0.80

[framework/connectivity/connman.git] / README

diff --git a/README b/README
index 163cef9..532e327 100644 (file)
--- a/README
+++ b/README
@@ -11,6 +11,7 @@ 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
@@ -18,8 +19,6 @@ Various plugins can be enabled for networking support:
        - Bluetooth plugin
 
 Also plugins with additional features are available:
-       - DHCP plugins (uDHCP and dhclient)
-       - Resolver plugins (resolvconf and DNS proxy)
        - Loopback setup
        - PolicyKit support
 
@@ -31,7 +30,6 @@ In order to compile Connection Manager you need following software packages:
        - GCC compiler
        - GLib library
        - D-Bus library
-       - udev library (optional)
        - PolicyKit (optional)
 
 To configure run:
@@ -43,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
 =========================
 
@@ -61,53 +74,6 @@ For a working system, certain configuration options need to be enabled:
 
                Enable support for Bluetooth devices (requires BlueZ)
 
-       --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