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: [PATCH 0/2] stop scan on p2p technology disable
(Daniel Wagner)
2. Re: [PATCH] wifi: Avoid interface's state machine moves
forward with P2P networks (Daniel Wagner)
3. Re: [PATCH 0/2] stop scan on p2p technology disable
(Vasyl Vavrychuk)
4. Re: race between __connman_service_connect and
config_notify_handler (Daniel Wagner)
5. Re: [PATCH 0/2] stop scan on p2p technology disable
(Daniel Wagner)
6. Re: [PATCH] Wait 4 seconds for RA before re-sending RS
messages. (Daniel Wagner)
7. Re: [PATCH] peer: Do not notify state changes when peer is
not registered yet (Daniel Wagner)
8. How can one specify what wired and wireless interfaces to
use? (KARBOWSKI Piotr)
----------------------------------------------------------------------
Message: 1
Date: Mon, 18 Dec 2017 21:57:05 +0100
From: Daniel Wagner <[email protected]>
To: Vasyl Vavrychuk <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH 0/2] stop scan on p2p technology disable
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Vasyl,
On 12/08/2017 03:19 PM, Vasyl Vavrychuk wrote:
> Vasyl Vavrychuk (2):
> device: add stop_scan method to device interface
> wifi: stop scan on p2p technology disable
I spitted the two patches a bit more and fixed a couple of 80 character
limits. We tend to do baby steps in ConnMan, with the goal to simplify
the review etc.
Thanks,
Daniel
------------------------------
Message: 2
Date: Mon, 18 Dec 2017 21:59:39 +0100
From: Daniel Wagner <[email protected]>
To: [email protected], [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH] wifi: Avoid interface's state machine moves
forward with P2P networks
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Jose,
On 12/10/2017 07:25 PM, [email protected] wrote:
> From: Jose Blanquicet <[email protected]>
>
> When P2P is connecting and the other device acts as Group owner then it
> is not needed to handle interface state changes G_SUPPLICANT_STATE_*
> because the P2P connection success is completely based on the peer state
> CONNMAN_PEER_STATE_*. Therefore, do not treat interface state changes
> during a P2P connection, otherwise it could result in an inconsistency.
>
> Check wifi->p2p_device will handle system's configuration where the P2P
> group interface is created and wifi->p2p_connecting where it is not.
>
> Reported-by: Saurav Babu <[email protected]>
Patch applied.
Thanks,
Daniel
------------------------------
Message: 3
Date: Mon, 18 Dec 2017 22:59:54 +0200
From: Vasyl Vavrychuk <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH 0/2] stop scan on p2p technology disable
Message-ID:
<cagj4m+4d_gza-8mzojbd-ujrvf44ccum_xks3se9rd_rbps...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thank you. I look nicer after that.
On Mon, Dec 18, 2017 at 10:57 PM, Daniel Wagner <[email protected]> wrote:
> Hi Vasyl,
>
> On 12/08/2017 03:19 PM, Vasyl Vavrychuk wrote:
>
>> Vasyl Vavrychuk (2):
>> device: add stop_scan method to device interface
>> wifi: stop scan on p2p technology disable
>>
>
> I spitted the two patches a bit more and fixed a couple of 80 character
> limits. We tend to do baby steps in ConnMan, with the goal to simplify the
> review etc.
>
> Thanks,
> Daniel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20171218/7d240df4/attachment-0001.html>
------------------------------
Message: 4
Date: Mon, 18 Dec 2017 22:04:20 +0100
From: Daniel Wagner <[email protected]>
To: Vasyl Vavrychuk <[email protected]>, [email protected]
Subject: Re: race between __connman_service_connect and
config_notify_handler
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Vasyl,
On 12/12/2017 01:39 AM, Vasyl Vavrychuk wrote:
> Hi,
>
> I want to develop demo of using Provisioning property in JSON format.
> For this I need JSON parser but when I use JSON Glib I am getting conflicts
>
> In file included from /usr/include/glib-2.0/gio/gio.h:26:0,
> ? ? ? ? ? ? ? ? ?from
> /usr/include/json-glib-1.0/json-glib/json-generator.h:32,
> ? ? ? ? ? ? ? ? ?from /usr/include/json-glib-1.0/json-glib/json-glib.h:32,
> ? ? ? ? ? ? ? ? ?from src/service.c:33:
> /usr/include/glib-2.0/gio/giotypes.h:546:47: error: conflicting types
> for ?GDBusProxy?
> ?typedef struct _GDBusProxy? ? ? ? ? ? ? ? ? ? GDBusProxy;
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?^~~~~~~~~~
> In file included from src/service.c:30:0:
>
> Does this means that I can not use JSON Glib?
Oh, I didn't realize that the glib JSON parser has a dependency to GIO
and as you found out will not work with ConnMan.
We didn't want to introduce the object model of the GNOME libraries.
That's why we never used those parts of the glib.
I fear you need to use an other JSON implementation.
Thanks,
Daniel
------------------------------
Message: 5
Date: Mon, 18 Dec 2017 22:06:00 +0100
From: Daniel Wagner <[email protected]>
To: Vasyl Vavrychuk <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH 0/2] stop scan on p2p technology disable
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 12/18/2017 09:59 PM, Vasyl Vavrychuk wrote:
> Thank you. I look nicer after that.
I wanted to play with magit under emacs anyway. So your patches were my
test object :)
Thanks,
Daniel
------------------------------
Message: 6
Date: Mon, 18 Dec 2017 22:09:24 +0100
From: Daniel Wagner <[email protected]>
To: Niraj Kumar Goit <[email protected]>, [email protected]
Cc: [email protected]
Subject: Re: [PATCH] Wait 4 seconds for RA before re-sending RS
messages.
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Niraj,
On 12/13/2017 11:37 AM, Niraj Kumar Goit wrote:
> As per RFC 4861, a host should transmit up to 3 Router Solicitation
> messages, each separated by at least RTR_SOLICITATION_INTERVAL(4)
> seconds to obtain RA for IPv6 auto-configuration.
Patch applied.
Thanks,
Daniel
------------------------------
Message: 7
Date: Mon, 18 Dec 2017 22:35:33 +0100
From: Daniel Wagner <[email protected]>
To: Vasyl Vavrychuk <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] peer: Do not notify state changes when peer is
not registered yet
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Vasyl,
On 12/15/2017 05:57 AM, Vasyl Vavrychuk wrote:
> Hi, Daniel,
>
> I have found that situation with this issue is more interesting.
>
> On Thu, Dec 7, 2017 at 10:16 AM, Daniel Wagner <[email protected]
> <mailto:[email protected]>> wrote:
>
> Could you try this and see if everything is still okay after the added
> ref/unref?
>
>
> Actually for?__connman_agent_report_peer_error
> ->?connman_agent_report_error_full ->?connman_agent_queue_message last
> function perform ref for user_context and then?agent_request_free
> perform unref.
>
> There is a bit problem that actually passed structure to
> context_ref/unref is connman_peer but agent_driver treats it as
> connman_service.
Urgs, that would be really wrong thing to do. I didn't find the place
where we hand in connman_peer as user_data.
> But theoretically it should still work because refcount
> field is not the same position and it should be always >= 2 during unref
> because connman_peer_unregister performs agent cancel.
If this is the case, it is a serious bug.
> Now I do not know why this issue happens...
Hard to say what's going wrong bug I think you are pretty close from
your report.
Thanks,
Daniel
ps: Please send text only message to mailing list.
------------------------------
Message: 8
Date: Tue, 19 Dec 2017 19:33:27 +0100
From: KARBOWSKI Piotr <[email protected]>
To: [email protected]
Subject: How can one specify what wired and wireless interfaces to
use?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hello,
I'd like to ask, how can one specify what interfaces should be used?
I see that I can start `connmand` with `-i` and `-I` switches and I
could use that to omit devices, but that's a bit problematic.
If I have two wireless cards, wlan0 and wlan1, how can I choose which to
use to connect? I'd like to connect with wlan0 to one network and with
wlan1 to another.
-- Piotr.
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 26, Issue 18
***************************************
