Targo Telekom

Angelos · 01.10.2012

Da li neko igra Diablo 3 ili BF3 online pored WoT?
Kakvi su Vam pingovi?

defcoon221 · 01.10.2012

Angelos je napisao(la):
Da li neko igra Diablo 3 ili BF3 online pored WoT?
Kakvi su Vam pingovi?

Ja sam juce trebao to da uradim ali me vrat boli i lezim u krevetu vec od cetvrtka ima da lezim jos 2 dana do srede....

Cim budem mogao postavicu na youtube....

dejan#7 · 01.10.2012

AKCIJA - Časti sebe i pokloni dragim ljudima

dejan#7 · 01.10.2012

Inace danas je LS

jox · 01.10.2012

veljaNBG je napisao(la):
To sto ti mislis da su oni dosli sa masinom (BTW "oni" uslovno, imaju podizvodjace) i seku tek tako naravno da tako ne ide.Prijatelj mi je komunalni inspektor i on je resavao 10 prijava radova za 10 lokacija.
Slobodno pisi prijave komunalnoj gde god vidis, jedino tako ce neko i izaci na teren.
Da za mikro-rovove treba MANJE dozvola ne i NIKAKVA dozvola.

ne mislim da su bez ikakve dozvole, ali bi neka kontrola njihovog rada trebala da postoji i da se nateraju da asfalt koji ostave izgleda koliko toliko normalno.

pavle93 · 01.10.2012

Vec 4h montiraju u stanu kablove, bolje bi bilo da je tako dobar. Javljam utiske.

defcoon221 · 01.10.2012

pavle93 je napisao(la):
Vec 4h montiraju u stanu kablove, bolje bi bilo da je tako dobar. Javljam utiske.

Ja mogu samo da uputim reci hvale za TT ali ti vidi kako ti bude to bilo imas 14 dana da se odlucis

,kada sam zadnji put koristio internet na TT up je bio ako se dobro secam malo iznad 800 kb,naravno ako ti ti znaci a dn mi je u nekim trenucima isao i do dvadeset i nesto Mb/s .... Sto se tice tv to ni negledam ali je korektna slika

batak65 · 01.10.2012

batak65 je napisao(la):
Juče sam napokon uspeo da razgovaram sa inženjerom iz Targo podrške, izneo mu tri problema:

1. WiFi umrežavanje putem Homegroup,
2. pristup USB-u sa spoljne mreže,
3. postavljanje uputstva za ONT na njihov sajt. Kako mi je rečeno

Kako mi je prenešeno, oni nisu isprobali uređaj da li podržava pod 1. i 2. Pod 1. su probali samo klasično da se umreže i to putem kabla, to znamo da funkcioniše i na WiFi. USB pristup spolja nisu testirali. Obećano mi je da će to uraditi za vikend i da će mi odgovori biti spremni u ponedeljak.

Pa, ako su lagali mene, lažem i ja vas.
Usvakom slučaju, postaviću rezultate ako ne može i ako može - kako!

Na žalost, dobio sam odgovor od podrške, bolje da nisam:

"Poštovani,
u prilogu mail-a šaljemo vam odgovor.

“Sto se tice Homegroup-a, imate na ovom linku uputstvo:
http://windows.microsoft.com/is-IS/windows7/help/homegroup-from-start-to-finish
Nas ONT omogucava medjusobnu komunikaciju racunara u lokalnoj mrezi i ni na koji nacin ne sprecava kreiranje Homegroup-e.”

S poštovanjem,
Vaš Targo Telekom."

Uporedite odgovor sa poslatim pitanjima i sve će vam biti jasno.

dejan#7 · 01.10.2012

Pa pitaj ih onda kako radi na adsl ruteru, a na njihovom ONT-u ne radi.

goran064 · 01.10.2012

Moje pitanje je: Kako je moguce da preko wifi imam skoro duplo manju brzinu downloada neko preko lana?Upload je u redu.
Do pre neki dan je sve bilo u redu a u medjuvremenu nije nista menjano.
Preko notebooka isto preko wifi-ja brzina je u redu,pa zakljucujem da je problem u mom laptopu?
S obzirom na odgovor koji je dobio Batak65 racunam da je bolje da ovde pitam.
(restartovao ruter,radio factory default,ma jok,ne pomaze)

dejan#7 · 01.10.2012

Pa najverovatnije je do WiFi tj. do lap topa.
Ako u lan radi normalno onda je sigurno to razlog.
Javice se neko strucniji da pojasni, ja sam samo izneo moje misljenje

yt7pwr · 01.10.2012

goran064 je napisao(la):
Moje pitanje je: Kako je moguce da preko wifi imam skoro duplo manju brzinu downloada neko preko lana?Upload je u redu.
Do pre neki dan je sve bilo u redu a u medjuvremenu nije nista menjano.
Preko notebooka isto preko wifi-ja brzina je u redu,pa zakljucujem da je problem u mom laptopu?
S obzirom na odgovor koji je dobio Batak65 racunam da je bolje da ovde pitam.
(restartovao ruter,radio factory default,ma jok,ne pomaze)

Ako je na laptop-u stari USB 1.0 onda je maksimalna brzina 802.11b oko 5.5Mb/s. Ako je laptop noviji proveri u BIOS-u da li je ukljucen USB 2.0. Ovo sve vazi ako se koristi spoljasnji WiFi adapter povezan na USB. Ako je u pitanju interni WiFi modul proveri njegove karakteristike tj. da li je b/g/n kompatibilan ili je stari tip brzine 11Mb (11Mb simplex ili 5.5Mb/s duplex).

kibicer · 01.10.2012

Danas su bili, evo rezultata možda 3 min nakon što je ONT uhvatio vezu:

SaniBG · 01.10.2012

batak65 je napisao(la):
Na žalost, dobio sam odgovor od podrške, bolje da nisam:

"Poštovani,
u prilogu mail-a šaljemo vam odgovor.

“Sto se tice Homegroup-a, imate na ovom linku uputstvo:
http://windows.microsoft.com/is-IS/windows7/help/homegroup-from-start-to-finish
Nas ONT omogucava medjusobnu komunikaciju racunara u lokalnoj mrezi i ni na koji nacin ne sprecava kreiranje Homegroup-e.”

S poštovanjem,
Vaš Targo Telekom."

Uporedite odgovor sa poslatim pitanjima i sve će vam biti jasno.

Ha ha ha, nadam se da vam je sada jasno zasto sam digao ruke po ovom pitanju i stavio njihov router u BRIDGE mod i povezao svoj WiFi router. Savetujem i ostalima da to urade i rese se muka!

goran064 · 01.10.2012

yt7pwr je napisao(la):
Ako je na laptop-u stari USB 1.0 onda je maksimalna brzina 802.11b oko 5.5Mb/s. Ako je laptop noviji proveri u BIOS-u da li je ukljucen USB 2.0. Ovo sve vazi ako se koristi spoljasnji WiFi adapter povezan na USB. Ako je u pitanju interni WiFi modul proveri njegove karakteristike tj. da li je b/g/n kompatibilan ili je stari tip brzine 11Mb (11Mb simplex ili 5.5Mb/s duplex).

Interni.Laptop je novijeg datuma i opet kazem do prekljuce je sve normalno pokazivao.

markomix · 01.10.2012

Probaj da promenis kanal, vidi jel ce to da pomogne

kibicer · 01.10.2012

Mereno iz IE, WiFi konekcija

dzonihsv · 01.10.2012

Nemoj IE, brlja sa pingom i rezultatima. Uzmi Chrome, Firefox, Operu... šta hoćeš, samo ne IE.

Mare · 01.10.2012

kibicer je napisao(la):
Mereno iz IE, WiFi konekcija

mrsh :d

kibicer · 01.10.2012

***, Mare, taman sam mislio da ti ustupim jedno dvaes mega linka, ali izgleda da je dzoni u pravu

Chrome, isto WiFi konekcija (drugi računar):

Opera:

mighty78 · 02.10.2012

SaniBG je napisao(la):
Ha ha ha, nadam se da vam je sada jasno zasto sam digao ruke po ovom pitanju i stavio njihov router u BRIDGE mod i povezao svoj WiFi router. Savetujem i ostalima da to urade i rese se muka!

Ja sam to planirao od starta, nikad me oprema provajdera nije preterano interesovala.

Imam svoj TL-1043ND kojim sam sasvim zadovoljan, sve podešeno kako treba, homegroup, redirekcija portova, wifi, što bih umesto njega stavio to izraelsko čudo? ONT treba da mi izigrava glupi kablovski modem i ništa više.

dzonihsv · 02.10.2012

kibicer je napisao(la):
***, Mare, taman sam mislio da ti ustupim jedno dvaes mega linka, ali izgleda da je dzoni u pravu

Chrome, isto WiFi konekcija (drugi računar):

Opera:

Pa naravno da jesam.

A sad daj speedtest-ove van TT mreže (prema SBB-u, Veratu i Telekomu).

kibicer · 02.10.2012

Teraš me da gasim torrent

Kačio sam sa drugih servera, ali nisam naznačio. Evo sad, sve iz Chrome, WiFi:

Telekom server:

Verat:

SBB:

dzonihsv · 02.10.2012

Torentovaćeš celu noć, ima vremena. Inače, ti speedtest-ovi su bitni, da se makar malo vidi interkonekcija.

Ujedno, ako te ne mrzi, odradi ping i tracert na sledeće ip adrese: da vidimo razliku u odnosu od pre mesec i nešto dana.

173.194.35.180 - google
66.220.152.32 - facebook
94.75.245.77 - bench

Odradi sve u jednom cmd prozoru, kopiraj i postavi u spoiler tagu.

Dodaću i ip adrese tih servera sa speedtest-a za par minuta (i kod njih odradi trace), da vidimo da l' paketi idu van države ili ne.

edit: dodato

212.200.189.118 - Telekom Srbija
217.26.64.149 - Verat
89.216.2.122 - SBB
130.180.224.194 - Targo Telekom

kibicer · 02.10.2012

Obećavam, uradiću ujutro, već sam u rem fazi....

dzonihsv · 02.10.2012

Ok.

Malo sam ja tu pingovao i tracert-ovao sa SBB-a... sad je izgleda i Targo u Sox-u. Tako da nema više saobraćaja van države, da bi se došlo do podataka unutar iste.

goran064 · 02.10.2012

Pih,resih problem.
Bilo jedo enskripcije.Samo mi nije jasno kad sam to pomerio sa AES.
Probao sam da se konektujem preko mobilnog pa nije hteo da prihvati konekciju tako da mi je to otvorilo oci,mada mi nije jasno da sam uopste i imao vezu.:lupko:

kibicer · 02.10.2012

dzonihsv je napisao(la):
Torentovaćeš celu noć, ima vremena. Inače, ti speedtest-ovi su bitni, da se makar malo vidi interkonekcija.

Ujedno, ako te ne mrzi, odradi ping i tracert na sledeće ip adrese: da vidimo razliku u odnosu od pre mesec i nešto dana.

173.194.35.180 - google
66.220.152.32 - facebook
94.75.245.77 - bench

Odradi sve u jednom cmd prozoru, kopiraj i postavi u spoiler tagu.

Dodaću i ip adrese tih servera sa speedtest-a za par minuta (i kod njih odradi trace), da vidimo da l' paketi idu van države ili ne.

edit: dodato

212.200.189.118 - Telekom Srbija
217.26.64.149 - Verat
89.216.2.122 - SBB
130.180.224.194 - Targo Telekom

Evo

Microsoft Windows XP [Version 5.1.2600]

C:\>ping 173.194.35.180

Pinging 173.194.35.180 with 32 bytes of data:

Reply from 173.194.35.180: bytes=32 time=35ms TTL=54
Reply from 173.194.35.180: bytes=32 time=35ms TTL=54
Reply from 173.194.35.180: bytes=32 time=33ms TTL=54
Reply from 173.194.35.180: bytes=32 time=10ms TTL=54

Ping statistics for 173.194.35.180:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 35ms, Average = 28ms

C:\>tracert 173.194.35.180

Tracing route to muc03s02-in-f20.1e100.net [173.194.35.180]
over a maximum of 30 hops:

1 1 ms 4294967273 ms 4294967273 ms 192.168.1.1
2 2 ms 4294967275 ms 5 ms 130.180.240.1
3 6 ms 4294967274 ms 4294967274 ms 130.180.225.5
4 22 ms 1 ms 13 ms abctrgovina-06.05.1999-ts15.16-r1.gw.siol.net [2
12.30.65.197]
5 18 ms 4294967290 ms 17 ms 95.176.253.16
6 * * * Request timed out.
7 44 ms 12 ms 13 ms 209.85.243.121
8 33 ms 8 ms 8 ms 216.239.48.144
9 37 ms 9 ms 13 ms 209.85.250.39
10 64 ms 34 ms 8 ms muc03s02-in-f20.1e100.net [173.194.35.180]

Trace complete.

C:\>ping 66.220.152.32

Pinging 66.220.152.32 with 32 bytes of data:

Reply from 66.220.152.32: bytes=32 time=107ms TTL=243
Reply from 66.220.152.32: bytes=32 time=134ms TTL=243
Reply from 66.220.152.32: bytes=32 time=140ms TTL=243
Reply from 66.220.152.32: bytes=32 time=133ms TTL=243

Ping statistics for 66.220.152.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 107ms, Maximum = 140ms, Average = 128ms

C:\>tracert 66.220.152.32

Tracing route to www-slb-11-09-frc1.facebook.com [66.220.152.32]
over a maximum of 30 hops:

1 4294967273 ms 4294967273 ms 4294967273 ms 192.168.1.1
2 4294967276 ms 4294967274 ms 4294967275 ms 130.180.240.1
3 2 ms 4294967273 ms 4294967274 ms 130.180.225.5
4 4294967295 ms <1 ms 4294967294 ms abctrgovina-06.05.1999-ts15.16-r1.gw
.siol.net [212.30.65.197]
5 22 ms 6 ms 7 ms 95.176.253.20
6 98 ms 97 ms 140 ms ae1.br01.fra1.tfbnw.net [80.81.194.40]
7 147 ms 110 ms 107 ms xe-2-2-0.bb02.iad2.tfbnw.net [204.15.20.221]
8 111 ms 109 ms 109 ms ae9.bb04.frc1.tfbnw.net [31.13.24.86]
9 107 ms 105 ms 107 ms ae4.dr03.frc1.tfbnw.net [31.13.27.71]
10 126 ms 115 ms 105 ms po1020.csw09c.frc1.tfbnw.net [31.13.26.133]
11 132 ms 109 ms 111 ms www-slb-11-09-frc1.facebook.com [66.220.152.32]

Trace complete.

C:\>ping 94.75.245.77

Pinging 94.75.245.77 with 32 bytes of data:

Reply from 94.75.245.77: bytes=32 time=42ms TTL=48
Reply from 94.75.245.77: bytes=32 time=66ms TTL=48
Reply from 94.75.245.77: bytes=32 time=67ms TTL=48
Reply from 94.75.245.77: bytes=32 time=43ms TTL=48

Ping statistics for 94.75.245.77:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 67ms, Average = 54ms

C:\>tracert 94.75.245.77

Tracing route to benchmark.rs [94.75.245.77]
over a maximum of 30 hops:

1 1 ms 4294967273 ms 4294967273 ms 192.168.1.1
2 8 ms 4294967274 ms 4294967276 ms 130.180.240.1
3 4294967274 ms 4294967275 ms 2 ms 130.180.225.5
4 66 ms 4294967295 ms 22 ms abctrgovina-06.05.1999-ts15.16-r1.gw.siol.
net [212.30.65.197]
5 <1 ms <1 ms 4294967295 ms 95.176.253.20
6 41 ms 20 ms 26 ms decix.jun.tc2.leaseweb.net [80.81.193.246]
7 90 ms 51 ms 81 ms po80.sr2.evo.leaseweb.net [62.212.80.74]
8 65 ms 41 ms 17 ms benchmark.rs [94.75.245.77]

Trace complete.

C:\>ping 212.200.189.118

Pinging 212.200.189.118 with 32 bytes of data:

Reply from 212.200.189.118: bytes=32 time=-21ms TTL=54
Reply from 212.200.189.118: bytes=32 time=3ms TTL=54
Reply from 212.200.189.118: bytes=32 time=7ms TTL=54
Reply from 212.200.189.118: bytes=32 time=-20ms TTL=54

Ping statistics for 212.200.189.118:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = -20ms, Average = 1073741816ms

C:\>tracert 212.200.189.118

Tracing route to 212-200-189-118.static.isp.telekom.rs [212.200.189.118]
over a maximum of 30 hops:

1 4294967273 ms 4294967273 ms 4294967274 ms 192.168.1.1
2 4294967274 ms 4294967278 ms 4294967273 ms 130.180.240.1
3 4294967277 ms 4294967273 ms 4294967273 ms 130.180.225.5
4 4294967285 ms 2 ms 27 ms 130.180.225.2
5 4294967277 ms 4294967276 ms 4294967274 ms telekom.sox.rs [193.105.163.38
]
6 2 ms 4294967275 ms 4294967275 ms 212.200.6.186
7 3 ms 4294967276 ms 4294967275 ms 212.200.227.229
8 2 ms 4294967274 ms 4294967275 ms 212.200.232.90
9 2 ms 4294967274 ms 4294967275 ms 212.200.17.9
10 3 ms 4294967274 ms 4294967275 ms 212-200-191-250.static.isp.telekom.r
s [212.200.191.250]
11 2 ms 4294967279 ms 3 ms 212-200-189-118.static.isp.telekom.rs [212
.200.189.118]

Trace complete.

C:\>ping 217.26.64.149

Pinging 217.26.64.149 with 32 bytes of data:

Reply from 217.26.64.149: bytes=32 time=2ms TTL=55
Reply from 217.26.64.149: bytes=32 time=3ms TTL=55
Reply from 217.26.64.149: bytes=32 time=27ms TTL=55
Reply from 217.26.64.149: bytes=32 time=28ms TTL=55

Ping statistics for 217.26.64.149:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 28ms, Average = 15ms

C:\>tracert 217.26.64.149

Tracing route to metrics.verat.net [217.26.64.149]
over a maximum of 30 hops:

1 1 ms 4294967277 ms 4294967274 ms 192.168.1.1
2 4294967278 ms 5 ms 45 ms 130.180.240.1
3 4294967275 ms 4294967276 ms 4294967273 ms 130.180.225.5
4 4294967274 ms 4294967275 ms 4294967274 ms 130.180.225.2
5 4294967275 ms 4294967275 ms 4294967274 ms verat.sox.rs [193.105.163.19]

6 3 ms 2 ms 2 ms powerslave.noc.verat.net [62.108.96.68]
7 6 ms 4294967274 ms 4294967274 ms metrics.verat.net [217.26.64.149]

Trace complete.

C:\>ping 89.216.2.122

Pinging 89.216.2.122 with 32 bytes of data:

Reply from 89.216.2.122: bytes=32 time=7ms TTL=57
Reply from 89.216.2.122: bytes=32 time=26ms TTL=57
Reply from 89.216.2.122: bytes=32 time=30ms TTL=57
Reply from 89.216.2.122: bytes=32 time=2ms TTL=57

Ping statistics for 89.216.2.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 30ms, Average = 16ms

C:\>tracert 89.216.2.122

Tracing route to mirror.sbb.rs [89.216.2.122]
over a maximum of 30 hops:

1 1 ms 4294967273 ms 4294967273 ms 192.168.1.1
2 4294967274 ms 4294967274 ms 4294967274 ms 130.180.240.1
3 4294967274 ms 1 ms 4294967274 ms 130.180.225.5
4 2 ms 4294967277 ms 4294967274 ms 130.180.225.2
5 4294967278 ms 4294967276 ms 4294967284 ms sbb.sox.rs [193.105.163.37]
6 2 ms 4294967274 ms 4294967274 ms bg-du-m-1-vl99.sbb.rs [89.216.5.74]

7 3 ms 4294967275 ms 4294967275 ms bg-ne-m-1-te0-0-0-0.sbb.rs [89.216.8
.146]
8 2 ms 4294967276 ms 4294967274 ms mirror.sbb.rs [89.216.2.122]

Trace complete.

C:\>ping 130.180.224.194

Pinging 130.180.224.194 with 32 bytes of data:

Reply from 130.180.224.194: bytes=32 time=2ms TTL=62
Reply from 130.180.224.194: bytes=32 time=2ms TTL=62
Reply from 130.180.224.194: bytes=32 time=28ms TTL=62
Reply from 130.180.224.194: bytes=32 time=3ms TTL=62

Ping statistics for 130.180.224.194:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 28ms, Average = 8ms

C:\>tracert 130.180.224.194

Tracing route to 130.180.224.194 over a maximum of 30 hops

1 1 ms 4294967273 ms 4294967274 ms 192.168.1.1
2 1 ms 4294967275 ms 1 ms 130.180.240.1
3 27 ms 3 ms 4294967275 ms 130.180.224.194

Trace complete.

C:\>

Mil0sbeo · 02.10.2012

Na SOX-u su, tako da tu ne bi trebalo da bude problema.

Kod:

C:\Users\milosi>ping 130.180.224.194

Pinging 130.180.224.194 with 32 bytes of data:
Reply from 130.180.224.194: bytes=32 time=1ms TTL=58
Reply from 130.180.224.194: bytes=32 time=1ms TTL=58
Reply from 130.180.224.194: bytes=32 time=1ms TTL=58
Reply from 130.180.224.194: bytes=32 time=1ms TTL=58

Ping statistics for 130.180.224.194:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms

Vuk · 02.10.2012

kibicer je napisao(la):
Evo

Microsoft Windows XP [Version 5.1.2600]

C:\>ping 173.194.35.180

Pinging 173.194.35.180 with 32 bytes of data:

Reply from 173.194.35.180: bytes=32 time=35ms TTL=54
Reply from 173.194.35.180: bytes=32 time=35ms TTL=54
Reply from 173.194.35.180: bytes=32 time=33ms TTL=54
Reply from 173.194.35.180: bytes=32 time=10ms TTL=54

Ping statistics for 173.194.35.180:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 35ms, Average = 28ms

C:\>tracert 173.194.35.180

Tracing route to muc03s02-in-f20.1e100.net [173.194.35.180]
over a maximum of 30 hops:

1 1 ms 4294967273 ms 4294967273 ms 192.168.1.1
2 2 ms 4294967275 ms 5 ms 130.180.240.1
3 6 ms 4294967274 ms 4294967274 ms 130.180.225.5
4 22 ms 1 ms 13 ms abctrgovina-06.05.1999-ts15.16-r1.gw.siol.net [2
12.30.65.197]
5 18 ms 4294967290 ms 17 ms 95.176.253.16
6 * * * Request timed out.
7 44 ms 12 ms 13 ms 209.85.243.121
8 33 ms 8 ms 8 ms 216.239.48.144
9 37 ms 9 ms 13 ms 209.85.250.39
10 64 ms 34 ms 8 ms muc03s02-in-f20.1e100.net [173.194.35.180]

Trace complete.

C:\>ping 66.220.152.32

Pinging 66.220.152.32 with 32 bytes of data:

Reply from 66.220.152.32: bytes=32 time=107ms TTL=243
Reply from 66.220.152.32: bytes=32 time=134ms TTL=243
Reply from 66.220.152.32: bytes=32 time=140ms TTL=243
Reply from 66.220.152.32: bytes=32 time=133ms TTL=243

Ping statistics for 66.220.152.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 107ms, Maximum = 140ms, Average = 128ms

C:\>tracert 66.220.152.32

Tracing route to www-slb-11-09-frc1.facebook.com [66.220.152.32]
over a maximum of 30 hops:

1 4294967273 ms 4294967273 ms 4294967273 ms 192.168.1.1
2 4294967276 ms 4294967274 ms 4294967275 ms 130.180.240.1
3 2 ms 4294967273 ms 4294967274 ms 130.180.225.5
4 4294967295 ms <1 ms 4294967294 ms abctrgovina-06.05.1999-ts15.16-r1.gw
.siol.net [212.30.65.197]
5 22 ms 6 ms 7 ms 95.176.253.20
6 98 ms 97 ms 140 ms ae1.br01.fra1.tfbnw.net [80.81.194.40]
7 147 ms 110 ms 107 ms xe-2-2-0.bb02.iad2.tfbnw.net [204.15.20.221]
8 111 ms 109 ms 109 ms ae9.bb04.frc1.tfbnw.net [31.13.24.86]
9 107 ms 105 ms 107 ms ae4.dr03.frc1.tfbnw.net [31.13.27.71]
10 126 ms 115 ms 105 ms po1020.csw09c.frc1.tfbnw.net [31.13.26.133]
11 132 ms 109 ms 111 ms www-slb-11-09-frc1.facebook.com [66.220.152.32]

Trace complete.

C:\>ping 94.75.245.77

Pinging 94.75.245.77 with 32 bytes of data:

Reply from 94.75.245.77: bytes=32 time=42ms TTL=48
Reply from 94.75.245.77: bytes=32 time=66ms TTL=48
Reply from 94.75.245.77: bytes=32 time=67ms TTL=48
Reply from 94.75.245.77: bytes=32 time=43ms TTL=48

Ping statistics for 94.75.245.77:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 67ms, Average = 54ms

C:\>tracert 94.75.245.77

Tracing route to benchmark.rs [94.75.245.77]
over a maximum of 30 hops:

1 1 ms 4294967273 ms 4294967273 ms 192.168.1.1
2 8 ms 4294967274 ms 4294967276 ms 130.180.240.1
3 4294967274 ms 4294967275 ms 2 ms 130.180.225.5
4 66 ms 4294967295 ms 22 ms abctrgovina-06.05.1999-ts15.16-r1.gw.siol.
net [212.30.65.197]
5 <1 ms <1 ms 4294967295 ms 95.176.253.20
6 41 ms 20 ms 26 ms decix.jun.tc2.leaseweb.net [80.81.193.246]
7 90 ms 51 ms 81 ms po80.sr2.evo.leaseweb.net [62.212.80.74]
8 65 ms 41 ms 17 ms benchmark.rs [94.75.245.77]

Trace complete.

C:\>ping 212.200.189.118

Pinging 212.200.189.118 with 32 bytes of data:

Reply from 212.200.189.118: bytes=32 time=-21ms TTL=54
Reply from 212.200.189.118: bytes=32 time=3ms TTL=54
Reply from 212.200.189.118: bytes=32 time=7ms TTL=54
Reply from 212.200.189.118: bytes=32 time=-20ms TTL=54

Ping statistics for 212.200.189.118:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = -20ms, Average = 1073741816ms

C:\>tracert 212.200.189.118

Tracing route to 212-200-189-118.static.isp.telekom.rs [212.200.189.118]
over a maximum of 30 hops:

1 4294967273 ms 4294967273 ms 4294967274 ms 192.168.1.1
2 4294967274 ms 4294967278 ms 4294967273 ms 130.180.240.1
3 4294967277 ms 4294967273 ms 4294967273 ms 130.180.225.5
4 4294967285 ms 2 ms 27 ms 130.180.225.2
5 4294967277 ms 4294967276 ms 4294967274 ms telekom.sox.rs [193.105.163.38
]
6 2 ms 4294967275 ms 4294967275 ms 212.200.6.186
7 3 ms 4294967276 ms 4294967275 ms 212.200.227.229
8 2 ms 4294967274 ms 4294967275 ms 212.200.232.90
9 2 ms 4294967274 ms 4294967275 ms 212.200.17.9
10 3 ms 4294967274 ms 4294967275 ms 212-200-191-250.static.isp.telekom.r
s [212.200.191.250]
11 2 ms 4294967279 ms 3 ms 212-200-189-118.static.isp.telekom.rs [212
.200.189.118]

Trace complete.

C:\>ping 217.26.64.149

Pinging 217.26.64.149 with 32 bytes of data:

Reply from 217.26.64.149: bytes=32 time=2ms TTL=55
Reply from 217.26.64.149: bytes=32 time=3ms TTL=55
Reply from 217.26.64.149: bytes=32 time=27ms TTL=55
Reply from 217.26.64.149: bytes=32 time=28ms TTL=55

Ping statistics for 217.26.64.149:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 28ms, Average = 15ms

C:\>tracert 217.26.64.149

Tracing route to metrics.verat.net [217.26.64.149]
over a maximum of 30 hops:

1 1 ms 4294967277 ms 4294967274 ms 192.168.1.1
2 4294967278 ms 5 ms 45 ms 130.180.240.1
3 4294967275 ms 4294967276 ms 4294967273 ms 130.180.225.5
4 4294967274 ms 4294967275 ms 4294967274 ms 130.180.225.2
5 4294967275 ms 4294967275 ms 4294967274 ms verat.sox.rs [193.105.163.19]

6 3 ms 2 ms 2 ms powerslave.noc.verat.net [62.108.96.68]
7 6 ms 4294967274 ms 4294967274 ms metrics.verat.net [217.26.64.149]

Trace complete.

C:\>ping 89.216.2.122

Pinging 89.216.2.122 with 32 bytes of data:

Reply from 89.216.2.122: bytes=32 time=7ms TTL=57
Reply from 89.216.2.122: bytes=32 time=26ms TTL=57
Reply from 89.216.2.122: bytes=32 time=30ms TTL=57
Reply from 89.216.2.122: bytes=32 time=2ms TTL=57

Ping statistics for 89.216.2.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 30ms, Average = 16ms

C:\>tracert 89.216.2.122

Tracing route to mirror.sbb.rs [89.216.2.122]
over a maximum of 30 hops:

1 1 ms 4294967273 ms 4294967273 ms 192.168.1.1
2 4294967274 ms 4294967274 ms 4294967274 ms 130.180.240.1
3 4294967274 ms 1 ms 4294967274 ms 130.180.225.5
4 2 ms 4294967277 ms 4294967274 ms 130.180.225.2
5 4294967278 ms 4294967276 ms 4294967284 ms sbb.sox.rs [193.105.163.37]
6 2 ms 4294967274 ms 4294967274 ms bg-du-m-1-vl99.sbb.rs [89.216.5.74]

7 3 ms 4294967275 ms 4294967275 ms bg-ne-m-1-te0-0-0-0.sbb.rs [89.216.8
.146]
8 2 ms 4294967276 ms 4294967274 ms mirror.sbb.rs [89.216.2.122]

Trace complete.

C:\>ping 130.180.224.194

Pinging 130.180.224.194 with 32 bytes of data:

Reply from 130.180.224.194: bytes=32 time=2ms TTL=62
Reply from 130.180.224.194: bytes=32 time=2ms TTL=62
Reply from 130.180.224.194: bytes=32 time=28ms TTL=62
Reply from 130.180.224.194: bytes=32 time=3ms TTL=62

Ping statistics for 130.180.224.194:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 28ms, Average = 8ms

C:\>tracert 130.180.224.194

Tracing route to 130.180.224.194 over a maximum of 30 hops

1 1 ms 4294967273 ms 4294967274 ms 192.168.1.1
2 1 ms 4294967275 ms 1 ms 130.180.240.1
3 27 ms 3 ms 4294967275 ms 130.180.224.194

Trace complete.

C:\>

Da li si ove testove radio sa wifi-a ili sa lan porta i da li si downloadovao ili uploadovao nesto dok si radio ove testove?
Pitam zato sto su oscilatorni ping rezultati prilicno.

Targo Telekom

Slavan

Slavan

Slavan

Slavan

Čuven

Slavan

Slavan

Cenjen

Slavan

Slavan

Slavan

Čuven

Čuven

Cenjen

Slavan

Slavan

Čuven

Čuven

Čuven

Čuven

Slavan

Čuven

Čuven

Čuven

Čuven

Čuven

Slavan

Čuven

Slavan

Čuven