Hi Daniel & Patrik,

Thanks for the responses.

Checked with connman incrementally from v1.30 to v1.33, found out the delay behaviour almost similar on my setup.
Also ensured systemd-networkd is not running on my setup.

Further observed with less available entropy.. on the setup causing the delay. So continuing with v1.33.

:~# cat /proc/sys/kernel/random/entropy_avail                                                                                                                           

Getting connman waiting/stuck at  getrandom (_rnd_get_system_entropy_getrandom) (by default gnutls enabled)
So tried to increase entropy with help of /dev/urandom & and with sufficient ~3k+ entropy count observed the getrandom call completed successfully.
Is this know behaviour Or experienced by anyone.. ?

:~# rngd -r /dev/urandom -o /dev/random                                                                                                                                        
:~# cat /proc/sys/kernel/random/entropy_avail

Please advise, we suppose to use only /dev/random for better security reasons and not /dev/urandom ? thoughts if any for other ways to deal with less/no entropy available with /dev/random?

Any pointers or references will be a great help..


On Wed, Dec 7, 2016 at 7:27 PM, Patrik Flykt <Patrik.Flykt@linux.intel.com> wrote:
On Fri, 2016-11-25 at 15:38 +0530, Shrikant Bobade wrote:
> Hi,
> I am using connman v1.33 along with systemd v230 for yocto based
> project.
>  Experiencing delay in IP assignment ranging from 20 sec. to 1.5 min.
> While used earlier versions previously didn't faced such delays. So
> by the time I am finding the exact change in version causing this
> delay issue. Just want to check anyone experiencing such delays in IP
> assignments. 
> Any suggestions or pointers will be a great help.  

Ensure that you don't have systemd-networkd running, at least not on
the interfaces used by ConnMan?