Thread Closed
OpenELEC Testbuilds for RaspberryPi (Kodi 16.0)
#26
(2015-07-08, 00:55)mp1111 Wrote: I don't know if it's just my ISP but I am unable to download any of these new builds faster than 32Kb/s

Code:
$ wget http://milhouse.openelec.tv/builds/master/RPi/OpenELEC-RPi.arm-6.0-Milhouse-20150707210143-%230707-g59a3db3.tar
--2015-07-07 23:57:20--  http://milhouse.openelec.tv/builds/master/RPi/OpenELEC-RPi.arm-6.0-Milhouse-20150707210143-%230707-g59a3db3.tar
Resolving milhouse.openelec.tv (milhouse.openelec.tv)... 82.220.2.33
Connecting to milhouse.openelec.tv (milhouse.openelec.tv)|82.220.2.33|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 120156160 (115M) [application/x-tar]
Saving to: ‘OpenELEC-RPi.arm-6.0-Milhouse-20150707210143-#0707-g59a3db3.tar’

100%[==================================================================>] 120,156,160 2.27MB/s   in 52s

2015-07-07 23:58:12 (2.20 MB/s) - ‘OpenELEC-RPi.arm-6.0-Milhouse-20150707210143-#0707-g59a3db3.tar’ saved [120156160/120156160]

2.2MB/s, which is the upper limit of my 22Mb/s downstream connection here in the UK (London).

Code:
$ ping milhouse.openelec.tv
PING milhouse.openelec.tv (82.220.2.33) 56(84) bytes of data.
64 bytes from ds1789932.dedicated.solnet.ch (82.220.2.33): icmp_seq=1 ttl=49 time=31.8 ms
64 bytes from ds1789932.dedicated.solnet.ch (82.220.2.33): icmp_seq=2 ttl=49 time=32.3 ms
64 bytes from ds1789932.dedicated.solnet.ch (82.220.2.33): icmp_seq=3 ttl=49 time=32.1 ms
64 bytes from ds1789932.dedicated.solnet.ch (82.220.2.33): icmp_seq=4 ttl=49 time=32.7 ms
^C
--- milhouse.openelec.tv ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 31.869/32.283/32.748/0.389 ms

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=53 time=9.83 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=53 time=9.48 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=53 time=9.16 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=53 time=9.70 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 9.167/9.547/9.837/0.280 ms

When you ping Google 8.8.8.8 you're unlikely to be connecting to a Google server in the same geographical location as the OpenELEC server (which appears to be located just outside Bern, in Switzerland), and instead you'll be pinging a Google server very close to your ISP.

Try running a tracepath (Ubuntu/Debian), traceroute (OpenELEC) or tracert (Windows) between you and the OpenELEC server:
Code:
$ tracepath 82.220.2.33
1?:  [LOCALHOST]                                         pmtu 1500
1:   inet-router.local                                     0.733ms
1:   inet-router.local                                     0.563ms
2:   inet-router.local                                     0.499ms pmtu 1458
2:   no reply
3:   31.55.186.133                                        18.798ms asymm  5
4:   31.55.186.156                                        18.937ms
5:   195.99.127.38                                        18.968ms
6:   peer6-hu0-19-0-1.telehouse.ukcore.bt.net             18.485ms
7:   uk-lon01a-ri4-gi-3-0-2.aorta.net                     19.491ms
8:   nl-ams05a-rd2-xe-2-3-1.aorta.net                     40.450ms asymm 15
9:   uk-lon01a-ri4-ge-4-0-0.aorta.net                     38.746ms asymm 14
10:  84.116.134.65                                        37.250ms
11:  84.116.202.230                                       38.189ms
12:  62.179.20.18                                         40.744ms
13:  151.252.33.64                                        41.223ms asymm 11
14:  eq2zrh-bbr02.solnet.ch                               50.573ms asymm 13
15:  vtlzrh-bbr01.solnet.ch                               42.420ms asymm 14
16:  vtlolt-bbr01.solnet.ch                               43.362ms asymm 15
17:  vtlbrn-bbr01.solnet.ch                               43.881ms asymm 16
18:  d11sol-bbr01.solnet.ch                               43.526ms asymm 14
19:  d11sol-dgr01.solnet.ch                               42.838ms asymm 15
20:  ds1789932.dedicated.solnet.ch                        44.173ms reached
     Resume: pmtu 1458 hops 20 back 16

Windows:
Code:
C:\>tracert 82.220.2.33

Tracing route to ds1789932.dedicated.solnet.ch [82.220.2.33]
over a maximum of 30 hops:

1     <1 ms    <1 ms    <1 ms  inet-router.local [192.168.0.1]
2      *        *        *     Request timed out.
3      9 ms     8 ms     8 ms  31.55.186.133
4      9 ms     8 ms     9 ms  31.55.186.156
5      9 ms     9 ms     9 ms  195.99.127.58
6      9 ms     8 ms     9 ms  peer6-hu0-19-0-1.telehouse.ukcore.bt.net [213.121.193.181]
7      9 ms     9 ms     9 ms  uk-lon01a-ri4-gi-3-0-2.aorta.net [213.46.174.97]
8     28 ms    28 ms    28 ms  nl-ams05a-rd2-xe-4-1-0.aorta.net [84.116.130.9]
9     52 ms    32 ms    27 ms  uk-lon01a-ri4-ge-4-0-0.aorta.net [84.116.132.18]
10    27 ms    26 ms    27 ms  uk-lon01b-rd1-xe-7-1-2.aorta.net [84.116.134.229]
11    28 ms    28 ms    27 ms  84.116.202.230
12    29 ms    38 ms    29 ms  62.179.20.18
13    37 ms    29 ms    29 ms  151.252.33.64
14    31 ms    42 ms    30 ms  eq2zrh-bbr02.solnet.ch [82.220.32.113]
15    31 ms    31 ms    31 ms  vtlzrh-bbr01.solnet.ch [212.101.0.63]
16    31 ms    31 ms    31 ms  vtlolt-bbr01.solnet.ch [212.101.0.48]
17    32 ms    32 ms    32 ms  vtlbrn-bbr01.solnet.ch [212.101.0.69]
18    43 ms    33 ms    40 ms  d11sol-bbr01.solnet.ch [212.101.0.70]
19    32 ms    32 ms    32 ms  d11sol-dgr01.solnet.ch [212.101.0.169]
20    32 ms    32 ms    31 ms  ds1789932.dedicated.solnet.ch [82.220.2.33]
Trace complete.

As you appear to be located on the US West Coast, you're connection is probably trundling along through the Southern states, popping out at New York or maybe Stamford before a swim across the Atlantic and then on to Switzerland. Or worse, you could be being routed via APAC to Europe...

You may find there's a bad or slow connection somewhere between you and the OpenELEC server, in which case you'll probably need to contact your ISP if the problem doesn't resolve itself.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
  Thread Closed
 
Thread Rating:
  • 10 Vote(s) - 5 Average


Messages In This Thread
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - by Milhouse - 2015-07-08, 01:23
Bluetooth on #1003 - by cdvreede - 2015-10-13, 11:08
Re: RE: Bluetooth on #1003 - by Milhouse - 2015-10-13, 13:24


Logout Mark Read Team Forum Stats Members Help
OpenELEC Testbuilds for RaspberryPi (Kodi 16.0)510