On Tue, 2015-10-13 at 14:42 -0700, Naveen Singh wrote:
> There is nothing that application knows that connman does not know.
> In fact application gets to know through connman that connection did
> not go through. The way application gets connected back is to initiate
> a scan and hoping that one
On Oct 13, 2015, at 11:01 PM, Patrik Flykt wrote:
> On Tue, 2015-10-13 at 14:42 -0700, Naveen Singh wrote:
>
>> There is nothing that application knows that connman does not know.
>> In fact application gets to know through connman that connection did
>> not go
Hi,
On Tue, 2015-10-13 at 23:24 -0700, Grant Erickson wrote:
> Due to these constraints, the application knows best when to scan and
> does so at its discretion. Neither connman nor wpa_s autoscan
> infrastructure scan at the application-desired times. When they do
> scan automatically,
Hi,
On Mon, 2015-10-12 at 21:46 -0700, Naveen Singh wrote:
> In my previous email when I meant *"**User could be initiating scan" *I
> actually meant "*Application could be initiating scan".*
Well, don't. Now the responsibility of correct behavior is taken away
from ConnMan and placed
On Tue, Oct 13, 2015 at 1:00 AM, Patrik Flykt
wrote:
>
> Hi,
>
> On Mon, 2015-10-12 at 21:46 -0700, Naveen Singh wrote:
> > In my previous email when I meant *"**User could be initiating scan" *I
> > actually meant "*Application could be initiating scan".*
>
Hi,
On Fri, 2015-10-09 at 10:52 -0700, Naveen Singh wrote:
> This may not happen at all. My understanding is that wpa_supplicant would
> time out only if the AP is not seen in subsequent scans. But the AP is
> always found in scan as there is nothing wrong at 802.11 level. The user
>
On Mon, Oct 12, 2015 at 6:31 AM, Patrik Flykt
wrote:
>
> Hi,
>
> On Fri, 2015-10-09 at 10:52 -0700, Naveen Singh wrote:
> > This may not happen at all. My understanding is that wpa_supplicant would
> > time out only if the AP is not seen in subsequent scans.
In my previous email when I meant *"**User could be initiating scan" *I
actually meant "*Application could be initiating scan".*
On Mon, Oct 12, 2015 at 10:38 AM, Naveen Singh wrote:
>
>
> On Mon, Oct 12, 2015 at 6:31 AM, Patrik Flykt <
> patrik.fl...@linux.intel.com>
Hi,
On Thu, 2015-10-08 at 13:25 -0700, Naveen Singh wrote:
> I looked into the code and the documentation and I do not see any way for
> service to go back to idle (even clearing the error property). I am not
> sure how devices which are supposed to auto-connect handle this?
This all
On Thu, 2015-10-08 at 13:30 -0700, Naveen Singh wrote:
> 5. Now it is in failure state and will never be able to connect.
It will be autoconnected once its state is no longer failure. The
failure state is cleared once the service is removed. The service is
removed once wpa_supplicant times out
Hi Patrik,
On Fri, Oct 9, 2015 at 1:13 AM, Patrik Flykt
wrote:
> On Thu, 2015-10-08 at 13:30 -0700, Naveen Singh wrote:
> > 5. Now it is in failure state and will never be able to connect.
>
> It will be autoconnected once its state is no longer failure. The
>
Hi,
On Wed, 2015-10-07 at 21:21 -0700, Naveen Singh wrote:
> I have few questions about service state transition to failure:
>
> 1. Can service state transition to Failure w/o generating an error event? I
> am seeing that WiFi connection is not going through even if the
Hi Patrik
Thanks for your response.
On Thu, Oct 8, 2015 at 6:20 AM, Patrik Flykt <patrik.fl...@linux.intel.com>
wrote:
>
> Hi,
>
> On Wed, 2015-10-07 at 21:21 -0700, Naveen Singh wrote:
> > I have few questions about service state transition to failure:
>
On Thu, Oct 8, 2015 at 6:20 AM, Patrik Flykt <patrik.fl...@linux.intel.com>
wrote:
>
> Hi,
>
> On Wed, 2015-10-07 at 21:21 -0700, Naveen Singh wrote:
> > I have few questions about service state transition to failure:
> >
> > 1. Can service state
Hi
I have few questions about service state transition to failure:
1. Can service state transition to Failure w/o generating an error event? I
am seeing that WiFi connection is not going through even if the AP is found
in scan. I dumped the service properties and I see that state is Failure
15 matches
Mail list logo