Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: wifi scan failing on ubuntu (Vasyl Vavrychuk)
2. [PATCH 1/2] Install DBus policy in /usr/share/dbus-1/system.d
(Jonas Bonn)
3. [PATCH 2/2] Don't forceably overwrite /etc/resolv.conf
(Jonas Bonn)
4. [PATCH] gresolv: ignore valid dns response with no answer
(Eliott Dumeix)
----------------------------------------------------------------------
Message: 1
Date: Wed, 20 Dec 2017 00:32:44 +0200
From: Vasyl Vavrychuk <[email protected]>
To: [email protected]
Subject: Re: wifi scan failing on ubuntu
Message-ID:
<cagj4m+6kwmjwaem_thitw6juukstwj3s9iojpymkrma4m9s...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
Could you please make sure that network manager is not running: systemctl
status NetworkManager
I had maybe similar problem to your. To debug it I wanted to build
wpa_supplicant by myself with some prints but I found issue disappeared
after that. You can try it by yourself
apt install build-essential devscripts ccache
apt build-dep wpa_supplicant
cd wpa
debuild -b -us -uc
dpkg -i ../package.deb
Kind regards,
Vasyl
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20171220/5607ac43/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 20 Dec 2017 11:24:31 +0100
From: Jonas Bonn <[email protected]>
To: [email protected]
Subject: [PATCH 1/2] Install DBus policy in /usr/share/dbus-1/system.d
Message-ID: <[email protected]>
The default location for DBus policy files should be
/usr/share/dbus-1/system.d and the corresponding directory under /etc
should be reserved for administrative changes to default/packaged
settings. This removes a dependency of connman on a populated /etc.
---
configure.ac | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure.ac b/configure.ac
index 4feccc08..3cdf4b29 100644
--- a/configure.ac
+++ b/configure.ac
@@ -230,9 +230,9 @@ AC_SUBST(DBUS_LIBS)
AC_ARG_WITH(dbusconfdir, AC_HELP_STRING([--with-dbusconfdir=PATH],
[path to D-Bus config directory]), [path_dbusconf=${withval}],
- [path_dbusconf="`$PKG_CONFIG --variable=sysconfdir dbus-1`"])
+ [path_dbusconf="`$PKG_CONFIG --variable=datadir dbus-1`"])
if (test -z "${path_dbusconf}"); then
- DBUS_CONFDIR="${sysconfdir}/dbus-1/system.d"
+ DBUS_CONFDIR="${datadir}/dbus-1/system.d"
else
DBUS_CONFDIR="${path_dbusconf}/dbus-1/system.d"
fi
--
2.14.1
------------------------------
Message: 3
Date: Wed, 20 Dec 2017 11:24:32 +0100
From: Jonas Bonn <[email protected]>
To: [email protected]
Subject: [PATCH 2/2] Don't forceably overwrite /etc/resolv.conf
Message-ID: <[email protected]>
Using L+ in the tmpfiles.d snippet is overly aggressive. These snippets
are evaluated on every boot and may be evaluated on package upgrade.
It's fine to check that the file /etc/resolv.conf exists, but forceably
overwriting an existing file or link makes it difficult for connman to
co-exist with other potential managers of /etc/resolv.conf.
:
---
scripts/connman_resolvconf.conf.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/connman_resolvconf.conf.in
b/scripts/connman_resolvconf.conf.in
index 2d61dfe1..a242d7bc 100644
--- a/scripts/connman_resolvconf.conf.in
+++ b/scripts/connman_resolvconf.conf.in
@@ -1,2 +1,2 @@
d @runstatedir@/connman - - - -
-L+ /etc/resolv.conf - - - - @runstatedir@/connman/resolv.conf
+L /etc/resolv.conf - - - - @runstatedir@/connman/resolv.conf
--
2.14.1
------------------------------
Message: 4
Date: Wed, 20 Dec 2017 17:28:35 +0100
From: Eliott Dumeix <[email protected]>
To: [email protected]
Subject: [PATCH] gresolv: ignore valid dns response with no answer
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
A dns response may return NOERROR status code with no answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3924
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
It means one or more resource records exist for this domain but
there isn?t a record matching the resource record type.
In this case, a G_RESOLV_RESULT_STATUS_SUCCESS was returned with an
empty results array.
---
gweb/gresolv.c | 7 +++++--
gweb/gresolv.h | 5 +++++
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/gweb/gresolv.c b/gweb/gresolv.c
index 8a51a9f6..35d518ca 100644
--- a/gweb/gresolv.c
+++ b/gweb/gresolv.c
@@ -511,7 +511,7 @@ static void sort_and_return_results(struct resolv_lookup
*lookup)
status = lookup->ipv4_status;
}
- debug(lookup->resolv, "lookup %p received %d results", lookup, n);
+ debug(lookup->resolv, "lookup %p received %d results", lookup, n-1);
g_queue_remove(lookup->resolv->lookup_queue, lookup);
destroy_lookup(lookup);
@@ -679,7 +679,10 @@ static void parse_response(struct resolv_nameserver
*nameserver,
switch (rcode) {
case ns_r_noerror:
- status = G_RESOLV_RESULT_STATUS_SUCCESS;
+ if (count > 0)
+ status = G_RESOLV_RESULT_STATUS_SUCCESS;
+ else
+ status = G_RESOLV_RESULT_STATUS_NO_ANSWER;
break;
case ns_r_formerr:
status = G_RESOLV_RESULT_STATUS_FORMAT_ERROR;
diff --git a/gweb/gresolv.h b/gweb/gresolv.h
index fac14f54..23c2a9bf 100644
--- a/gweb/gresolv.h
+++ b/gweb/gresolv.h
@@ -44,6 +44,11 @@ typedef enum {
G_RESOLV_RESULT_STATUS_NAME_ERROR,
G_RESOLV_RESULT_STATUS_NOT_IMPLEMENTED,
G_RESOLV_RESULT_STATUS_REFUSED,
+ /*
+ * It means one or more resource records exist for this domain but there
+ * isn?t a record matching the resource record type.
+ */
+ G_RESOLV_RESULT_STATUS_NO_ANSWER,
} GResolvResultStatus;
typedef void (*GResolvResultFunc)(GResolvResultStatus status,
--
2.13.6
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 26, Issue 19
***************************************
