Bug 7926

Summary:	connman checks for internet connectivity using a private site
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Cristian Iorga <cristian.iorga>
Component:	connectivity	Assignee:	Ross Burton <ross.burton>
Status:	VERIFIED WONTFIX	QA Contact:	Daniel Istrate <daniel.alexandrux.istrate>
Severity:	normal
Priority:	Medium+	CC:	bogdanx.a.voiculescu, jku, meta.mr.watcher, meta.watcher, ross.burton
Version:	unspecified
Target Milestone:	2.1 M3
Hardware:	All
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Yes (doc changes required)

Description Cristian Iorga 2015-06-26 14:47:22 UTC

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.

Comment 1 Cristian Iorga 2015-07-23 10:58:10 UTC

Pushing this to M3 due to changing priorities.

Comment 2 Jussi Kukkonen 2015-08-20 15:07:09 UTC

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.

Comment 3 Ross Burton 2016-01-26 16:22:48 UTC

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.

Comment 4 Ross Burton 2016-01-26 16:46:26 UTC

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.

Comment 5 Daniel Istrate 2016-02-17 10:42:51 UTC

Verified WontFix