follow-up

2015-05-27 Thread Thomas Green 
And as a follow up to my own question, we are running connman 1.29, and 
wpa_supplicant 2.0

Thanks again.
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman

Re: follow-up

2015-05-27 Thread Tomasz Bursztyka 

Hi Thomas,

Could you grab all connman and wpa_supplicant logs this way:

- wpa_supplicant -u -dddt &> wpa_supp.log
- CONNMAN_SUPPLICANT_DEBUG=1 CONNMAN_DHCP_DEBUG=1 connmand -n -d &> 
connman.log


Also, try to upgrade to latest wpa_supplicant, a huge amount of fixes 
went in (and ssl related ones,

might be worth being up to date with openssl as well)

Tomasz
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman

Re: follow-up

2015-05-27 Thread Tomasz Bursztyka 

Ah you did actually get the wpa_supplicant logs in the other mail, ok.

Ok try to update wpa_supplicant. It's definitely not a connman bug.
It might be related to the regulatory domain update once you get 
associated somehow.

I have seen such bug passing by before on wpa_s.

Let us know

Tomasz


Hi Thomas,

Could you grab all connman and wpa_supplicant logs this way:

- wpa_supplicant -u -dddt &> wpa_supp.log
- CONNMAN_SUPPLICANT_DEBUG=1 CONNMAN_DHCP_DEBUG=1 connmand -n -d &> 
connman.log


Also, try to upgrade to latest wpa_supplicant, a huge amount of fixes 
went in (and ssl related ones,

might be worth being up to date with openssl as well)

Tomasz
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman



___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman