Samo par sugestija na pocetku. Pricali smo vec kako vreme odziva ili ti ping ne zavisi od provajdera preko koga ides. Osim ako je njegova veza ka spolja maksimalno opterecena. Zavisi najvecim delom od toga u kom rezimu ti je namesten port (linija) na DSL pristupnom uredjaju u centrali (DSLAM). Sto je opet posledica kvaliteta bakarnih parica do tebe, i modema. Tako da eventualnom promenom provajdera samo iz tog razloga, ces najverovatnije biti razocaran, jer se nece nista spektakularno desiti. Mozda jesi promenio provajdera, ali bakarne parice su iste, a i port ce ti najverovatnije ostati isto podesen. Iz ovog naravno izuzimam razlog ako je neobee-u dobrim delom dana veza maksimalno iskoriscenja, a u tom slucaju ping je jos i manji razlog za promenu. S druge strane desavalo se da ljudi izgube tehnicke mogucnosti promenom provajdera, pa i na to treba da racunas, koliko god glupo zvucalo.
Elem, izabrao si izgleda veoma nestabilan server za ping-ovanje. Ja dobijam prosecne vrednosti od 80-140 ms. Cak ni preko optike nije nista bolje. Prvi ping dole ti je sa sbb-a (coax. kabl), drugi sa optike (gde je ping inace 1-2ms ka svim serverima u Beogradu
)
Code:
c:\>ping -n 10 www.driven.de
Pinging www.driven.de [217.160.140.85] with 32 bytes of data:
Reply from 217.160.140.85: bytes=32 time=107ms TTL=49
Reply from 217.160.140.85: bytes=32 time=104ms TTL=49
Reply from 217.160.140.85: bytes=32 time=106ms TTL=49
Reply from 217.160.140.85: bytes=32 time=106ms TTL=49
Reply from 217.160.140.85: bytes=32 time=105ms TTL=49
Reply from 217.160.140.85: bytes=32 time=97ms TTL=49
Reply from 217.160.140.85: bytes=32 time=109ms TTL=49
Reply from 217.160.140.85: bytes=32 time=110ms TTL=49
Reply from 217.160.140.85: bytes=32 time=103ms TTL=49
Reply from 217.160.140.85: bytes=32 time=97ms TTL=49
Ping statistics for 217.160.140.85:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 110ms, Average = 104ms
Code:
Router#ping
Protocol [ip]:
Target IP address: www.driven.de
Repeat count [5]: 200
Datagram size [100]: 36
Timeout in seconds [2]: 1
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 200, 36-byte ICMP Echos to 217.160.140.85, timeout is 1 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (200/200), round-trip min/avg/max = 80/102/120 ms
Kao sto rekoh dobijam sve od 80-140ms, sto je prilicno nestabilno. Daj neki drugi server, i daj svoj ping ka recimo 212.200.232.13
Poz.
Update:
Par minuta nakon sto napisah ovo gore, ping se najednom popravio. Sada sa oba izvora ide oko 50-55ms.
Code:
c:\>ping www.driven.de
Pinging www.driven.de [217.160.140.85] with 32 bytes of data:
Reply from 217.160.140.85: bytes=32 time=52ms TTL=49
Reply from 217.160.140.85: bytes=32 time=52ms TTL=49
Reply from 217.160.140.85: bytes=32 time=57ms TTL=49
Reply from 217.160.140.85: bytes=32 time=53ms TTL=49
Ping statistics for 217.160.140.85:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 57ms, Average = 53ms
Promisli jos malo oko promene provajdera
[Ovu poruku je menjao optix dana 10.09.2006. u 20:26 GMT+1]
"99% of your thought process is protecting your self-conceptions,
and 98% of that is wrong."
ADSL 256/64 - ping u command prompt-u