From 6b2381a2adabea7d8309ff158ef675ff88184305 Mon Sep 17 00:00:00 2001 From: Nishant Chaprana Date: Thu, 4 Jul 2019 17:41:09 +0530 Subject: Imported Upstream version 1.37 Change-Id: Ib5957e7ee3a9315ee86a331189bc3e9e71751ee8 Signed-off-by: Nishant Chaprana --- README | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) (limited to 'README') diff --git a/README b/README index cff3131e..f16b9ec0 100644 --- 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, IPv4-LL (link-local) and DHCP + - IPv4 address conflict detection (ACD) according to RFC 5227 - IPv6, DHCPv6 and 6to4 tunnels - Advanced routing and DNS configuration - Built-in DNS proxy and intelligent caching @@ -220,6 +221,16 @@ For a working system, certain configuration options need to be enabled: # semodule -i connman-task.pp in order to enable the dbus access. + --with-dns-backend=TYPE + + Enable support for a DNS resolving backend + + Select a DNS backend to use. Supported values are "internal" + and "systemd-resolved". If "internal" is selected, ConnMan + will be build with a caching DNS proxy. If "systemd-resolved" + is selected, ConnMan configures systemd-resolved to do DNS + resolving. The default value is "internal". + Activating debugging ==================== @@ -327,7 +338,10 @@ If wpa_supplicant is configured to D-Bus autostart, then ConnMan will trigger the autostart of wpa_supplicant. However please keep in mind that this trigger only happens once. If wpa_supplicant stops or crashes, ConnMan does not periodically try to autostart it. It is up to systemd or -similar service management tool to autostart it. +similar service management tool to autostart it. In case wpa_supplicant +is not started by ConnMan then make sure option "-u" is used in order +to enable its D-Bus control interface and ensure ConnMan can communicate +with it. VPN -- cgit v1.2.3