7926 2015-06-26 14:47:22 +0000 connman checks for internet connectivity using a private site 2016-02-17 10:42:51 +0000 1 1 7 Build System, Metadata & Runtime OE-Core connectivity unspecified All Multiple VERIFIED WONTFIX Medium+ normal 2.1 M3 1 cristian.iorga ross.burton bogdanx.a.voiculescu jku meta.mr.watcher meta.watcher ross.burton daniel.alexandrux.istrate --- --- Yes (doc changes required) oldest_to_newest 51966 0 cristian.iorga 2015-06-26 14:47:22 +0000 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. 52552 1 cristian.iorga 2015-07-23 10:58:10 +0000 Pushing this to M3 due to changing priorities. 53276 2 jku 2015-08-20 15:07:09 +0000 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. 58243 3 ross.burton 2016-01-26 16:22:48 +0000 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. 58245 4 ross.burton 2016-01-26 16:46:26 +0000 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. 59145 5 daniel.alexandrux.istrate 2016-02-17 10:42:51 +0000 Verified WontFix