Ping na VeratNet-u
- Začetnik teme Fidel
- Datum pokretanja
Vertigo
Čuven
- Učlanjen(a)
- 15.05.2002
- Poruke
- 333
- Poena
- 620
Beograd, centrala Zvezdara (240x-xxx), paket 256/64
Ka Veratu:
C:\Documents and Settings\Milan>ping www.verat.net -n 10
Pinging home.verat.net [85.222.160.152] with 32 bytes of data:
Reply from 85.222.160.152: bytes=32 time=37ms TTL=62
Reply from 85.222.160.152: bytes=32 time=37ms TTL=62
Reply from 85.222.160.152: bytes=32 time=38ms TTL=62
Reply from 85.222.160.152: bytes=32 time=37ms TTL=62
Reply from 85.222.160.152: bytes=32 time=37ms TTL=62
Reply from 85.222.160.152: bytes=32 time=74ms TTL=62
Reply from 85.222.160.152: bytes=32 time=35ms TTL=62
Reply from 85.222.160.152: bytes=32 time=34ms TTL=62
Reply from 85.222.160.152: bytes=32 time=36ms TTL=62
Reply from 85.222.160.152: bytes=32 time=34ms TTL=62
Ping statistics for 85.222.160.152:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 74ms, Average = 39ms
Ka sbb-u:
C:\Documents and Settings\Milan>ping www.sbb.co.yu -n 10
Pinging www.sbb.co.yu [82.117.194.4] with 32 bytes of data:
Reply from 82.117.194.4: bytes=32 time=73ms TTL=55
Reply from 82.117.194.4: bytes=32 time=32ms TTL=55
Reply from 82.117.194.4: bytes=32 time=32ms TTL=55
Reply from 82.117.194.4: bytes=32 time=34ms TTL=55
Reply from 82.117.194.4: bytes=32 time=32ms TTL=55
Reply from 82.117.194.4: bytes=32 time=32ms TTL=55
Reply from 82.117.194.4: bytes=32 time=186ms TTL=55
Reply from 82.117.194.4: bytes=32 time=37ms TTL=55
Reply from 82.117.194.4: bytes=32 time=37ms TTL=55
Reply from 82.117.194.4: bytes=32 time=37ms TTL=55
Ping statistics for 82.117.194.4:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 186ms, Average = 53ms
Ka google-u:
C:\Documents and Settings\Milan>ping www.google.com -n 10
Pinging www.l.google.com [64.233.183.104] with 32 bytes of data:
Reply from 64.233.183.104: bytes=32 time=66ms TTL=241
Reply from 64.233.183.104: bytes=32 time=65ms TTL=241
Reply from 64.233.183.104: bytes=32 time=72ms TTL=241
Reply from 64.233.183.104: bytes=32 time=72ms TTL=241
Reply from 64.233.183.104: bytes=32 time=71ms TTL=241
Reply from 64.233.183.104: bytes=32 time=69ms TTL=241
Reply from 64.233.183.104: bytes=32 time=87ms TTL=241
Reply from 64.233.183.104: bytes=32 time=68ms TTL=241
Reply from 64.233.183.104: bytes=32 time=65ms TTL=241
Reply from 64.233.183.104: bytes=32 time=70ms TTL=241
Ping statistics for 64.233.183.104:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 65ms, Maximum = 87ms, Average = 70ms
Ka yahoo-u:
C:\Documents and Settings\Milan>ping www.yahoo.com -n 10
Pinging www.yahoo-ht3.akadns.net [87.248.113.14] with 32 bytes of data:
Reply from 87.248.113.14: bytes=32 time=87ms TTL=51
Reply from 87.248.113.14: bytes=32 time=87ms TTL=51
Reply from 87.248.113.14: bytes=32 time=93ms TTL=51
Reply from 87.248.113.14: bytes=32 time=91ms TTL=51
Reply from 87.248.113.14: bytes=32 time=91ms TTL=51
Reply from 87.248.113.14: bytes=32 time=91ms TTL=51
Reply from 87.248.113.14: bytes=32 time=89ms TTL=51
Reply from 87.248.113.14: bytes=32 time=89ms TTL=51
Reply from 87.248.113.14: bytes=32 time=88ms TTL=51
Reply from 87.248.113.14: bytes=32 time=87ms TTL=51
Ping statistics for 87.248.113.14:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 93ms, Average = 89ms
Eto, otprilike bi to bilo to.
Ono sto sam primetio da prema lokalnim serverima, pa i običnim peerovima (kad pingujem nekog drugara koji je na beotelu) postoje odzivi koji, otprilike, svaki 10. put drastično odstupe od uobičajenih vrednosti. Iskreno, nisam bio siguran da li je ovo bilo do mene ili druga, ali kapiram, da pošto je otvorena ovakva tema, nisam jedini koji primećuje malko pogoršanje u kvalitetu.
Iskreno, ovo meni i ne smeta mnogo, jer i je ovakav kakav je, ping je u granicama normale koje su meni potrebne za svaki normalan rad. Ono čega se pribojavam je ovo povećanje download brzine koje se najavljuje za 1. avgust. Ako to bude ispraćeno adekvatnim proširenjem linka, neće biti zime. Ako ne, bojim se eventualnih request timeouta, što stvarno može da zagorča život (naročito u online igranju).
Videćemo za koji dan kad se pređe na 512/64 kakve su promene, ako ih ima uopšte, pa ću baciti nove vrednosti pinga.
Ka Veratu:
C:\Documents and Settings\Milan>ping www.verat.net -n 10
Pinging home.verat.net [85.222.160.152] with 32 bytes of data:
Reply from 85.222.160.152: bytes=32 time=37ms TTL=62
Reply from 85.222.160.152: bytes=32 time=37ms TTL=62
Reply from 85.222.160.152: bytes=32 time=38ms TTL=62
Reply from 85.222.160.152: bytes=32 time=37ms TTL=62
Reply from 85.222.160.152: bytes=32 time=37ms TTL=62
Reply from 85.222.160.152: bytes=32 time=74ms TTL=62
Reply from 85.222.160.152: bytes=32 time=35ms TTL=62
Reply from 85.222.160.152: bytes=32 time=34ms TTL=62
Reply from 85.222.160.152: bytes=32 time=36ms TTL=62
Reply from 85.222.160.152: bytes=32 time=34ms TTL=62
Ping statistics for 85.222.160.152:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 74ms, Average = 39ms
Ka sbb-u:
C:\Documents and Settings\Milan>ping www.sbb.co.yu -n 10
Pinging www.sbb.co.yu [82.117.194.4] with 32 bytes of data:
Reply from 82.117.194.4: bytes=32 time=73ms TTL=55
Reply from 82.117.194.4: bytes=32 time=32ms TTL=55
Reply from 82.117.194.4: bytes=32 time=32ms TTL=55
Reply from 82.117.194.4: bytes=32 time=34ms TTL=55
Reply from 82.117.194.4: bytes=32 time=32ms TTL=55
Reply from 82.117.194.4: bytes=32 time=32ms TTL=55
Reply from 82.117.194.4: bytes=32 time=186ms TTL=55
Reply from 82.117.194.4: bytes=32 time=37ms TTL=55
Reply from 82.117.194.4: bytes=32 time=37ms TTL=55
Reply from 82.117.194.4: bytes=32 time=37ms TTL=55
Ping statistics for 82.117.194.4:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 186ms, Average = 53ms
Ka google-u:
C:\Documents and Settings\Milan>ping www.google.com -n 10
Pinging www.l.google.com [64.233.183.104] with 32 bytes of data:
Reply from 64.233.183.104: bytes=32 time=66ms TTL=241
Reply from 64.233.183.104: bytes=32 time=65ms TTL=241
Reply from 64.233.183.104: bytes=32 time=72ms TTL=241
Reply from 64.233.183.104: bytes=32 time=72ms TTL=241
Reply from 64.233.183.104: bytes=32 time=71ms TTL=241
Reply from 64.233.183.104: bytes=32 time=69ms TTL=241
Reply from 64.233.183.104: bytes=32 time=87ms TTL=241
Reply from 64.233.183.104: bytes=32 time=68ms TTL=241
Reply from 64.233.183.104: bytes=32 time=65ms TTL=241
Reply from 64.233.183.104: bytes=32 time=70ms TTL=241
Ping statistics for 64.233.183.104:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 65ms, Maximum = 87ms, Average = 70ms
Ka yahoo-u:
C:\Documents and Settings\Milan>ping www.yahoo.com -n 10
Pinging www.yahoo-ht3.akadns.net [87.248.113.14] with 32 bytes of data:
Reply from 87.248.113.14: bytes=32 time=87ms TTL=51
Reply from 87.248.113.14: bytes=32 time=87ms TTL=51
Reply from 87.248.113.14: bytes=32 time=93ms TTL=51
Reply from 87.248.113.14: bytes=32 time=91ms TTL=51
Reply from 87.248.113.14: bytes=32 time=91ms TTL=51
Reply from 87.248.113.14: bytes=32 time=91ms TTL=51
Reply from 87.248.113.14: bytes=32 time=89ms TTL=51
Reply from 87.248.113.14: bytes=32 time=89ms TTL=51
Reply from 87.248.113.14: bytes=32 time=88ms TTL=51
Reply from 87.248.113.14: bytes=32 time=87ms TTL=51
Ping statistics for 87.248.113.14:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 93ms, Average = 89ms
Eto, otprilike bi to bilo to.
Ono sto sam primetio da prema lokalnim serverima, pa i običnim peerovima (kad pingujem nekog drugara koji je na beotelu) postoje odzivi koji, otprilike, svaki 10. put drastično odstupe od uobičajenih vrednosti. Iskreno, nisam bio siguran da li je ovo bilo do mene ili druga, ali kapiram, da pošto je otvorena ovakva tema, nisam jedini koji primećuje malko pogoršanje u kvalitetu.
Iskreno, ovo meni i ne smeta mnogo, jer i je ovakav kakav je, ping je u granicama normale koje su meni potrebne za svaki normalan rad. Ono čega se pribojavam je ovo povećanje download brzine koje se najavljuje za 1. avgust. Ako to bude ispraćeno adekvatnim proširenjem linka, neće biti zime. Ako ne, bojim se eventualnih request timeouta, što stvarno može da zagorča život (naročito u online igranju).
Videćemo za koji dan kad se pređe na 512/64 kakve su promene, ako ih ima uopšte, pa ću baciti nove vrednosti pinga.
Mister_D
Čuven
- Učlanjen(a)
- 02.05.2005
- Poruke
- 382
- Poena
- 620
Moja oprema
- CPU & Cooler
- AMD 5600X, Cooler master Hyper 212 Black
- Matična ploča
- MSI B550 Torpedo
- RAM
- 4x8GB 3600 DDR4
- GPU
- Sapphire RX7800XT Nitro+
- Storage
- Samsung 990Pro 1TB, Kingspec 2TB NVME
- Zvuk
- Integrusa, Razer Kraken Green, Technics SA-AX540
- PSU
- ASUS ROG 850G
- Kućište
- Antec C8 Black, 4x140mm, 6x120mm
- Monitor
- HP Omen 32q
- Miš & tastatura
- Cooler Master MM720, Genesis RX22
- Pristup internetu
- Optički internet
- ADSL
Novi Beograd, paket 768/192k
Pinging home.verat.net [85.222.160.152] with 32 bytes of data:
Reply from 85.222.160.152: bytes=32 time=14ms TTL=61
Reply from 85.222.160.152: bytes=32 time=15ms TTL=61
Reply from 85.222.160.152: bytes=32 time=14ms TTL=61
Reply from 85.222.160.152: bytes=32 time=13ms TTL=61
.
.
.
Reply from 85.222.160.152: bytes=32 time=14ms TTL=61
Reply from 85.222.160.152: bytes=32 time=15ms TTL=61
Reply from 85.222.160.152: bytes=32 time=15ms TTL=61
Reply from 85.222.160.152: bytes=32 time=15ms TTL=61
Ping statistics for 85.222.160.152:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 15ms, Average = 14ms
----------------------------
Pinging www.sbb.co.yu [82.117.194.4] with 32 bytes of data:
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
Reply from 82.117.194.4: bytes=32 time=15ms TTL=54
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
.
.
.
Reply from 82.117.194.4: bytes=32 time=13ms TTL=54
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
Ping statistics for 82.117.194.4:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 16ms, Average = 14ms
----------------------------
Pinging www.l.google.com [64.233.183.99] with 32 bytes of data:
Reply from 64.233.183.99: bytes=32 time=48ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
.
.
.
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=47ms TTL=240
Ping statistics for 64.233.183.99:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 50ms, Average = 48ms
Ping do gugla mi je ranije bio average 38-39ms,...ali i ovo je ok
----------------------------
Pinging www.yahoo-ht3.akadns.net [87.248.113.14] with 32 bytes of data:
Reply from 87.248.113.14: bytes=32 time=71ms TTL=50
Reply from 87.248.113.14: bytes=32 time=71ms TTL=50
Reply from 87.248.113.14: bytes=32 time=71ms TTL=50
Reply from 87.248.113.14: bytes=32 time=71ms TTL=50
.
.
.
Reply from 87.248.113.14: bytes=32 time=70ms TTL=50
Reply from 87.248.113.14: bytes=32 time=71ms TTL=50
Reply from 87.248.113.14: bytes=32 time=72ms TTL=50
Reply from 87.248.113.14: bytes=32 time=69ms TTL=50
Ping statistics for 87.248.113.14:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 72ms, Average = 70ms
Pinging home.verat.net [85.222.160.152] with 32 bytes of data:
Reply from 85.222.160.152: bytes=32 time=14ms TTL=61
Reply from 85.222.160.152: bytes=32 time=15ms TTL=61
Reply from 85.222.160.152: bytes=32 time=14ms TTL=61
Reply from 85.222.160.152: bytes=32 time=13ms TTL=61
.
.
.
Reply from 85.222.160.152: bytes=32 time=14ms TTL=61
Reply from 85.222.160.152: bytes=32 time=15ms TTL=61
Reply from 85.222.160.152: bytes=32 time=15ms TTL=61
Reply from 85.222.160.152: bytes=32 time=15ms TTL=61
Ping statistics for 85.222.160.152:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 15ms, Average = 14ms
----------------------------
Pinging www.sbb.co.yu [82.117.194.4] with 32 bytes of data:
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
Reply from 82.117.194.4: bytes=32 time=15ms TTL=54
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
.
.
.
Reply from 82.117.194.4: bytes=32 time=13ms TTL=54
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
Reply from 82.117.194.4: bytes=32 time=14ms TTL=54
Ping statistics for 82.117.194.4:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 16ms, Average = 14ms
----------------------------
Pinging www.l.google.com [64.233.183.99] with 32 bytes of data:
Reply from 64.233.183.99: bytes=32 time=48ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
.
.
.
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=47ms TTL=240
Ping statistics for 64.233.183.99:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 50ms, Average = 48ms
Ping do gugla mi je ranije bio average 38-39ms,...ali i ovo je ok
----------------------------
Pinging www.yahoo-ht3.akadns.net [87.248.113.14] with 32 bytes of data:
Reply from 87.248.113.14: bytes=32 time=71ms TTL=50
Reply from 87.248.113.14: bytes=32 time=71ms TTL=50
Reply from 87.248.113.14: bytes=32 time=71ms TTL=50
Reply from 87.248.113.14: bytes=32 time=71ms TTL=50
.
.
.
Reply from 87.248.113.14: bytes=32 time=70ms TTL=50
Reply from 87.248.113.14: bytes=32 time=71ms TTL=50
Reply from 87.248.113.14: bytes=32 time=72ms TTL=50
Reply from 87.248.113.14: bytes=32 time=69ms TTL=50
Ping statistics for 87.248.113.14:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 72ms, Average = 70ms
Woogley[MTS]
Slavan
- Učlanjen(a)
- 26.06.2005
- Poruke
- 293
- Poena
- 319
Mister_D, to se vec moze nazvati OK pingom i ako stvarno moze ADSL da ima takve pingove onda skidam kapu 
Takve prema SBB-u i Veratu sam imao na 256/128 SBB-u i sada imam na 512/256. Ipak dosta zavisi od paketa, da ne kazem od uploada
Takve prema SBB-u i Veratu sam imao na 256/128 SBB-u i sada imam na 512/256. Ipak dosta zavisi od paketa, da ne kazem od uploada
Mister_D
Čuven
- Učlanjen(a)
- 02.05.2005
- Poruke
- 382
- Poena
- 620
Moja oprema
- CPU & Cooler
- AMD 5600X, Cooler master Hyper 212 Black
- Matična ploča
- MSI B550 Torpedo
- RAM
- 4x8GB 3600 DDR4
- GPU
- Sapphire RX7800XT Nitro+
- Storage
- Samsung 990Pro 1TB, Kingspec 2TB NVME
- Zvuk
- Integrusa, Razer Kraken Green, Technics SA-AX540
- PSU
- ASUS ROG 850G
- Kućište
- Antec C8 Black, 4x140mm, 6x120mm
- Monitor
- HP Omen 32q
- Miš & tastatura
- Cooler Master MM720, Genesis RX22
- Pristup internetu
- Optički internet
- ADSL
Cak mislim da ni ovi moji pingovi nisu nesto posebno. Npr, dok sam imao 512k ping do gugla mi je bio 75-80ms, a na 768k najnize sto sam izmerio je bilo 36-37ms. Ortak koji ima Telekom 512k adsl vec sad ima oko 45ms ping. Drugi ortak na Sezamu oko 50ms. Mada ima i primera kada ljudima radi stvarno katastrofalno. Mene bas zanima koliko ce ovo udvostrucavanje brzine uticati na ping.
@ Mister D
Tvoj ping prema Google-u je neverovatan, za mene mislena imenica. Mozda ima veze s tvojom centralom a sigurno sa trostruko vecim protokom tvog paketa. Moja centrala, nekad dobra, je Krunski venac a paket 256/64. Sudeci po pingu OCAJ.
Jedino ne znam sto ti i Vertigo pingujete sa tako malo paketa, sa 100 ili manje paketa i kod mene je 0% gubitaka i mozda malo bolji odziv.
Tvoj ping prema Google-u je neverovatan, za mene mislena imenica. Mozda ima veze s tvojom centralom a sigurno sa trostruko vecim protokom tvog paketa. Moja centrala, nekad dobra, je Krunski venac a paket 256/64. Sudeci po pingu OCAJ.
Jedino ne znam sto ti i Vertigo pingujete sa tako malo paketa, sa 100 ili manje paketa i kod mene je 0% gubitaka i mozda malo bolji odziv.
Mister_D
Čuven
- Učlanjen(a)
- 02.05.2005
- Poruke
- 382
- Poena
- 620
Moja oprema
- CPU & Cooler
- AMD 5600X, Cooler master Hyper 212 Black
- Matična ploča
- MSI B550 Torpedo
- RAM
- 4x8GB 3600 DDR4
- GPU
- Sapphire RX7800XT Nitro+
- Storage
- Samsung 990Pro 1TB, Kingspec 2TB NVME
- Zvuk
- Integrusa, Razer Kraken Green, Technics SA-AX540
- PSU
- ASUS ROG 850G
- Kućište
- Antec C8 Black, 4x140mm, 6x120mm
- Monitor
- HP Omen 32q
- Miš & tastatura
- Cooler Master MM720, Genesis RX22
- Pristup internetu
- Optički internet
- ADSL
Evo za 1764 paketa, rezultat je maltene isti. Inace sa ortakom sa kojim delim net stalno igram CS zajedno, i sasvim lepo ide. Trojica kroz istu vezu vec nece da radi kako treba.
Pinging www.l.google.com [64.233.183.99] with 32 bytes of data:
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=48ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=52ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=48ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=48ms TTL=240
Reply from 64.233.183.99: bytes=32 time=48ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Ping statistics for 64.233.183.99:
Packets: Sent = 1764, Received = 1760, Lost = 4(0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 95ms, Average = 50ms
Pinging www.l.google.com [64.233.183.99] with 32 bytes of data:
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=48ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=52ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=48ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=48ms TTL=240
Reply from 64.233.183.99: bytes=32 time=48ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=50ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Reply from 64.233.183.99: bytes=32 time=51ms TTL=240
Reply from 64.233.183.99: bytes=32 time=49ms TTL=240
Ping statistics for 64.233.183.99:
Packets: Sent = 1764, Received = 1760, Lost = 4(0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 95ms, Average = 50ms
@ Mister_D
Vidim opet vise nego odlicne rezultate za Google. I jesam pitao za pingovanje sa vise paketa (1000 i vise) jer kod mene su onda vrlo velike oscilacije. Ti opet imas vrlo ujednacene vrednosti, kakve ja imam prema Veratu!, a meni zna maksimalna vrednost da se popne i na vise od 1000ms i to vise puta kad je Google u pitanju.
Vidim opet vise nego odlicne rezultate za Google. I jesam pitao za pingovanje sa vise paketa (1000 i vise) jer kod mene su onda vrlo velike oscilacije. Ti opet imas vrlo ujednacene vrednosti, kakve ja imam prema Veratu!, a meni zna maksimalna vrednost da se popne i na vise od 1000ms i to vise puta kad je Google u pitanju.
Mister_D
Čuven
- Učlanjen(a)
- 02.05.2005
- Poruke
- 382
- Poena
- 620
Moja oprema
- CPU & Cooler
- AMD 5600X, Cooler master Hyper 212 Black
- Matična ploča
- MSI B550 Torpedo
- RAM
- 4x8GB 3600 DDR4
- GPU
- Sapphire RX7800XT Nitro+
- Storage
- Samsung 990Pro 1TB, Kingspec 2TB NVME
- Zvuk
- Integrusa, Razer Kraken Green, Technics SA-AX540
- PSU
- ASUS ROG 850G
- Kućište
- Antec C8 Black, 4x140mm, 6x120mm
- Monitor
- HP Omen 32q
- Miš & tastatura
- Cooler Master MM720, Genesis RX22
- Pristup internetu
- Optički internet
- ADSL
Sta znam, mozda je tvoja linija podesena na interleaved path mod u centrali? Ako jeste, pokusaj da prebacis na fast path. Mada, koliko ja znam, korisnici se stavljaju na interleaved ako imaju smetnje na liniji, daleko su od centrale i sl. Pogledaj koliko ti je slabljenje. Meni je: DS Line Attenuation 27
US Line Attenuation 32
Path Mode Fast Path
Ni ja nisam siguran koje su optimalne vrednosti, pretpostavljam da je sto manje to bolje. Mozda imas problem i sa modemom (ruterom) koji koristis. Ja imam DLink 504, a probao sam i TPLink 8840 i ping je bio za nijansu visi.
US Line Attenuation 32
Path Mode Fast Path
Ni ja nisam siguran koje su optimalne vrednosti, pretpostavljam da je sto manje to bolje. Mozda imas problem i sa modemom (ruterom) koji koristis. Ja imam DLink 504, a probao sam i TPLink 8840 i ping je bio za nijansu visi.
Gde da pogledam DS Line Attenuation i US Line Attenuation? Pretpostavljam da interleaved path mod i fast path mod ne mogu ja da menjam.
Mister_D
Čuven
- Učlanjen(a)
- 02.05.2005
- Poruke
- 382
- Poena
- 620
Moja oprema
- CPU & Cooler
- AMD 5600X, Cooler master Hyper 212 Black
- Matična ploča
- MSI B550 Torpedo
- RAM
- 4x8GB 3600 DDR4
- GPU
- Sapphire RX7800XT Nitro+
- Storage
- Samsung 990Pro 1TB, Kingspec 2TB NVME
- Zvuk
- Integrusa, Razer Kraken Green, Technics SA-AX540
- PSU
- ASUS ROG 850G
- Kućište
- Antec C8 Black, 4x140mm, 6x120mm
- Monitor
- HP Omen 32q
- Miš & tastatura
- Cooler Master MM720, Genesis RX22
- Pristup internetu
- Optički internet
- ADSL
Trebalo bi da mozes da vidis u podesavanjima za modem (ruter). Meni se nalazi u Status/DSL status, i kod tebe je nesto slicno sigurno. Prebacivanje na fast path se radi u centrali, na tvoj zahtev provajderu (ako vec nisi podesen na fast).
@ Mister_D
U prilogu su sva podesavanja modema koja su mi dostupna, modem je Sagem 840. Sto se tipa veze tice, sutra trazim upit od telekoma preko verata. Najverovatnije je da je interleave jer je to izgleda po default-u.
Ajde ljudi, javljajte vas ping na Veratu.
U prilogu su sva podesavanja modema koja su mi dostupna, modem je Sagem 840. Sto se tipa veze tice, sutra trazim upit od telekoma preko verata. Najverovatnije je da je interleave jer je to izgleda po default-u.
Ajde ljudi, javljajte vas ping na Veratu.
Prilozi
Zar je moguce da se niko nije javio 13 dana? Zar Verat ima tako malo ADSL korisnika? I to Krunski venac, Beograd, ali naravno slobodno i za sve druge, cisto da se uporede rezultati.
Ljudi, imam ocajan odziv! Hocu da vidim da li da se mirim s tim ili da nesto preduzimam. Pingujte! 1000 i vise paketa.
Ljudi, imam ocajan odziv! Hocu da vidim da li da se mirim s tim ili da nesto preduzimam. Pingujte! 1000 i vise paketa.
Mister_D
Čuven
- Učlanjen(a)
- 02.05.2005
- Poruke
- 382
- Poena
- 620
Moja oprema
- CPU & Cooler
- AMD 5600X, Cooler master Hyper 212 Black
- Matična ploča
- MSI B550 Torpedo
- RAM
- 4x8GB 3600 DDR4
- GPU
- Sapphire RX7800XT Nitro+
- Storage
- Samsung 990Pro 1TB, Kingspec 2TB NVME
- Zvuk
- Integrusa, Razer Kraken Green, Technics SA-AX540
- PSU
- ASUS ROG 850G
- Kućište
- Antec C8 Black, 4x140mm, 6x120mm
- Monitor
- HP Omen 32q
- Miš & tastatura
- Cooler Master MM720, Genesis RX22
- Pristup internetu
- Optički internet
- ADSL
I meni je dosta losiji. Do gugla mi je oko 70ms, a nekad sam imao i ispod 40. Cini mi se da im je i dalje malo zagusen link. Recimo, ujutru je stabilan ping i dl je zakucan na 157KB, a popodne pocinje da skace ping a dl da pada i do trostruko. Valjda ce srediti, na Veratovom adsl-u sam vec dve i po godine, i generalno sam zadovoljan.
Goyakla
Čuven
- Učlanjen(a)
- 07.03.2005
- Poruke
- 2,667
- Poena
- 705
Pinging www.l.google.com [216.239.59.103] with 32 bytes of data:
Reply from 216.239.59.103: bytes=32 time=118ms TTL=242
Reply from 216.239.59.103: bytes=32 time=123ms TTL=242
Reply from 216.239.59.103: bytes=32 time=122ms TTL=242
Reply from 216.239.59.103: bytes=32 time=139ms TTL=242
Ping statistics for 216.239.59.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 118ms, Maximum = 139ms, Average = 125ms
Kragujevac, centrala Bubanj. 512/64
Radi mnogo loše od kad su povećali brzinu. Nekad radi normalno kad je manji saobraćaj (kasno noću i ujutru) a preko dana katastrofa, download od 300-400. Ping na CS-u uglavnom preko 120. Ozbiljno razmišljam da predjem kod nekog drugog :crash:
Reply from 216.239.59.103: bytes=32 time=118ms TTL=242
Reply from 216.239.59.103: bytes=32 time=123ms TTL=242
Reply from 216.239.59.103: bytes=32 time=122ms TTL=242
Reply from 216.239.59.103: bytes=32 time=139ms TTL=242
Ping statistics for 216.239.59.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 118ms, Maximum = 139ms, Average = 125ms
Kragujevac, centrala Bubanj. 512/64
Radi mnogo loše od kad su povećali brzinu. Nekad radi normalno kad je manji saobraćaj (kasno noću i ujutru) a preko dana katastrofa, download od 300-400. Ping na CS-u uglavnom preko 120. Ozbiljno razmišljam da predjem kod nekog drugog :crash:
Pinging www.yahoo-ht3.akadns.net [87.248.113.14] with 32 bytes of data:
Ping statistics for 87.248.113.14:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 122ms, Maximum = 144ms, Average = 132ms
Pinging www.l.google.com [64.233.183.147] with 32 bytes of data
Ping statistics for 64.233.183.147:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 143ms, Average = 129ms
Pinging home.verat.net [85.222.160.152] with 32 bytes of data:
Ping statistics for 85.222.160.152:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 24ms, Average = 19ms
Centrala je Krunski Venac, Beograd, a lokacija ADSL prikljucka je kod Kalenic pijace. Gubitak paketa je izrazen tek uvece, posle 20.00, i ide od 5-10%, da ne gresim dusu ponekad je i 0%. Ovo je radjeno u 15.51.
Ping statistics for 87.248.113.14:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 122ms, Maximum = 144ms, Average = 132ms
Pinging www.l.google.com [64.233.183.147] with 32 bytes of data
Ping statistics for 64.233.183.147:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 143ms, Average = 129ms
Pinging home.verat.net [85.222.160.152] with 32 bytes of data:
Ping statistics for 85.222.160.152:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 24ms, Average = 19ms
Centrala je Krunski Venac, Beograd, a lokacija ADSL prikljucka je kod Kalenic pijace. Gubitak paketa je izrazen tek uvece, posle 20.00, i ide od 5-10%, da ne gresim dusu ponekad je i 0%. Ovo je radjeno u 15.51.
