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: [RFC v2 0/6] Move resolv.conf to /run/connman (Patrik Flykt)
2. Re: [RFC] connman.service: Restrict capabilities (Patrik Flykt)
3. Re: [PATCH] Ensure that NameServer ordering is correct when
not using the DNS proxy (Patrik Flykt)
4. Re: [PATCH 0/5 v2] Properly configure search domains for
resolvers (Patrik Flykt)
5. [PATCH] service: Set search domains regardless of connected
state (Patrik Flykt)
----------------------------------------------------------------------
Message: 1
Date: Wed, 25 Nov 2015 13:36:10 +0200
From: Patrik Flykt <[email protected]>
To: [email protected]
Subject: Re: [RFC v2 0/6] Move resolv.conf to /run/connman
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
On Tue, 2015-11-24 at 14:28 +0200, Patrik Flykt wrote:
> Hi,
>
> Here's an updated RFC set for moving resolv.conf to /run/connman.
>
> The update to ConnMan is that it first tries to write to
> [/var]/run/connman/resolv.conf. If it fails, /etc/resolv.conf is used instead.
>
> The tmpfiles configuration file and init script now create the directory
> [/var]/run/connman/resolv.conf.
>
> When this is done, the file system access can be restricted with patch 6.
Applied all six patches.
Patrik
------------------------------
Message: 2
Date: Wed, 25 Nov 2015 13:36:48 +0200
From: Patrik Flykt <[email protected]>
To: [email protected]
Subject: Re: [RFC] connman.service: Restrict capabilities
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
On Tue, 2015-11-24 at 15:25 +0200, Patrik Flykt wrote:
> Restrict the set of capabilities to the ones needed for normal operation
> in the systemd unit file.
Rebased and applied.
Patrik
------------------------------
Message: 3
Date: Wed, 25 Nov 2015 13:40:25 +0200
From: Patrik Flykt <[email protected]>
To: connman <[email protected]>
Subject: Re: [PATCH] Ensure that NameServer ordering is correct when
not using the DNS proxy
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
On Mon, 2015-11-02 at 15:08 +0000, Sam Nazarko wrote:
> ---
> src/resolver.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
When applying, I only get:
Applying: Ensure that NameServer ordering is correct when not using the
DNS proxy
error: patch failed: src/resolver.c:91
error: src/resolver.c: patch does not apply
If I try to apply it using patch -p1 I get:
patching file src/resolver.c
Hunk #1 FAILED at 91.
1 out of 1 hunk FAILED -- saving rejects to file src/resolver.c.rej
Cheers,
Patrik
> diff --git a/src/resolver.c b/src/resolver.c
> index 6a64938..5f08ce3 100644
> --- a/src/resolver.c
> +++ b/src/resolver.c
> @@ -91,15 +91,9 @@ static int resolvfile_export(void)
>
> content = g_string_new("# Generated by Connection Manager\n");
>
> - /*
> - * Domains and nameservers are added in reverse so that the most
> - * recently appended entry is the primary one. No more than
> - * MAXDNSRCH/MAXNS entries are used.
> - */
> -
> - for (count = 0, list = g_list_last(resolvfile_list);
> + for (count = 0, list = g_list_first(resolvfile_list);
> list && (count < MAXDNSRCH);
> - list = g_list_previous(list))
> {
> + list = g_list_next(list)) {
> struct resolvfile_entry *entry = list->data;
>
> if (!entry->domain)
> --
> 2.1.0
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.connman.net/mailman/listinfo/connman
------------------------------
Message: 4
Date: Wed, 25 Nov 2015 15:29:22 +0200
From: Patrik Flykt <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [PATCH 0/5 v2] Properly configure search domains for
resolvers
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
On Tue, 2015-11-24 at 22:18 +0200, [email protected] wrote:
> From: Pasi Sj?holm <[email protected]>
>
> While debugging append_domain issue reported Vladimir Pavljuchenkov
> I noticed that dnsproxy did not do any appended_domain-queries with
> nameserver/resolvers configured by IPv6-infrastructure.
>
> After these five small patches the things seems to be right
> and all the resolvers are queried with configured search domains
> (DNSSL, DHCPv4/6 and manually configured).
>
> DHCPv4/6: siirappi.com
> DNSSL: google.com
Applied, many thanks!
Patrik
------------------------------
Message: 5
Date: Wed, 25 Nov 2015 16:31:36 +0200
From: Patrik Flykt <[email protected]>
To: [email protected]
Subject: [PATCH] service: Set search domains regardless of connected
state
Message-ID:
<[email protected]>
Search domains will be added before the service gets connected, thus
allow them to be set. The interface index ensures that correct search
domains will be used. This change also fixes issues where search domains
were not appended correctly to the DNS lookups.
Reported by Mike Purvis.
---
src/service.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/src/service.c b/src/service.c
index e3317dd..be38364 100644
--- a/src/service.c
+++ b/src/service.c
@@ -1027,9 +1027,6 @@ static int searchdomain_add_all(struct connman_service
*service)
{
int index, i = 0;
- if (!is_connected(service))
- return -ENOTCONN;
-
index = __connman_service_get_index(service);
if (index < 0)
return -ENXIO;
--
2.1.4
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 1, Issue 6
*************************************
