[ Suiauthon @ 10.07.2011. 21:08 ] @
[ Suiauthon @ 10.07.2011. 21:08 ] @
[ djricky @ 11.07.2011. 10:57 ] @
desavalo se i ranije... ne moze nista da se uradi... 99% zagusen uplink od centrale...
[ Suiauthon @ 11.07.2011. 17:55 ] @
Nadam se da ce problem vremenom nestati :(. Hvala! [ Slobodan Milivojevic @ 11.07.2011. 21:22 ] @
Samo jedno pitanje, zasto je upload 256kbps ako ti je download 4096kbps? Ne bi smelo da je tako...
[ Suiauthon @ 12.07.2011. 08:32 ] @
Tako je po ugovoru. To je neki studentski popust click 4 po ceni click 1. Mozda je pre godinu dana kada sam potpisao ugovor upload za click 4 bio 256Kbps, ali se ne secam tacno. Uglavnom, svima sa ovim popustom je tako.
[ Slobodan Milivojevic @ 12.07.2011. 08:44 ] @
Pa i nije bas, evo ja imam na jednoj liniji takav paket i upload je 512kbps. [code]ADSL State: Show Time Data Path: Fast Operation Mode: G.dmt.bisplus Max. Bandwidth Down/Up(kbps): 14488 / 1304 Bandwidth Down/Up(kbps): 4095 / 507 A isto je taj studentski... Zato mi je bilo i cudno. [ calexx @ 12.07.2011. 08:55 ] @
Možda zato što mu za max upload piše 264.
[ zentriks @ 16.07.2011. 15:51 ] @
nesto kod njega nije u redu sa linijom, mislim da ne bi smelo da bude power up u minusu dok za download ok...ili toliki max download a upload samo 256...
[ Suiauthon @ 22.07.2011. 19:20 ] @
Evo, zvao sam telekom i kazu da su njihovom greskom smanjili upload. Posle povecanja uploada na 512, ping mi se popravio za oko 15ms u proseku, ali jos uvek daleko od onih vrednosti od pre. Evo i sada tracert.
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Marko>tracert www.google.com Tracing route to www.l.google.com [74.125.39.106] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 69 ms 69 ms 69 ms 79.101.176.1 3 72 ms 72 ms 72 ms 212.200.15.241 4 72 ms 83 ms 73 ms 212.200.6.161 5 74 ms 72 ms 72 ms 212.200.6.238 6 79 ms 80 ms 79 ms 79.101.106.2 7 80 ms 79 ms 80 ms 209.85.242.228 8 94 ms 116 ms 135 ms 72.14.232.102 9 94 ms 94 ms 94 ms 209.85.254.114 10 107 ms 107 ms 94 ms 209.85.249.162 11 95 ms 95 ms 95 ms 74.125.39.106 Trace complete. Zar ne bi trebalo da ovaj drugi hop bude dosta manji, recimo do 30? Evo parametara sada: ADSL State Show Time Data Path Fast Operation Mode G.dmt.bisplus Max. Bandwidth Down/Up(kbps) 23400 / 520 Bandwidth Down/Up(kbps) 4095 / 511 SNR Margin Down/Up(dB) 33.0 / 26.0 Attenuation Down/Up(dB) 17.0 / 9.6 Power Down/Up(dBm) 19.3 / 11.3 CRC Down/Up 6 / 13 FEC Down/Up 4 / 0 HEC Down/Up 5 / 0 System Up Time 23:56:09 DSL Up Time 23:55:15 PVC Select PPP Up Time 23:55:09 [ niceness @ 23.07.2011. 12:10 ] @
Da, trebalo bi biti manje od 30ms. Evo primer na ok liniji (provajder je neobee tj. sada orion telekom):
Code: $ traceroute www.google.com traceroute to www.google.com (209.85.148.99), 30 hops max, 60 byte packets 1 192.168.0.1 (192.168.0.1) 2.747 ms 3.840 ms 5.044 ms 2 ADSL-LNS-CLU.neobee.net (80.74.164.249) 10.138 ms 10.358 ms 12.643 ms 3 passat-LNS.neobee.net (80.74.160.113) 15.549 ms 17.509 ms 20.925 ms 4 santaslittlehelper.neobee.net (80.74.160.20) 23.603 ms 26.055 ms 28.838 ms 5 212.200.231.237 (212.200.231.237) 31.659 ms 33.354 ms 35.768 ms 6 212.200.17.210 (212.200.17.210) 41.641 ms 10.869 ms 11.175 ms 7 212.200.232.117 (212.200.232.117) 13.849 ms 16.013 ms 18.691 ms 8 212.200.232.41 (212.200.232.41) 21.862 ms 23.927 ms 26.338 ms 9 212.200.227.230 (212.200.227.230) 27.768 ms 212.200.227.249 (212.200.227.249) 29.934 ms 212.200.227.230 (212.200.227.230) 32.874 ms 10 79.101.96.166 (79.101.96.166) 42.210 ms 45.748 ms 151.359 ms 11 209.85.242.228 (209.85.242.228) 50.534 ms 17.394 ms 20.067 ms 12 72.14.232.102 (72.14.232.102) 32.446 ms 35.837 ms 38.253 ms 13 209.85.254.41 (209.85.254.41) 47.123 ms 209.85.254.57 (209.85.254.57) 50.981 ms 209.85.254.41 (209.85.254.41) 47.234 ms 14 fra07s07-in-f99.1e100.net (209.85.148.99) 49.058 ms 51.129 ms 51.909 ms $ $ $ ping 80.74.164.249 PING 80.74.164.249 (80.74.164.249) 56(84) bytes of data. 64 bytes from 80.74.164.249: icmp_req=1 ttl=63 time=7.47 ms 64 bytes from 80.74.164.249: icmp_req=2 ttl=63 time=7.80 ms 64 bytes from 80.74.164.249: icmp_req=3 ttl=63 time=7.62 ms 64 bytes from 80.74.164.249: icmp_req=4 ttl=63 time=7.89 ms ^C --- 80.74.164.249 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 7.478/7.701/7.898/0.172 ms [ Slobodan Milivojevic @ 23.07.2011. 12:38 ] @
Evo Telekom ADSL isto 4Mbps, do 2. hop-a:
slobodan@sun:~$ ping 178.223.144.1 -c 4 PING 178.223.144.1 (178.223.144.1) 56(84) bytes of data. 64 bytes from 178.223.144.1: icmp_req=1 ttl=253 time=7.69 ms 64 bytes from 178.223.144.1: icmp_req=2 ttl=253 time=8.26 ms 64 bytes from 178.223.144.1: icmp_req=3 ttl=253 time=8.64 ms 64 bytes from 178.223.144.1: icmp_req=4 ttl=253 time=7.62 ms --- 178.223.144.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 7.625/8.055/8.640/0.427 ms [ Suiauthon @ 23.07.2011. 15:55 ] @
Sta mislite da li ce se problem resiti prelaskom kod drugog provajdera, recimo Orion telekoma? Konkretno da li ce se time izbeci ovaj isti problematicni drugi hop?
[ niceness @ 23.07.2011. 17:03 ] @
Ne verujem, sam si rekao da i komsije imaju isti problem, a djricky je dao moguce objasnjenje.
[ Suiauthon @ 23.07.2011. 18:09 ] @
Jos samo par pitanja koja me zanimaju. Ovaj IP drugog hopa, predpostavljam da je to adresa nekog telekomovog rutera. Gde se on nalazi, u centrali ili negde posle centrale? Da li ovaj problem moze biti resen samo kada bi telekom prosirio up link na ovoj centrali?
[ Slobodan Milivojevic @ 23.07.2011. 20:01 ] @
To ti je IP adresa od BRAS-a (Broadband Remote Access Server). Oni se nalaze u nekoliko gradova po Srbiji (ne znam tacno gde) ali evo ja iz Pirota vidim brasnis i brasklv - pretpostavljam Nis i Kraljevo. Sto znaci da se ti serveri ne nalaze u centrali nego dalje u mrezi Telekoma.
Copyright (C) 2001-2025 by www.elitesecurity.org. All rights reserved.
|