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: Is there some "Hello GDbus connman World" somewhere ?
(Pierre Couderc)
2. Re: Is there some "Hello GDbus connman World" somewhere ?
(Pierre Couderc)
3. Re: miracast connections using connman disconnect after 30
mins (DHCP renewal problem?) (Carl D. Blake)
4. Re: miracast connections using connman disconnect after 30
mins (DHCP renewal problem?) (Carl D. Blake)
----------------------------------------------------------------------
Message: 1
Date: Mon, 24 Jul 2017 17:18:06 +0200
From: Pierre Couderc <[email protected]>
To: [email protected]
Subject: Re: Is there some "Hello GDbus connman World" somewhere ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 07/24/2017 03:18 PM, Daniel Wagner wrote:
>
> Daniel
Thank you, these examples are interesting.
------------------------------
Message: 2
Date: Mon, 24 Jul 2017 17:23:36 +0200
From: Pierre Couderc <[email protected]>
To: [email protected]
Subject: Re: Is there some "Hello GDbus connman World" somewhere ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 07/24/2017 04:07 PM, Julien Massot wrote:
> Hi Pierre,
>
>
> Julien
Thank you, Julien, I study that.
------------------------------
Message: 3
Date: Mon, 24 Jul 2017 10:35:33 -0700
From: "Carl D. Blake" <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: miracast connections using connman disconnect after 30
mins (DHCP renewal problem?)
Message-ID: <1500917733.26575.215.camel@ironhills>
Content-Type: text/plain; charset="UTF-8"
Daniel,
On Mon, 2017-07-24 at 15:06 +0200, Daniel Wagner wrote:
> Hi Carl,
>
> On 07/21/2017 08:00 PM, Carl D. Blake wrote:
> > I don't see any further messages that indicate why the driver is
> > deauthorizing. I do notice that I get the message from wpa_supplicant
> > that it failed to initiate sched scan right before the disconnect
> > occurs.
>
> wpa_s is always good for some trouble. So one thing you could do is to
> start wpa_s by hand and enable the debug options and see what wpa_s doing:
>
> # wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -s -dd
>
It looks to me like connman is starting wpa_supplicant. Is this true?
I've been setting debug options in the various /etc files for
wpa_supplicant, but I always get one wpa_supplicant running in the
background which does not have its debug options set. This
wpa_supplicant always starts after connman starts and I can't locate any
other places in /etc where wpa_supplicant is started.
> > Could this have something to do with it?
>
> The DHCP code in ConnMan is not really driving anything directly. That
> means we would see something from service.c which tells us it decided to
> disconnect. But we don't see that either. So we should look at wpa_s.
>
> > I'm unconvinced that
> > this is a problem with the driver. The disconnect occurs reliably after
> > 30 minutes of being connected. I can set my watch by it.
>
> I agree, if you see can reproduce this with different wifi cards it is
> probably not the drivers.
>
> Thanks,
> Daniel
------------------------------
Message: 4
Date: Mon, 24 Jul 2017 10:45:51 -0700
From: "Carl D. Blake" <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: miracast connections using connman disconnect after 30
mins (DHCP renewal problem?)
Message-ID: <1500918351.26575.216.camel@ironhills>
Content-Type: text/plain; charset="UTF-8"
Daniel,
On Mon, 2017-07-24 at 10:35 -0700, Carl D. Blake wrote:
> Daniel,
>
> On Mon, 2017-07-24 at 15:06 +0200, Daniel Wagner wrote:
> > Hi Carl,
> >
> > On 07/21/2017 08:00 PM, Carl D. Blake wrote:
> > > I don't see any further messages that indicate why the driver is
> > > deauthorizing. I do notice that I get the message from wpa_supplicant
> > > that it failed to initiate sched scan right before the disconnect
> > > occurs.
> >
> > wpa_s is always good for some trouble. So one thing you could do is to
> > start wpa_s by hand and enable the debug options and see what wpa_s doing:
> >
> > # wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -s -dd
> >
>
> It looks to me like connman is starting wpa_supplicant. Is this true?
> I've been setting debug options in the various /etc files for
> wpa_supplicant, but I always get one wpa_supplicant running in the
> background which does not have its debug options set. This
> wpa_supplicant always starts after connman starts and I can't locate any
> other places in /etc where wpa_supplicant is started.
>
Never mind, I found it being started by dbus
in /usr/share/dbus-1/system-services.
> > > Could this have something to do with it?
> >
> > The DHCP code in ConnMan is not really driving anything directly. That
> > means we would see something from service.c which tells us it decided to
> > disconnect. But we don't see that either. So we should look at wpa_s.
> >
> > > I'm unconvinced that
> > > this is a problem with the driver. The disconnect occurs reliably after
> > > 30 minutes of being connected. I can set my watch by it.
> >
> > I agree, if you see can reproduce this with different wifi cards it is
> > probably not the drivers.
> >
> > Thanks,
> > Daniel
>
>
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/connman
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 21, Issue 15
***************************************
