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: Issues with resolving AWS IoT Thing URLs (Daniel Wagner)
2. Re: [PATCH 1/2] client: Added session create append dict
(Daniel Wagner)
----------------------------------------------------------------------
Message: 1
Date: Sun, 26 Nov 2017 21:16:39 +0100
From: Daniel Wagner <[email protected]>
To: Benjamin Walsh <[email protected]>, [email protected]
Subject: Re: Issues with resolving AWS IoT Thing URLs
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Ben,
On 11/23/2017 04:32 PM, Benjamin Walsh wrote:
> Hi,
>
> We are seeing intermittent issues when resolving AWS IoT Thing
> addresses, in the form
>
> a24sqv8kn64psq.iot.us-west-2.amazonaws.com
> <http://a24sqv8kn64psq.iot.us-west-2.amazonaws.com>
>
> iot.us-west-2.amazonaws.com <http://iot.us-west-2.amazonaws.com> always
> resolves correctly.
>
> Those Thing URLs reaolve to multiple IP addresses. It seems that connman
> times out intermittently when trying to resolve them.
Nothing obvious wrong. When it works, I see that ConnMan says it
switches over to TCP. Also the response is pretty long, maybe ConnMan
has problems with that? Hard to say without really digging into it.
Anyway, one thing you could try is to use the systemd-resolved instead
of the built-in. By using the systemd-resolved we could at least find
out if the built-in resolver is broken or not :)
> I attached the debug output from a failure case, a success case, and
> tcpdump of port 53 during a failure case. >
> Any idea what could be going wrong ?
Not really :(
Thanks
Daniel
------------------------------
Message: 2
Date: Sun, 26 Nov 2017 21:29:35 +0100
From: Daniel Wagner <[email protected]>
To: Mounesh Sutar <[email protected]>
Cc: [email protected], "Sutar, Mounesh" <[email protected]>
Subject: Re: [PATCH 1/2] client: Added session create append dict
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Mounesh,
On 11/24/2017 09:06 AM, Mounesh Sutar wrote:
> Hi,
>
> This change is a follow up of previous discussion:
> https://lists.01.org/pipermail/connman/2017-October/022198.html
> <https://lists.01.org/pipermail/connman/2017-October/022198.html>
Both patches applied. I did some smaller commit message modification and
changed the help string from 'Context Identifier' to
<context_identifier>'. I think this matches more the rest of the help
strings.
Thanks for getting this changes done! I really appreciate it!
Thanks,
Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 25, Issue 15
***************************************
