Dear normis ;
when we will be able to download again from tiktube.com ???
this site is a good refrence for MikroTik users , so to keep these clips will be helpfull .
also why MikroTik not officially filming MUM events and publish it to users ? , most of all are not able to attend the MUM for many reasons .
with best regards .
Dear Normis ;
how are you ? , how is the MUM ?
yes , i know there are many films about MUM and i download many of them before which they are a valueable and good refrence to me .
i got many ideas from them and watch many more than a time and for that i am asking when we will be able to dounload them ?
also i asked that MikroTik team record the MUM from their cams , because in many previous clips there is a big croud and noise which it make it harder to listen .
many thanks in advance for all your efforts .
with best regards .
tiktube Works well from SpectrumNET Varna Bulgaria. MUM CZ 09: Non line of sight very funny but http://www.tiktube.com/?video=221 How to install Mikrotik 3.15 on Sun VirtualBox virtual machine not working
Tracing route to tiktube.com [174.36.189.128]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms mikrotik []
2 10 ms 2 ms 2 ms r1-shipka.varna.spnet.net [82.103.67.98]
3 2 ms 1 ms 1 ms router.varna.spnet.net [82.103.67.97]
4 47 ms 68 ms 52 ms spectrum-ic-131757-ffm-b10.c.telia.net [213.248.90.206]
5 47 ms 75 ms 49 ms ffm-b10-link.telia.net [213.248.90.205]
6 48 ms 47 ms 46 ms ffm-bb1-link.telia.net [80.91.251.123]
7 49 ms 53 ms 76 ms ffm-b2-link.telia.net [80.91.248.98]
8 52 ms 68 ms 54 ms verio-ic-128400-ffm-b2.c.telia.net [213.248.69.50]
9 310 ms 309 ms 311 ms xe-3-2.r00.frnkge03.de.bb.gin.ntt.net [129.250.2.224]
10 48 ms 48 ms 49 ms xe-1-1-0.r20.frnkge03.de.bb.gin.ntt.net [129.250.2.240]
11 49 ms 49 ms 48 ms p16-0-0-0.r00.frnkge02.de.bb.gin.ntt.net [129.250.2.122]
12 48 ms 49 ms 56 ms p16-2-0-0.r01.frnkge02.de.bb.gin.ntt.net [129.250.3.195]
13 54 ms 54 ms 72 ms p16-0-0-2.r22.amstnl02.nl.bb.gin.ntt.net [129.250.5.6]
14 54 ms 55 ms 56 ms ae-1.r23.amstnl02.nl.bb.gin.ntt.net [129.250.4.222]
15 159 ms 150 ms 145 ms as-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.158]
16 149 ms 140 ms 145 ms ae-3.r20.asbnva02.us.bb.gin.ntt.net [129.250.2.129]
17 207 ms 208 ms 201 ms as-2.r21.lsanca03.us.bb.gin.ntt.net [129.250.5.24]
18 199 ms 199 ms 204 ms ae-0.r20.lsanca03.us.bb.gin.ntt.net [129.250.3.33]
19 306 ms 306 ms 310 ms as-5.r20.tokyjp01.jp.bb.gin.ntt.net [129.250.3.23]
20 309 ms 319 ms 323 ms ae-3.r20.osakjp01.jp.bb.gin.ntt.net [129.250.4.210]
21 338 ms 336 ms 338 ms ae-4.r21.osakjp01.jp.bb.gin.ntt.net [129.250.4.58]
22 324 ms 325 ms 342 ms as-1.r21.sttlwa01.us.bb.gin.ntt.net [129.250.3.87]
23 313 ms * 315 ms po-1.r01.sttlwa01.us.bb.gin.ntt.net [129.250.3.37]
24 316 ms 323 ms 327 ms te1-3.cer02.sea01.seattle-datacenter.com [198.104.203.254]
25 335 ms 467 ms 447 ms po02.fcr01.sea01.seattle-datacenter.com [67.228.118.138]
26 333 ms 330 ms 331 ms 174.36.189.128-static.reverse.softlayer.com [174.36.189.128]
Trace complete.
Wow, your routes are seriously messed up there. Flips from Germany, Netherlands, US to JP back to US.. From Bulgaria? Maybe time to move upstream provider?
Tracing route to tiktube.com [174.36.189.128]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms mikrotik []
2 1 ms 1 ms 1 ms r2-musala.varna.spnet.net [82.103.67.124]
3 1 ms 2 ms 3 ms router.varna.spnet.net [82.103.67.97]
4 43 ms 42 ms 41 ms spectrum-ic-131757-ffm-b10.c.telia.net [213.248.90.206]
5 42 ms 42 ms 41 ms ffm-b10-link.telia.net [213.248.90.205]
6 45 ms 41 ms 41 ms ffm-bb1-link.telia.net [80.91.251.123]
7 45 ms 43 ms 46 ms ffm-b2-link.telia.net [80.91.252.172]
8 46 ms 49 ms 45 ms verio-ic-128400-ffm-b2.c.telia.net [213.248.69.50]
9 45 ms 45 ms 45 ms xe-1-1-0.r21.frnkge03.de.bb.gin.ntt.net [129.250.2.12]
10 55 ms 42 ms 45 ms xe-1-0-0.r20.frnkge03.de.bb.gin.ntt.net [129.250.2.148]
11 60 ms 57 ms 55 ms as-0.r22.londen03.uk.bb.gin.ntt.net [129.250.2.226]
12 130 ms 133 ms 157 ms as-0.r20.nycmny01.us.bb.gin.ntt.net [129.250.3.254]
13 199 ms 200 ms 199 ms as-2.r21.sttlwa01.us.bb.gin.ntt.net [129.250.3.190]
14 203 ms 205 ms 204 ms po-1.r01.sttlwa01.us.bb.gin.ntt.net [129.250.3.37]
15 203 ms 201 ms 203 ms te1-3.cer02.sea01.seattle-datacenter.com [198.104.203.254]
16 256 ms 206 ms 206 ms po02.fcr01.sea01.seattle-datacenter.com [67.228.118.138]
17 201 ms 201 ms 204 ms 174.36.189.128-static.reverse.softlayer.com [174.36.189.128]
Trace complete.