What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Unable to download mesh files = I can't use HB!

I would too, if it was only effecting people in New Zealand :p

The mesh server has a 30 second timeout before it kicks you from trying to download things. Is it possible its timing out due to some aspect of your connection (I know you have two and they are awesome so probably not) or just the routing from NZ to wherever the auth server is in Germany? Are the other people with the same issue from areas far away as well?

Try doing a tracert to 188.165.234.190 and see if you have any strange hops that are taking a long time. Here's mine for reference:

Code:
  3     1 ms     1 ms     1 ms  mpr1.vlan-3-bbnet1.bsn004.pnap.net [63.251.128.46]
  4     1 ms     1 ms     1 ms  xe-0-1-0.bos10.ip4.tinet.net [77.67.77.53]
  5     5 ms     5 ms     5 ms  xe-8-2-0.nyc32.ip4.tinet.net [89.149.182.169]
  6     6 ms     6 ms     6 ms  te9-4-10G.ar8.NYC1.gblx.net [64.212.107.181]
  7   114 ms   110 ms     *     ldn-1-6k.uk.eu [213.251.130.53]
  8   108 ms   105 ms   105 ms  rbx-g2-a9.fr.eu [91.121.131.177]
  9    96 ms    99 ms   101 ms  vss-3-6k.fr.eu [94.23.122.93]
 10   107 ms   100 ms   105 ms  ns213941.ovh.net [188.165.234.190]

Trace complete.
 
Test 1

PHP:
Tracing route to ns213941.ovh.net [188.165.234.190]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 42 ms 58 ms 40 ms p24.static.cpiak1-f2.callplus.net.nz [202.180.77.24]
3 62 ms 42 ms 47 ms skytrain.cust.commverge.net.nz [202.180.65.153]
4 22 ms 47 ms 19 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
5 65 ms 50 ms 35 ms ge-1-0-0-401.gw1.akl2.asianetcom.net [203.192.130.193]
6 145 ms 152 ms 165 ms po1-1-0.gw3.lax1.asianetcom.net [203.192.185.62]
7 164 ms 178 ms 145 ms TenGigabitEthernet1-2.ar5.LAX2.gblx.net [64.215.81.145]
8 279 ms 307 ms 277 ms ldn-1-6k.uk.eu [213.251.130.53]
9 291 ms 380 ms 350 ms rbx-g2-a9.fr.eu [91.121.131.177]
10 * * * Request timed out.
11 296 ms 281 ms 303 ms ns213941.ovh.net [188.165.234.190]
 
Trace complete.

Test 2

PHP:
Tracing route to ns213941.ovh.net [188.165.234.190]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms 192.168.1.1
2 47 ms 19 ms 60 ms p24.static.cpiak1-f2.callplus.net.nz [202.180.77.24]
3 32 ms 52 ms 33 ms skytrain.cust.commverge.net.nz [202.180.65.153]
4 21 ms 20 ms 54 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
5 20 ms 21 ms 54 ms ge-1-0-0-401.gw1.akl2.asianetcom.net [203.192.130.193]
6 185 ms 195 ms 144 ms po1-1-0.gw3.lax1.asianetcom.net [203.192.185.62]
7 159 ms 152 ms 216 ms TenGigabitEthernet1-2.ar5.LAX2.gblx.net [64.215.81.145]
8 * 277 ms 277 ms ldn-1-6k.uk.eu [213.251.130.53]
9 317 ms 315 ms 346 ms rbx-g2-a9.fr.eu [91.121.131.177]
10 318 ms * 315 ms vss-3-6k.fr.eu [213.251.130.77]
11 281 ms 286 ms 281 ms ns213941.ovh.net [188.165.234.190]
Trace complete


Ping test

PHP:
C:\Users\Administrator>ping 188.165.234.190
Pinging 188.165.234.190 with 32 bytes of data:
Reply from 188.165.234.190: bytes=32 time=288ms TTL=118
Reply from 188.165.234.190: bytes=32 time=289ms TTL=118
Reply from 188.165.234.190: bytes=32 time=280ms TTL=118
Reply from 188.165.234.190: bytes=32 time=315ms TTL=118
Ping statistics for 188.165.234.190:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 280ms, Maximum = 315ms, Average = 293ms

This has only been an issue since the encryption was added to the mesh files.
 
Last edited:
Back
Top