[ Iggy-ar @ 03.01.2009. 22:58 ] @
[ Iggy-ar @ 03.01.2009. 22:58 ] @
[ Sylvester @ 04.01.2009. 00:17 ] @
speedtest definitivno ne prikazuje tacan ping :)
probaj rucno da pingujes www.verat.net (kod njih se hostuje taj test) i neke druge lokacije [ darth zool @ 04.01.2009. 02:48 ] @
meni je bio takav ping kad sam merio iz opere.
dosta bolji ping je bio iz ff, a najbolji kada sam merio iz ie. [ optix @ 04.01.2009. 02:49 ] @
Toliko o kvalitetu Speedtest.net-a
![]() [ Iggy-ar @ 05.01.2009. 01:26 ] @
Uf , i kod tebe je "isto dobar" !!
Da ,merio sam iz Opere ,probacu i druge ,FF i IE ,samo da mi neko objasni kako da rucno pingujem ??? Ima li ili nema veze ping sa "gusenjem" veze ? POZ. [ anon115774 @ 05.01.2009. 12:49 ] @
Citat: Iggy-ar: samo da mi neko objasni kako da rucno pingujem ??? Ne znas "rucno" da pingujes a hoces da 'opravljas isti :) Postavlja se onda pitanje, da li ti znas sta je ping? Da li znas sta sve utice na vrednost pinga? Da li zbog ovako "loseg" pinga imas nekih primetnih problema? Ljudi, opustite se... [ fdafsd @ 05.01.2009. 13:49 ] @
Ma čovek "utvrdio" da tu nešto treba da se popravlja, ali nije baš siguran zašto treba da se popravlja...
[ lewlz @ 05.01.2009. 14:13 ] @
Da se ubacim : D
Telekom asdl 2mbit @ speedup. Od pocetka novembra (prvo podizanje brzine) ping mnogo varira, od ~20ms ujutru do 200ms preko dana sa povremenim stabilizovanjem na par sati. Download takodje varira u tom periodu od 140-160 . Od novog dizanja brzina pre 2 nedelje ping je konstantno ~200+ms, download preko dana varira od 30kb/s do 70kb/s. Kada radi normalno ping do gatewaya je 15ms dl je oko 240kb/s. ![]() Code: Pinging 93.86.4.1 with 32 bytes of data: Reply from 93.86.4.1: bytes=32 time=180ms TTL=254 Reply from 93.86.4.1: bytes=32 time=205ms TTL=254 Reply from 93.86.4.1: bytes=32 time=208ms TTL=254 Reply from 93.86.4.1: bytes=32 time=221ms TTL=254 Reply from 93.86.4.1: bytes=32 time=214ms TTL=254 Reply from 93.86.4.1: bytes=32 time=188ms TTL=254 Reply from 93.86.4.1: bytes=32 time=228ms TTL=254 Reply from 93.86.4.1: bytes=32 time=165ms TTL=254 Reply from 93.86.4.1: bytes=32 time=217ms TTL=254 Reply from 93.86.4.1: bytes=32 time=222ms TTL=254 Ping statistics for 93.86.4.1: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 165ms, Maximum = 228ms, Average = 204ms ![]() U call centru kazhu da je to tako normalno na adslu i da ne mogu nishta da urade : D ... Any help? [ fdafsd @ 05.01.2009. 14:45 ] @
Nisi mor'o da registruješ novi nalog samo da bi to postavio...
[ anon115774 @ 05.01.2009. 17:08 ] @
Vala bas :)
A zbog cega ti sa Telekoma pingujes Verat? Sta dobijas time odnosno sta ti govori taj veliki lag? Meni govori da mozda Telekom ima neki problem. A govori mi i da mozda Verat ima neki problem. A govori mi i da neka tacka izmedju Telekoma i Verata ima problem. A govori mi da je moguca neka od kombinacija prethodne tri recenice. Shvatas poentu? :) To sto ti imas lag sa Telekoma ka Veratu je isto kao da imas lag ka nekoj tacki u Australiji. I jedna i druga situacija ti govore i mnogo i malo odnosno nista. Jedino sto ima svrhe je da meris ping do prvog rutera koji je ispred tebe. Evo npr: Code: [test1@presretac] > ping 93.86.178.1 93.86.178.1 64 byte ping: ttl=255 time=18 ms 93.86.178.1 64 byte ping: ttl=255 time=18 ms 93.86.178.1 64 byte ping: ttl=255 time=18 ms 93.86.178.1 64 byte ping: ttl=255 time=18 ms 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 18/18.0/18 ms Ovako izgleda ping sa rutera koji je nakacen na Telekomov modem do prvog rutera u telekomu odnosno default gateway-a. Veza je 2Mbit/s a iskoriscenost linka prilikom ovog pinga je oko 1-2%. A ovako izgleda ping sa istog tog rutera do Verata koji ti pingujes uporno :) Code: [test1@presretac] > ping 93.86.4.1 93.86.4.1 64 byte ping: ttl=246 time=19 ms 93.86.4.1 64 byte ping: ttl=246 time=19 ms 93.86.4.1 64 byte ping: ttl=246 time=19 ms 93.86.4.1 64 byte ping: ttl=246 time=19 ms 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 19/19.0/19 ms Kao sto vidis razlika je samo u 1ms iako razlika u hopovima i nije bas tako zanemarljiva: Code: [test1@presretac] > tool traceroute 93.86.4.1 ADDRESS STATUS 1 93.86.178.1 15ms 16ms 16ms 2 212.200.15.149 16ms 16ms 18ms 3 212.200.17.46 17ms 18ms 18ms mpls-label=619 4 212.200.17.7 18ms 18ms 20ms mpls-label=317 5 212.200.232.93 20ms 18ms 18ms mpls-label=429840 6 212.200.232.42 18ms 18ms 18ms mpls-label=117152 7 212.200.233.254 20ms 20ms 20ms mpls-label=672944 8 212.200.232.146 16ms 18ms 20ms mpls-label=23 9 212.200.17.217 18ms 17ms 18ms 10 93.86.4.1 18ms 15ms 16ms A evo kako izgleda ping do tvog Verata kada je link iskoriscen 100% (bez traffic shaping-a): Code: [test1@presretac] > ping 93.86.4.1 93.86.4.1 64 byte ping: ttl=246 time=355 ms 93.86.4.1 64 byte ping: ttl=246 time=313 ms 93.86.4.1 64 byte ping: ttl=246 time=287 ms 93.86.4.1 64 byte ping: ttl=246 time=187 ms 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 187/285.5/355 ms Tako da.... man'te se vi te rabote, kad vam ja kazem :) [ Danilo Cvjeticanin @ 05.01.2009. 17:33 ] @
A sta kazete na ovo???
Code: C:\Users\Danilo Cvjeticanin>ping www.google.com Pinging www.l.google.com [216.239.59.104] with 32 bytes of data: Request timed out. Reply from 216.239.59.104: bytes=32 time=91ms TTL=239 Request timed out. Reply from 216.239.59.104: bytes=32 time=104ms TTL=239 Ping statistics for 216.239.59.104: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 91ms, Maximum = 104ms, Average = 97ms Code: C:\Users\Danilo Cvjeticanin>ping www.verat.net Pinging home.verat.net [85.222.160.152] with 32 bytes of data: Reply from 85.222.160.152: bytes=32 time=27ms TTL=53 Reply from 85.222.160.152: bytes=32 time=24ms TTL=53 Request timed out. Reply from 85.222.160.152: bytes=32 time=28ms TTL=53 Ping statistics for 85.222.160.152: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 24ms, Maximum = 28ms, Average = 26ms Code: C:\Users\Danilo Cvjeticanin>ping www.telekom.rs Pinging www.telekom.rs [212.200.252.2] with 32 bytes of data: Reply from 212.200.252.2: bytes=32 time=27ms TTL=115 Reply from 212.200.252.2: bytes=32 time=67ms TTL=115 Reply from 212.200.252.2: bytes=32 time=54ms TTL=115 Request timed out. Ping statistics for 212.200.252.2: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 67ms, Average = 49ms Ocigledno je da se paketi gube. E sad u cemu je problem ne znam, ne mogu da dobijem tehnicku podrsku, ja bih trebao imati izmedju 2 i 3mbit-a konekciju. Sa ovim rezultatima je ping extra, ali se paketi gube, pokusavam i dalje da dobijem tehnicku podrsku pa cu javim rezultate. E da, IPTV radi extra. [ lewlz @ 05.01.2009. 17:46 ] @
@ informer, 93.86.4.1 je moj default gateway, ne verat. znaci pingujem telekom.
[ anon115774 @ 05.01.2009. 18:07 ] @
Ok, priznajem, moja greska. Nisam obratio paznju da taj gate pripada Telekomu.
U svakom slucaju jel imate vi momci neku ppp statistiku na ruterima (ili sta vec koristite)? Da li se javljaju neke greske pri transportu ili slicno? [ anon115774 @ 05.01.2009. 18:17 ] @
Danilo, probaj ping -w 60000 www.google.com pa vidi da li ce u tom roku da vrati odgovor.
[ Iggy-ar @ 05.01.2009. 21:06 ] @
@fdafsd & Informer : Ako ste dobro citali moj post ,nisam "krenuo da popravljam" nego sam pitao KAKO se popravlja ! Ali nema veze ,vidim da ima ljudi koji znaju da "rucno" pinguju ,valjda forum i sluzi da se pokaze znanje ,a da li ce neko nekome pomoci ,nije bitno ....!
Uglavnom, dosta ljudi ima isti problem ,pa ako provale u cemu je caka ,popravicu i ja !! Poz. [ Danilo Cvjeticanin @ 05.01.2009. 21:22 ] @
Citat: Informer: Danilo, probaj ping -w 60000 www.google.com pa vidi da li ce u tom roku da vrati odgovor. C:\Users\Danilo Cvjeticanin>ping -w 60000 www.google.com Pinging www.l.google.com [216.239.59.104] with 32 bytes of data: Reply from 216.239.59.104: bytes=32 time=107ms TTL=238 Reply from 216.239.59.104: bytes=32 time=295ms TTL=238 Reply from 216.239.59.104: bytes=32 time=81ms TTL=238 Reply from 216.239.59.104: bytes=32 time=161ms TTL=238 Ping statistics for 216.239.59.104: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 81ms, Maximum = 295ms, Average = 161ms ma ping mi je u svakom slucaju katastrofa, do nedavno uvek je bio od 40-70ms. [ taneb @ 06.01.2009. 00:59 ] @
C:\Documents and Settings\admin>ping -w 60000 www.google.com
Pinging www.l.google.com [66.249.91.103] with 32 bytes of data: Reply from 66.249.91.103: bytes=32 time=77ms TTL=233 Reply from 66.249.91.103: bytes=32 time=81ms TTL=233 Reply from 66.249.91.103: bytes=32 time=81ms TTL=233 Reply from 66.249.91.103: bytes=32 time=81ms TTL=233 Ping statistics for 66.249.91.103: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 77ms, Maximum = 81ms, Average = 80ms Nije ovo tako lose ali koliko se secam ranije dok mi je paket bio 768k(tad najjaci) ping ka google mi je bio oko 50-60 ali ovo je smejurija ![]() ![]() ![]() ![]() ma kakav speedtest.net [ optix @ 06.01.2009. 01:03 ] @
Mozda zato sto, po 1000x ponovljeno, ne treba ping-ovati Google, jer google nije uvek na istoj lokacji!?
Ee... internet dzedaji... ima jos dosta toga da se nauci. [ anon115774 @ 06.01.2009. 07:51 ] @
Da ali to sto dns ne pokazuje uvek na iste servere ne znaci da treba da se gube paketi :)
[ optix @ 06.01.2009. 08:02 ] @
Odnosilo se na razliku u rtt-u kod taneb-a.
Copyright (C) 2001-2025 by www.elitesecurity.org. All rights reserved.
|