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: race between __connman_service_connect and
config_notify_handler (Vasyl Vavrychuk)
2. What is the best way to refresh connections ? (Louis Rannou)
----------------------------------------------------------------------
Message: 1
Date: Wed, 6 Dec 2017 07:20:31 +0200
From: Vasyl Vavrychuk <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: race between __connman_service_connect and
config_notify_handler
Message-ID:
<CAGj4m+7nTO-Qn20Lqz23jB39VEtPEho1Qh0Jv8ak5EH+eb=n...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi, Daniel,
I found an attempt to implement EAP parameters via D-Bus api
https://lists.01.org/pipermail/connman/2010-August/002420.html.
Could you merge proposed patch to resolve my issue or this patch should be
reworked according to some way suggested in mailing list?
Kind regards,
Vasyl
On Sun, Nov 12, 2017 at 12:05 PM, Daniel Wagner <[email protected]> wrote:
> Hi Vasyl,
>
> On 11/06/2017 11:40 PM, Vasyl Vavrychuk wrote:
>
>> I have implemented GUI for connman which in particular connects to 802.1x
>> services.
>>
>> Since for them we have to use provision file I have following simple
>> algorithm.
>>
>> 1. Write connection parameters in provision file and flush it.
>> 2. Call connman service Connect method via D-Bus.
>>
>> But it looks like sometimes I have Connect handled sooner than provision
>> file reloaded.
>>
>> I am not 100% sure, but looking at the source code I think that this
>> situation is at least theoretically possible. Isn't it?
>>
>
> I think this race is real. ConnMan uses inotify to monitor changes in the
> /var/lib/connman directory. Whenever a file is updated it will take some
> time until ConnMan sees the changes. ConnMan itself is single threaded and
> therefore all changes have been processed or they haven't.
>
> Anyway not really sure how to fix this. They only way I see is to add a
> D-Bus call which writes the provisioning to the disc. Though this idea has
> not been popular around here. I personally don't mind having such an
> extension.
>
> Thanks,
> Daniel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20171206/1e676d5e/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 6 Dec 2017 09:34:18 +0100
From: Louis Rannou <[email protected]>
To: [email protected]
Subject: What is the best way to refresh connections ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hello,
I have several network services connected. My goal is to check if the
main service is connected to the internet (able to access a portal), and
if not, switch to one connected (if there is one).
Therefore I want to implement a new service API (ex: refresh). I may
have two options :
*1/* check the main service's connection and downgrade its state to
READY. Then connman should check every service to find one online (only
with option EnableOnlineCheck).*
2/* find the first service that has a connection and move it before the
main connection.
In my opinion, the second option is easier to implement as all
mechanisms needed already exist.
To check the connection, I was thinking about using the function
/wispr_portal_request_portal(*wp_context)/.
I am not really aware about connman's logic yet, so I'm open to your
suggestions.
Regards,
Louis.
--
Logo <http://www.smile.eu/>
14 rue G?nissieu
38000 Grenoble
*Louis RANNOU*
Ing?nieur ?tudes et D?veloppement
email [email protected] <mailto:[email protected]>
url http://www.smile.eu
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20171206/20468178/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 26, Issue 4
**************************************
