connman checks for online connectivity using a private site. connman pings connman.net to see if it gets the response it expects, and if there's captive portal tricks going on. The solution to this issue will be: a) make this clearly configurable in the recipe; b) see if we can use some yoctoproject.org address by default c) document how the users of our project can establish own web infrastructure to perform the online connectivity check.
Pushing this to M3 due to changing priorities.
FYI so you don't have to start from zero: I had a discussion about this on connman mailing list (sorry, no link but it was during this summer) and IMO Marcel made a pretty good case for not doing any of these options as well as explaining how the assumed privacy problems really aren't there: the server really can't tell anything about the clients that ping connman.net.
For what it's worth I agree with Jussi/Marcel here. Most modern networking stacks do this exact same thing to a well-known service to check for captive portals and determine public IP.
So the mail from Marcel is at https://www.mail-archive.com/connman@connman.net/msg18117.html. The README for connman explains what hosts it pings, and what the expected API is. https://www.mail-archive.com/connman@connman.net/msg18105.html has an example configuration for nginx. There's a huge overhead in maintaining this infrastructure yourself: you need to be constantly available over ipv4 and ipv6, otherwise your hardware breaks. Closing wontfix as I don't believe this is something we should fix. If a user of YP is watching outgoing packets and wants to change the behaviour, it's just a two line patch to connman (that upstream refuses to accept a configuration for) and an infrastructure commitment.
Verified WontFix