conf/distro/poky.conf: use google.com for connectivity check
PATCH 1/1 conf/distro/poky.conf: use google.com for connectivity check
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.
--- meta-yocto/conf/distro/poky.conf | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
meta-yocto/conf/distro/poky.conf +1 -3
@@ -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 \
Signature · 1 line
2.6.4
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Robert Yang
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
Quoted 7 lines · Ross
On 28 January 2016 at 07:58, Robert Yang <[email protected] <mailto:[email protected]>> wrote:
Sorry, but google.com <http://google.com> is nearly unreachable in China as the reason you may know.
Quoted 6 lines
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
Quoted 2 lines
Ross
Quoted 6 lines · Ross
Quoted 3 lines · Robert Yang
Sorry, but google.com is nearly unreachable in China as the reason you may know.
Quoted 6 lines
Quoted 2 lines
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
Quoted 3 lines · Richard Purdie
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
Quoted 9 lines · Ross
On 28 January 2016 at 10:16, Richard Purdie <[email protected] <mailto:[email protected]>> 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
Quoted 2 lines
Ross
Quoted 3 lines · Robert Yang
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