[PATCH] conf/distro/poky.conf: use google.com for connectivity check

[PATCH] conf/distro/poky.conf: use google.com for connectivity check

[Ross Burton]

Instead of pinging both the Yocto Project download site and bugzilla, just ping
google.com.

In my testing this reduces the time taken for connectivity checks from 3 seconds
to 0.15 seconds.

Signed-off-by: Ross Burton <ross.burton@intel.com>
---
 meta-yocto/conf/distro/poky.conf | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index 39419d5..f3bea27 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -65,9 +65,7 @@ https://.*/.*    http://downloads.yoctoproject.org/mirror/sources/ \n"
 # the variable to be empty.
 # Git example url: git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=master
 
-CONNECTIVITY_CHECK_URIS ?= " \
-             https://eula-downloads.yoctoproject.org/index.php \
-             http://bugzilla.yoctoproject.org/report.cgi"
+CONNECTIVITY_CHECK_URIS ?= "http://google.com/"
 
 SANITY_TESTED_DISTROS ?= " \
             poky-1.7 \n \
-- 
2.6.4

Re: [PATCH] conf/distro/poky.conf: use google.com for connectivity check

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 442 bytes --]

On 28 January 2016 at 07:58, Robert Yang <liezhi.yang@windriver.com> wrote:

> Sorry, but google.com is nearly unreachable in China as the reason you
> may know.
>
> How about 8.8.8.8 which is OK ?
>

That's a good point which I should have thought of.  I'm surprised the
Great Firewall lets 8.8.8.8 through, but as this check uses the fetcher
there needs to be a HTTP URL it can open and 8.8.8.8 doesn't respond to
HTTP.

Ross

[-- Attachment #2: Type: text/html, Size: 926 bytes --]

Re: [PATCH] conf/distro/poky.conf: use google.com for connectivity check

[Robert Yang]

On 01/28/2016 05:17 PM, Burton, Ross wrote:
>
> On 28 January 2016 at 07:58, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
>
>     Sorry, but google.com <http://google.com> is nearly unreachable in China as
>     the reason you may know.
>
>     How about 8.8.8.8 which is OK ?
>
>
> That's a good point which I should have thought of.  I'm surprised the Great
> Firewall lets 8.8.8.8 through, but as this check uses the fetcher there needs to
> be a HTTP URL it can open and 8.8.8.8 doesn't respond to HTTP.

It seems that 8.8.8.8 doesn't repond to HTTP. How about example.org which
is reserved by RFC ?

In the USA:
$ ping example.org
PING example.org (93.184.216.34) 56(84) bytes of data.
64 bytes from 93.184.216.34: icmp_req=1 ttl=52 time=5.82 ms
64 bytes from 93.184.216.34: icmp_req=2 ttl=52 time=5.25 ms

$ ping google.com
PING google.com (216.58.219.14) 56(84) bytes of data.
64 bytes from lax17s03-in-f14.1e100.net (216.58.219.14): icmp_req=1 ttl=54 
time=12.2 ms
64 bytes from lax17s03-in-f14.1e100.net (216.58.219.14): icmp_req=2 ttl=54 
time=11.8 ms


$ ping yoctoproject.org
PING yoctoproject.org (140.211.169.56) 56(84) bytes of data.
64 bytes from yocto-www.yoctoproject.org (140.211.169.56): icmp_req=1 ttl=53 
time=26.6 ms
64 bytes from yocto-www.yoctoproject.org (140.211.169.56): icmp_req=2 ttl=53 
time=26.0 ms

The example.org is faster than google.com and yoctoproject.org.

In China, example.org is also OK.
$ ping example.org
PING example.org (93.184.216.34) 56(84) bytes of data.
64 bytes from 93.184.216.34: icmp_seq=2 ttl=52 time=155 ms
64 bytes from 93.184.216.34: icmp_seq=3 ttl=52 time=158 ms

$ ping google.com
PING google.com (216.58.221.142) 56(84) bytes of data.
[no respond]

$ ping yoctoproject.org
PING yoctoproject.org (140.211.169.56) 56(84) bytes of data.
64 bytes from yocto-www.yoctoproject.org (140.211.169.56): icmp_seq=3 ttl=49 
time=336 ms
64 bytes from yocto-www.yoctoproject.org (140.211.169.56): icmp_seq=4 ttl=49 
time=397 ms

// Robert

>
> Ross

Re: [PATCH] conf/distro/poky.conf: use google.com for connectivity check

[Richard Purdie]

On Thu, 2016-01-28 at 09:17 +0000, Burton, Ross wrote:
> 
> On 28 January 2016 at 07:58, Robert Yang <liezhi.yang@windriver.com>
> wrote:
> > Sorry, but google.com is nearly unreachable in China as the reason
> > you may know.
> > 
> > How about 8.8.8.8 which is OK ?
> > 
> That's a good point which I should have thought of.  I'm surprised
> the Great Firewall lets 8.8.8.8 through, but as this check uses the
> fetcher there needs to be a HTTP URL it can open and 8.8.8.8 doesn't
> respond to HTTP.

Note that we specifically put an https:// test in here too as we've had
issues with that before :(

Cheers,

Richard

Re: [PATCH] conf/distro/poky.conf: use google.com for connectivity check

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 245 bytes --]

On 28 January 2016 at 10:16, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> Note that we specifically put an https:// test in here too as we've had
> issues with that before :(
>

How about https://www.iana.org/?

Ross

[-- Attachment #2: Type: text/html, Size: 705 bytes --]

Re: [PATCH] conf/distro/poky.conf: use google.com for connectivity check

[Robert Yang]

On 01/28/2016 06:50 PM, Burton, Ross wrote:
>
> On 28 January 2016 at 10:16, Richard Purdie <richard.purdie@linuxfoundation.org
> <mailto:richard.purdie@linuxfoundation.org>> wrote:
>
>     Note that we specifically put an https:// test in here too as we've had
>     issues with that before :(
>
>
> How about https://www.iana.org/?

This fine, but I prefer:

http://www.example.org/
https://www.example.org/

They are faster and smaller than www.iana.org in both the USA and China.
I'm not sure about the U.K. since I don't have a server there.

// Robert

>
> Ross

Re: [PATCH] conf/distro/poky.conf: use google.com for connectivity check

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

On 29 January 2016 at 01:41, Robert Yang <liezhi.yang@windriver.com> wrote:

> They are faster and smaller than www.iana.org in both the USA and China.
> I'm not sure about the U.K. since I don't have a server there.
>

Agreed, it responds quickly and the page is very small.  We have a winner!

Ross

[-- Attachment #2: Type: text/html, Size: 800 bytes --]