» »

ADSL ping?

ADSL ping?

scenic ::

OK ADSL je tu, pa ta nova povezava, če pa pingam www.siol.net dobim povprečje okoli 500 - 600 ms nikoli manj in ko gledam tiste z pingom pod 50 ms se čudim od kod razlika.
Uporabljam XP-je in njihovega klienta.
Kako bi bilo z RASPPPOE_098.
Kako se ga pa sploh namesti.
Pa še nekaj, sin igra Ultima online in pravi, da mu šteka, če jaz kaj dol vlečem, koliko je tu resnice in kako, da mu šteka včasih ko sploh nisem koneektan.

Hvala

Scenic

  • premaknil: Tomi ()

Han ::

Evo, ping preko RASPPPOE:

D:\>ping www.siol.net

Pinging hestija.siol.net [193.189.160.170] with 32 bytes of data:

Reply from 193.189.160.170: bytes=32 time=20ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126

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


RASPPPOE je čisto enostavno namestiti - slediš navodilom na strani in dela iz prve, če ni kaj drugega narobe...

Tr0n ::

Uff, 500 > je definitivno prevec, se sploh ce gre za direktno povezavo do SiOLa. Poklici in jim povem. Ima da zadevo popravijo.

SLOWWWeb.net ::

okoli 29-35
__________________________________________________
WEBhosting / WEBdesign / WEBdomain / Security solutions
BREZPLAČNI marketinški nasveti za podjetja in www strani

Mikrohard ::

Ping statistics for 193.189.160.170:
Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 37ms, Average = 17ms
Trenutno uporabljam Raspppoe, toda tudi v WinXP clientu je bil povprečen ping 20ms :\

Gre^gor ::

Ce nic ne dljam 10ms povprecje, ce dljam 125kB/s 50ms povprecje.

Hux ::

ping je lahko odvisni od vec faktorjev. Ze od samega hardwera na tvoji strani. Kot kiro network karto mas kiri modem. Jaz mam naprimer 3Comov Externi in Asusov intenri ISDN modem in je razlika za 10 v pingu. Pol se pa dolzina in sama kvaliteta linije ter tudi kofiguracija Dslama ampak teoreticno bi naj bli vsi isto skofigurirani. Teorija pa praksa sta si vcasih kot dan in noc.

Torej Sentry kaki hardwere mas?

Gre^gor ::

siemensov modem, eno mrezno za 2k sit (pomoje na realtek 8029as cipu)... se kej? disketnik :)

scenic ::

Točno za mrežno, modem je drug, se je pa ta pin popravil tako da pride povprečno okoli 30 ms. Včasih pa je še vedno visok.
Ali bi zamenjava mrežne vplivala na kvaliteto?
Drugače pa vsem hvala.

Lp

Scenic

Hux ::

do kot mas ping 30? Jaz mam tudi eno z Railetek cipom eno cheap verzijo.
Realtek RTL8139 Family PCI Fast Ethernet NIC in oni crni Copper jet modem z puno luckami.

Gre^gor ::

Pomoje bi z zamenjavo hardvera pridobil mogoce 5ms? Rekel bi, da je krivda na telekomu :) Vem da je imel enkrat nekdo na ADSL 75ms pinga, pol so pa po enem mesecu koncno popravili nekaj na centrali in je bilo potem normalno...
Kako je pa kaj s pingom v tujini?

Zgodovina sprememb…

  • spremenilo: Gre^gor ()

Reso ::

Men tud mal počas vse skupi dela..

64 bytes from 193.2.1.66: icmp_seq=10 ttl=248 time=105 ms
64 bytes from 193.2.1.66: icmp_seq=11 ttl=248 time=480 ms
64 bytes from 193.2.1.66: icmp_seq=12 ttl=248 time=469 ms

--- 193.2.1.66 ping statistics ---
12 packets transmitted, 12 received, 0% loss, time 11107ms
rtt min/avg/max/mdev = 105.019/402.684/797.964/184.380 ms

Tole sm izvaju na gatewayu ko je kazaa polno obremenjeval upload. Preden sem dobil adsl mi je pa na ISDNju bil med idlanjem 60ms.

Hux ::

NEvem no Sentry ko sem sel z 3COma na Asus ISDN sem mel ping za vsaj 10 tock nizji isti kot mam zaj na ADSLu do tistega server DSL report test. Okol 120 prej z 3Comom pa 130.

Pinging 193.2.1.66 with 32 bytes of data:

Reply from 193.2.1.66: bytes=32 time=36ms TTL=248
Reply from 193.2.1.66: bytes=32 time=27ms TTL=248
Reply from 193.2.1.66: bytes=32 time=51ms TTL=248
Reply from 193.2.1.66: bytes=32 time=34ms TTL=248

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

Zgodovina sprememb…

  • spremenilo: Hux ()

Gre^gor ::

C:\>ping -n 20 193.2.1.66

Pinging 193.2.1.66 with 32 bytes of data:

Reply from 193.2.1.66: bytes=32 time=30ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250

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

wind ::

jaz imam vedno nad 20 pinga do siola. Enkrat je bil tehnik iz Telekoma pri meni pa je rekel, da je taksen ping ze na moji centrali in ne more pomagat.

Hux ::

C:\>ping -n 20 193.2.1.66

Pinging 193.2.1.66 with 32 bytes of data:

Reply from 193.2.1.66: bytes=32 time=23ms TTL=248
Reply from 193.2.1.66: bytes=32 time=20ms TTL=248
Reply from 193.2.1.66: bytes=32 time=24ms TTL=248
Reply from 193.2.1.66: bytes=32 time=22ms TTL=248
Reply from 193.2.1.66: bytes=32 time=21ms TTL=248
Reply from 193.2.1.66: bytes=32 time=19ms TTL=248
Reply from 193.2.1.66: bytes=32 time=21ms TTL=248
Reply from 193.2.1.66: bytes=32 time=19ms TTL=248
Reply from 193.2.1.66: bytes=32 time=24ms TTL=248
Reply from 193.2.1.66: bytes=32 time=21ms TTL=248
Reply from 193.2.1.66: bytes=32 time=21ms TTL=248
Reply from 193.2.1.66: bytes=32 time=20ms TTL=248
Reply from 193.2.1.66: bytes=32 time=21ms TTL=248
Reply from 193.2.1.66: bytes=32 time=24ms TTL=248
Reply from 193.2.1.66: bytes=32 time=37ms TTL=248
Reply from 193.2.1.66: bytes=32 time=21ms TTL=248
Reply from 193.2.1.66: bytes=32 time=21ms TTL=248
Reply from 193.2.1.66: bytes=32 time=23ms TTL=248
Reply from 193.2.1.66: bytes=32 time=28ms TTL=248
Reply from 193.2.1.66: bytes=32 time=22ms TTL=248

Ping statistics for 193.2.1.66:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 37ms, Average = 22ms

C:\>

Han ::

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

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

Sistem: Asus P2B, P3@1GHz, LevelOne FNC-0111TX mrežna kartica (PCI za 2k SIT), oklopljen UTP kabel, temno siv ADSL adapter (IskraTel).

Gre^gor ::

Sej ql :D :D



C:\>ping -n 30 193.2.1.66

Pinging 193.2.1.66 with 32 bytes of data:

Reply from 193.2.1.66: bytes=32 time=11ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=21ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=11ms TTL=250
Reply from 193.2.1.66: bytes=32 time=20ms TTL=250
Reply from 193.2.1.66: bytes=32 time=10ms TTL=250

Ping statistics for 193.2.1.66:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 21ms, Average = 14ms







C:\>ping -n 30 193.189.160.170

Pinging 193.189.160.170 with 32 bytes of data:

Reply from 193.189.160.170: bytes=32 time=20ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=20ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=20ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=20ms TTL=126
Reply from 193.189.160.170: bytes=32 time=20ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=11ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126
Reply from 193.189.160.170: bytes=32 time=10ms TTL=126

Ping statistics for 193.189.160.170:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 20ms, Average = 11ms

Reso ::

Sej smo kul da si kažemo pinge sam a kdo ve če se da kej zrihtat, k men se zdi da je 700 definitivno preveč.

Hux ::

Jep drzalo bo. Ping je odvisen samo in le smao od nastavitev na cetrali. Danes so prklali centralo in vklaplali 2Mbit ludkeom (meni tudi) in ping se je znizal iz 19-21 na 14-15. Hitrosti se siol ni dvigno to so samo nastavitve na cetrali.

In 700 ping je definitivno prevec. To ti morajo popravit sej to je neuporabno tak kak mas zaj. Klici se enrkat tja pa jih jebi. Sicer nevem ce si ze na kaki kritcni razdalji al kaj koli v najslabsem primeru ti bojo dali ADSL zastojn pa bo delovalo tak pac slabo. Jaz sicer nebi bil zadovolen z tem ampak sej morajo to popravit.

Zgodovina sprememb…

  • spremenilo: Hux ()

zu_dre ::

Microsoft Windows 2000 [Version 5.00.2195]
Š Copyright 1985-2000 Microsoft Corp.

C:\>ping -n 20 193.2.1.66

Pinging 193.2.1.66 with 32 bytes of data:

Reply from 193.2.1.66: bytes=32 time<10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time<10ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250
Reply from 193.2.1.66: bytes=32 time=16ms TTL=250

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


pingi so ok ampak dl pa niha

Hux ::

eh kurc to ej. Jaz sem mislo da bom zaj lahko mel donkeja vsaltanega ko spilam pa ping vseeno skace skyhigh. Prokleti program da nemorem naret 0 upload.

Firebat ::

a ubstaja kaki program za nizanje pinga>:D
a je to velik 120/240 pinga na tujih serverjih za ut2k3 original
kje bi lahko preveril ping od SIOLA

Hux ::

daj ludeki pingajte mi malo didi.siol.net prosim in sporocite rezultate. Zaj trenutno in ze dva dni ni ADSL vrden pol pare.

Jaz osebno mislim da je siol ze na kolenah z svojimi zmogljivostmi.

Pingi niso problem noja razen tega didija norega drugo pa je problem v hitrostji ker so pingi do servera niski.

Zgodovina sprememb…

  • spremenilo: Hux ()

Tomi ::

Hux2: to, kar imajo drugi, tebi ne bo prav nič pomagalo. Samo videl boš lahko, kakšno je splošno stanje.
Čisto tako ad informandum:
isti računalnik, isti ponudnik (Arnes), enkrat GigaSet 3070 (doma, pa preko mreže), drugič I-surf (v Ljubljani), pa imam doma (kar ni logike) 75 ms pinga, v Ljubljani, ko sem pa skoraj na istem omrežju (pa še samo 2 km fiziče oddaljenost od faksa in 1 km od Arnes), pa 100 ms.
(pingam zgolj v administrativne namene, tako btw)
metrodusa.blogspot.com

Zgodovina sprememb…

  • spremenil: Tomi ()

Hux ::

zvecer ze zadnje tri dni gre v pm povezava! Kaj naj naredim!!! Vceraj je blo isto zjutraj superca popolne svinjarija in do zvecera je drzalo. Testiram isti server. Zanimivo je le jaz vendo all seeing eye pozenem in ce so ostali slovenski serveri normalni torej okol 33 pinga je tudi tujina normalna cim pa vidim tam 60- 180 pa je tujina zanic. Vecji ping ma tisti server bol pocasi gre vse vkupaj. Fora pa je da tisti server prav nic nima z tujino in ce grem trackat ftp.sunet.se bom dobo niski ping a povezava je pocasna. Isto z microsoftov stranjo.

Zgodovina sprememb…

  • spremenilo: Hux ()

Tomi ::

Ne, želim ti samo povedati, da ti to, kar ti bodo povedal drugi, ne bo pretirano koristilo. Za takšne probleme je plačan Siolov helpdesk. Njim moraš zatežiti.
metrodusa.blogspot.com

Hux ::

Ja sej jim smao fora je da je to 100% preobremenitost sej druga nemore bit ce se pojavla ob istih urah.

zu_dre ::

Microsoft Windows 2000 [Version 5.00.2195]
Š Copyright 1985-2000 Microsoft Corp.

C:\>ping -n 20 didi.siol.net

Pinging didi.siol.net [193.189.161.203] with 32 bytes of data:

Reply from 193.189.161.203: bytes=32 time=16ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254
Reply from 193.189.161.203: bytes=32 time<10ms TTL=254

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

C:\>

Hux ::

thx. sej zaj sem bil na tem serveru in vprasal ce ma kdo adsl. Dva sta se javla en z 1'-16 pingom drugi z 20-25. Jaz stretji z 80-180 ter izgubami ker me je metalo v steno in stekalo.

Problem je ocitno na dslamu ne?

To ja nemore bit vec res kak za kurc deluje vse vkup. Lih pred 14 dnevi je pa bil tisti server za tujino v pizdi.

Zgodovina sprememb…

  • spremenilo: Hux ()

Gandalfar ::

Hux2: dej prosm pokaz traceroute do tega problematicnega streznika.

Hux ::

Pizda nemorem ker s eje spet normaliziralo eto grem probat download zaj.

Gandalfar ::

Hux2: dej pokaz traceroute zdej k je normalizirano stanje pa pol k bo spet slabo. Pa prosu bi te da zdej vsakic k bos mel tezave z pingi se traceroute pokazes. Bomo lazje dolocili tezavo.

Hux ::

AMis server!

C:\>tracert 212.18.32.54

Tracing route to q3arena.amis.net [212.18.32.54]
over a maximum of 30 hops:

1 18 ms 14 ms 18 ms BSN-250-14-1.dsl.siol.net [213.250.14.1]
2 46 ms 42 ms 35 ms didi.siol.net [193.189.161.203]
3 51 ms 58 ms 44 ms six.amis.net [193.2.141.40]
4 75 ms 77 ms 66 ms mb1-ser2-1.router.amis.net [212.18.35.73]
5 42 ms 44 ms 46 ms q3arena.amis.net [212.18.32.54]

Trace complete.

NEkaj se morem omenit ni cisto normalno ker cisto normalno kot je blo zjutraj je blo okol 20. Zaj ko je blizu normalno mi tudi naekrat downloadi z Microsoftowe strani 225kB/s vlecejo. Ko je blo cisto normalno zjutraj je slo 240kB/s

To pa pinganje didija.

C:\>ping -n 20 didi.siol.net

Pinging didi.siol.net [193.189.161.203] with 32 bytes of data:

Reply from 193.189.161.203: bytes=32 time=55ms TTL=252
Reply from 193.189.161.203: bytes=32 time=57ms TTL=252
Reply from 193.189.161.203: bytes=32 time=56ms TTL=252
Reply from 193.189.161.203: bytes=32 time=50ms TTL=252
Reply from 193.189.161.203: bytes=32 time=45ms TTL=252
Reply from 193.189.161.203: bytes=32 time=52ms TTL=252
Reply from 193.189.161.203: bytes=32 time=54ms TTL=252
Reply from 193.189.161.203: bytes=32 time=53ms TTL=252
Reply from 193.189.161.203: bytes=32 time=50ms TTL=252
Reply from 193.189.161.203: bytes=32 time=46ms TTL=252
Reply from 193.189.161.203: bytes=32 time=65ms TTL=252
Request timed out.
Reply from 193.189.161.203: bytes=32 time=72ms TTL=252
Reply from 193.189.161.203: bytes=32 time=78ms TTL=252
Reply from 193.189.161.203: bytes=32 time=23ms TTL=252
Reply from 193.189.161.203: bytes=32 time=82ms TTL=252
Request timed out.
Reply from 193.189.161.203: bytes=32 time=46ms TTL=252
Reply from 193.189.161.203: bytes=32 time=55ms TTL=252
Reply from 193.189.161.203: bytes=32 time=56ms TTL=252

Ping statistics for 193.189.161.203:
Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 82ms, Average = 55ms

Eh sranje lih ko sem zacel pingat se je spet poslabsal ping.
Sem lih zaj tudi opazo da KKS server gre preko enega drugega ki je normalni ampak se zasteka pri KKSu samem. tak.

C:\>tracert 213.161.22.140

Tracing route to gamebox.kks.net [213.161.22.140]
over a maximum of 30 hops:

1 16 ms 17 ms 16 ms BSN-250-14-1.dsl.siol.net [213.250.14.1]
2 14 ms 14 ms 19 ms karibda.siol.net [193.189.161.13]
3 14 ms 14 ms 14 ms pollux.siol.net [213.250.19.228]
4 17 ms 21 ms 17 ms 212.152.180.245
5 23 ms 21 ms 21 ms 62.218.48.78
6 86 ms 56 ms 52 ms hyper.border.kks.net [213.161.1.242]
7 67 ms 72 ms 68 ms wildfire.kks.net [213.161.1.241]
8 60 ms 64 ms 62 ms forum.GE.kks.net [213.161.1.42]
9 63 ms 56 ms 58 ms gamebox.kks.net [213.161.22.140]

Trace complete.

Kaj je predvsem smesno ko ping raste padajo hitrosti z mocrosoftove strani ter ostalih serverov. Le jolt.co.uk drzi neko linijo neglede na ping z nekaj cez 220kB/s. Takrat ko pa mam didija na 150 je pa grozno leti z 33kBs

Zgodovina sprememb…

  • spremenilo: Hux ()

Firebat ::

Kako te strani pngas???
me ful zanima kok mam jest

McHusch ::

v command prompt (DOS okno) vpises naslednje: ping -n [poljubna št.] [naslov], npr:
ping -n 15 www.slo-tech.com

Zgodovina sprememb…

  • spremenil: McHusch ()

cyber ::

Poskusi z programom npr: dobiš ga pa na tej strani Visual route
Visual Route

Firebat ::

sm pingu sam

C:\>ping -n 20 didi.siol.net

Pinging didi.siol.net [193.189.161.203] with 32 bytes of d

Reply from 193.189.161.203: bytes=32 time=27ms TTL=254
Reply from 193.189.161.203: bytes=32 time=22ms TTL=254
Reply from 193.189.161.203: bytes=32 time=18ms TTL=254
Reply from 193.189.161.203: bytes=32 time=25ms TTL=254
Reply from 193.189.161.203: bytes=32 time=19ms TTL=254
Reply from 193.189.161.203: bytes=32 time=21ms TTL=254
Reply from 193.189.161.203: bytes=32 time=22ms TTL=254
Reply from 193.189.161.203: bytes=32 time=21ms TTL=254
Reply from 193.189.161.203: bytes=32 time=35ms TTL=254
Reply from 193.189.161.203: bytes=32 time=21ms TTL=254
Reply from 193.189.161.203: bytes=32 time=21ms TTL=254
Reply from 193.189.161.203: bytes=32 time=21ms TTL=254
Reply from 193.189.161.203: bytes=32 time=20ms TTL=254
Reply from 193.189.161.203: bytes=32 time=23ms TTL=254
Reply from 193.189.161.203: bytes=32 time=21ms TTL=254
Reply from 193.189.161.203: bytes=32 time=274ms TTL=254 :(
Reply from 193.189.161.203: bytes=32 time=21ms TTL=254
Reply from 193.189.161.203: bytes=32 time=26ms TTL=254
Reply from 193.189.161.203: bytes=32 time=32ms TTL=254
Reply from 193.189.161.203: bytes=32 time=43ms TTL=254

Ping statistics for 193.189.161.203:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 274ms, Average = 36ms

:( Zakaj je ping tle tako visok je mogoce ker neki dljam Edonkey)to je pr vsakem serverju

Hux ::

eto Gandalfar. Testiranje didija zjutraj ko je vse ok.

C:\>ping -n 20 didi.siol.net

Pinging didi.siol.net [193.189.161.203] with 32 bytes of data:

Reply from 193.189.161.203: bytes=32 time=17ms TTL=252
Reply from 193.189.161.203: bytes=32 time=17ms TTL=252
Reply from 193.189.161.203: bytes=32 time=17ms TTL=252
Reply from 193.189.161.203: bytes=32 time=16ms TTL=252
Reply from 193.189.161.203: bytes=32 time=17ms TTL=252
Reply from 193.189.161.203: bytes=32 time=15ms TTL=252
Reply from 193.189.161.203: bytes=32 time=17ms TTL=252
Reply from 193.189.161.203: bytes=32 time=16ms TTL=252
Reply from 193.189.161.203: bytes=32 time=18ms TTL=252
Reply from 193.189.161.203: bytes=32 time=18ms TTL=252
Reply from 193.189.161.203: bytes=32 time=15ms TTL=252
Reply from 193.189.161.203: bytes=32 time=17ms TTL=252
Reply from 193.189.161.203: bytes=32 time=16ms TTL=252
Reply from 193.189.161.203: bytes=32 time=18ms TTL=252
Reply from 193.189.161.203: bytes=32 time=16ms TTL=252
Reply from 193.189.161.203: bytes=32 time=16ms TTL=252
Reply from 193.189.161.203: bytes=32 time=18ms TTL=252
Reply from 193.189.161.203: bytes=32 time=19ms TTL=252
Reply from 193.189.161.203: bytes=32 time=15ms TTL=252
Reply from 193.189.161.203: bytes=32 time=15ms TTL=252

Ping statistics for 193.189.161.203:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 19ms, Average = 16ms


Ter track do amisa.


C:\>tracert 212.18.32.54

Tracing route to q3arena.amis.net [212.18.32.54]
over a maximum of 30 hops:

1 14 ms 14 ms 14 ms BSN-250-14-1.dsl.siol.net [213.250.14.1]
2 16 ms 16 ms 16 ms didi.siol.net [193.189.161.203]
3 16 ms 15 ms 17 ms six.amis.net [193.2.141.40]
4 21 ms 21 ms 22 ms mb1-ser2-1.router.amis.net [212.18.35.73]
5 20 ms 22 ms 21 ms q3arena.amis.net [212.18.32.54]

Trace complete.

Racunam da tak okol 12tih se bo spet vse poslabsalo prvo na zelo slabo pol pa na sprejemlivo vendar ne za slovenske servere. 80 pinga ni fajn meti na slovenskih serverih.

Hux ::

Ves kaj mi sploh negre v glavo. KKS server ki negre preko didija amapk ma v vsakem trenutku identicen ping z ostalimi serveri ki so na lagu. Cisto vedno ceprav oni osredni server cist normalno deluje. Ko se didi poslabsa zaj se je spet namrec gre tudi hyper.border.kks.net kvragu. sicilija in castor siol.net ki prestopam cez njih pa mata oba 14 pinga. Ki je tu logika? Sej gre z siola v avstrijo in ko pride nazaj iz austrije zacne ping narascat.

================================================
=== VisualRoute report on 2002.10.6 10:48:07 ===
================================================

Report for didi.siol.net [193.189.161.203]

Analysis: 'didi.siol.net' was found in 2 hops (TTL=252).

-----------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
-----------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 193.77.156.18 | hux-zfyemow2ge4 | * | | | | Posta Slovenije d.o.o. |
| 1 | | 213.250.14.1 | BSN-250-14-1.dsl.siol.net | ?(Slovenia) | | 14 | x | SiOL d.o.o. (Slovenia Online) |
| 2 | | 193.189.161.203 | didi.siol.net | ?Ljubljana, Slovenia | | 77 | -x--- | SiOL d.o.o. (Slovenia On Line) |
-----------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to didi.siol.net, average = 77ms, min = 69ms, max = 108ms -- 2002.10.6 10:48:07

Zgodovina sprememb…

  • spremenilo: Hux ()

Hux ::

Evo to pa je ko je spet nenormalno ob 12:00

C:\>ping -n 20 didi.siol.net

Pinging didi.siol.net [193.189.161.203] with 32 bytes of data:

Reply from 193.189.161.203: bytes=32 time=117ms TTL=252
Reply from 193.189.161.203: bytes=32 time=108ms TTL=252
Reply from 193.189.161.203: bytes=32 time=138ms TTL=252
Reply from 193.189.161.203: bytes=32 time=109ms TTL=252
Reply from 193.189.161.203: bytes=32 time=102ms TTL=252
Reply from 193.189.161.203: bytes=32 time=122ms TTL=252
Reply from 193.189.161.203: bytes=32 time=134ms TTL=252
Reply from 193.189.161.203: bytes=32 time=138ms TTL=252
Reply from 193.189.161.203: bytes=32 time=29ms TTL=252
Reply from 193.189.161.203: bytes=32 time=81ms TTL=252
Reply from 193.189.161.203: bytes=32 time=133ms TTL=252
Reply from 193.189.161.203: bytes=32 time=118ms TTL=252
Reply from 193.189.161.203: bytes=32 time=127ms TTL=252
Reply from 193.189.161.203: bytes=32 time=124ms TTL=252
Reply from 193.189.161.203: bytes=32 time=131ms TTL=252
Reply from 193.189.161.203: bytes=32 time=129ms TTL=252
Reply from 193.189.161.203: bytes=32 time=137ms TTL=252
Reply from 193.189.161.203: bytes=32 time=134ms TTL=252
Reply from 193.189.161.203: bytes=32 time=119ms TTL=252
Reply from 193.189.161.203: bytes=32 time=139ms TTL=252

Ping statistics for 193.189.161.203:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 139ms, Average = 118ms

boha ::

obremenjenost dslama?
to se dogaja vsem...

Hux ::

oni na siol forumah pravi da se to psloh ne dogaja in ce se bi kdaj ze bi nadgradili! Jau hudo bo se to vse skupaj. 2Mbit mam zgolj zato da mi vlece pocasneje kot prej na 1mbit ker takrat je delalo vendo z maximumom.

Firebat ::

C:\>ping -n 20 didi.siol.net

Pinging didi.siol.net [193.189.161.203] with 32 byt

Reply from 193.189.161.203: bytes=32 time=20ms TTL=
Reply from 193.189.161.203: bytes=32 time=19ms TTL=
Reply from 193.189.161.203: bytes=32 time=21ms TTL=
Reply from 193.189.161.203: bytes=32 time=21ms TTL=
Reply from 193.189.161.203: bytes=32 time=21ms TTL=
Reply from 193.189.161.203: bytes=32 time=20ms TTL=
Reply from 193.189.161.203: bytes=32 time=19ms TTL=
Reply from 193.189.161.203: bytes=32 time=20ms TTL=
Reply from 193.189.161.203: bytes=32 time=20ms TTL=
Reply from 193.189.161.203: bytes=32 time=19ms TTL=
Reply from 193.189.161.203: bytes=32 time=21ms TTL=
Reply from 193.189.161.203: bytes=32 time=20ms TTL=
Reply from 193.189.161.203: bytes=32 time=21ms TTL=
Reply from 193.189.161.203: bytes=32 time=20ms TTL=
Reply from 193.189.161.203: bytes=32 time=20ms TTL=
Reply from 193.189.161.203: bytes=32 time=20ms TTL=
Reply from 193.189.161.203: bytes=32 time=20ms TTL=
Reply from 193.189.161.203: bytes=32 time=21ms TTL=
Reply from 193.189.161.203: bytes=32 time=20ms TTL=
Reply from 193.189.161.203: bytes=32 time=19ms TTL=

Ping statistics for 193.189.161.203:
Packets: Sent = 20, Received = 20, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 21ms, Average = 20ms


merjeno on 16.00

zile ::

Ni vse zlato kar se sveti 8-)


Vredno ogleda ...

TemaSporočilaOglediZadnje sporočilo
TemaSporočilaOglediZadnje sporočilo
»

Visoki pingi Siol ADSL 1024/256 (strani: 1 2 3 )

Oddelek: Omrežja in internet
10210039 (6618) Alexius Heristalski
»

SiOL mrk (strani: 1 2 3 4 )

Oddelek: Novice / Omrežja / internet
1729142 (9142) hruske
»

Preveliki pingi (strani: 1 2 )

Oddelek: Omrežja in internet
524572 (3979) [L4M3RZ] - TinLaDeN
»

Samomor?

Oddelek: Omrežja in internet
71790 (1537) Hux
»

Pingi in ADSL

Oddelek: Omrežja in internet
292038 (1400) matter

Več podobnih tem