Riješeno

Ping jitter na Homeboxu

  • 1 April 2017
  • 5 odgovora
  • 2088 pregleda

  • Aktivni forumaš početnik
  • 10 odgovora
Uzeo sam homebox prije nekih mjesec dana i imam ping jitter u igrama, posto sam hardcore gamer jako mi to smeta. Znaci jitter je od 40ms do 75ms nekad zna polako se podizat i padat a nekad skoci toliko brzo da imam micro lag u game-u. Dali postoji nacin da se ustabili ping??

download mi je preko 20mbps..

jitter: http://www.pingtest.net/result/160351466.png
icon

Najbolji odgovor od klajo22 1 April 2017, 16:25

Pogledaj original

Odgovora 5

Razina korisnika 7
Bedž +3
Napisao sam ti u temi homebox, nema potrebe za novom temom. Zovi SZK i prati putanju do tehničara i objasni im problem.
mislim da sam nasao soluciju ili workaround, ugl downloadao i podesio pomocu basic tcp optimizer appa.. za sad sljaka bez jittera..
Bok @klajo22
Možeš li pokušati napraviti ping test prema Vipnetovom DNSu (212.91.97.3) kada primijetiš problem sa pingom? Čisto da provjerimo da li je generalno problem sa pingom ili nešto drugo.
sada sam skuzio da se ping jump desava svakih 10-20 sekundi skoci tipa ono za 20-30 i vrati se na normalan/bazican ping.. da li to moze bit do homebox usluge? jer na dsl-u mi je normalno radilo sve...

vidio sam negdje online isto da za ovaj ruter koji trenutno imam (zte_mf283+) postoji novija verzija software-a (trenutna mi je v1) a izasla je vec v3. Kad pokusam kliknut na ''Odaberite “Provjeri” za provjeravanje nove inačice'' softwarea izbaci mi da nema nadogradnji..
@VIP_MARKO Pinging 212.91.97.3 with 32 bytes of data:
Reply from 212.91.97.3: bytes=32 time=31ms TTL=251
Reply from 212.91.97.3: bytes=32 time=29ms TTL=251
Reply from 212.91.97.3: bytes=32 time=26ms TTL=251
Reply from 212.91.97.3: bytes=32 time=33ms TTL=251
Reply from 212.91.97.3: bytes=32 time=30ms TTL=251
Reply from 212.91.97.3: bytes=32 time=37ms TTL=251
Reply from 212.91.97.3: bytes=32 time=34ms TTL=251
Reply from 212.91.97.3: bytes=32 time=31ms TTL=251
Reply from 212.91.97.3: bytes=32 time=37ms TTL=251
Reply from 212.91.97.3: bytes=32 time=35ms TTL=251
Reply from 212.91.97.3: bytes=32 time=19ms TTL=251
Reply from 212.91.97.3: bytes=32 time=28ms TTL=251
Reply from 212.91.97.3: bytes=32 time=25ms TTL=251
Reply from 212.91.97.3: bytes=32 time=33ms TTL=251
Reply from 212.91.97.3: bytes=32 time=29ms TTL=251
Reply from 212.91.97.3: bytes=32 time=36ms TTL=251
Reply from 212.91.97.3: bytes=32 time=34ms TTL=251
Reply from 212.91.97.3: bytes=32 time=30ms TTL=251
Reply from 212.91.97.3: bytes=32 time=37ms TTL=251
Reply from 212.91.97.3: bytes=32 time=34ms TTL=251
Reply from 212.91.97.3: bytes=32 time=31ms TTL=251
Reply from 212.91.97.3: bytes=32 time=28ms TTL=251
Reply from 212.91.97.3: bytes=32 time=23ms TTL=251
Reply from 212.91.97.3: bytes=32 time=21ms TTL=251
Reply from 212.91.97.3: bytes=32 time=20ms TTL=251
Reply from 212.91.97.3: bytes=32 time=22ms TTL=251
Reply from 212.91.97.3: bytes=32 time=20ms TTL=251
Reply from 212.91.97.3: bytes=32 time=20ms TTL=251
Reply from 212.91.97.3: bytes=32 time=28ms TTL=251
Reply from 212.91.97.3: bytes=32 time=18ms TTL=251

Ping statistics for 212.91.97.3:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 37ms, Average = 28ms

Odgovori