<div dir="ltr">We just ship what upstream connman provides, so you'll probably have more luck talking to the connman list.<div><br></div><div>Ross</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 28 November 2017 at 17:22, Francesco Giancane <span dir="ltr"><<a href="mailto:francescogiancane8@gmail.com" target="_blank">francescogiancane8@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi everyone,<br>
<br>
I am doing a build on the Raspberry Pi 3 for an University project. I<br>
included in the core-image-minimal image the connman packages, so that<br>
I have connmanctl, connman.service and connman-wait-online.service<br>
enabled.<br>
<br>
Wired network is set up properly and so is wifi using connmanctl. I<br>
can successfully connect to the board using ssh.<br>
<br>
What bugs me is the fact that connman-wait-online is not signaling<br>
properly systemd that the network is configured.<br>
<br>
systemctl status network.target yields that the target network has<br>
been reached so far.<br>
On the same side, network-online.target is not even started (no one<br>
notified it of the network being online).<br>
<br>
Also, connman-wait-online.service seems to not be even started<br>
(reports inactive (dead)).<br>
<br>
What is happening? Can someone tell me what I am missing in order to<br>
connman-wait-online to correctly signal network being online?<br>
<br>
Many thanks,<br>
Francesco<br>
<span class="HOEnZb"><font color="#888888">--<br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.<wbr>openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</font></span></blockquote></div><br></div>