a kako da pristupim njemu? i ja imam taj bullet5
Neka iskustva sa kbcnet?
Zaključano
Zakačeno
Ukucas u web pretrazivacu 192.168.1.20 i enter, i kucas ubnt u polje user i polje pasword i pristupas uredjaju
Pogledaj sta ti je default gateway (recimo sa start-run pa cmd, pa enter, pa ukucas ipconfig /all , pa enter pa pogledas gde se javlja default gateway), i tu adresu upises u svoj browser i otkucas username/password i dobijes podesavajna rutera.
Default user/password za bullet5 je ubnt/ubnt
EDIT: pretece me che :)
P.S. Ne mora da bude 192.168.1.20 :)
Default user/password za bullet5 je ubnt/ubnt
EDIT: pretece me che :)
P.S. Ne mora da bude 192.168.1.20 :)
Potpis
Kad sve ostalo zakaže, pročitaj uputstvo...
hehe nego jel radi jos kbcnet hub i kako da pristupim
^^ 'bem li ga, nisam pristupio poslednjiuh mesec i po - pre toga je radio ali je bilo slabo ljudi.
Potpis
Kad sve ostalo zakaže, pročitaj uputstvo...
hvala obojici :) nego video sam na sajtu kbc-a (gde su cene paketa) da su stavili deo D/U lokal brzinama? jel to opet mreza proradila ili to stoji samo onako bezveze...?
i default gateway pise da je 192.168.1.1 ali kad ukucam to u browser izlazi mi tplink wireless router,a ne bullet5
i default gateway pise da je 192.168.1.1 ali kad ukucam to u browser izlazi mi tplink wireless router,a ne bullet5
^^ Ah, ti imas onda 2 rutera u mrezi... to je u redu :)
A ono za lokal - verovatno misle samo na hub..
A ono za lokal - verovatno misle samo na hub..
Potpis
Kad sve ostalo zakaže, pročitaj uputstvo...
i kako onda da pristupim bullet-u? :P verovatno je glupo pitanje...
Ljudi kako da izmerim ping a da to nebude sa pingtest sajta treba mi nesto realnije
@andrijabg:
pa vidi tom tp-link-u sta je default gw, pa ces m u znati ip - verovatno je taj 192.168.1.20.
@che82 - svestan si da je ping zavisan od udaljenosti servera? Sta ti znaci "realnije"?
pa vidi tom tp-link-u sta je default gw, pa ces m u znati ip - verovatno je taj 192.168.1.20.
@che82 - svestan si da je ping zavisan od udaljenosti servera? Sta ti znaci "realnije"?
Potpis
Kad sve ostalo zakaže, pročitaj uputstvo...
Citat:
andrijabg: i kako onda da pristupim bullet-u? :P verovatno je glupo pitanje...
Wireshark digni i sniffaj malo traffic...;)
Potpis
Stane Dolanc: "Bavljenje tehnikom treba da postane svakodnevna potreba coveka.."
Pa i to sto kazes
Citat:
andrijabg: i kako onda da pristupim bullet-u? :P verovatno je glupo pitanje...
a da zaobidjes taj tvoj ruter i da ubodes utp od bullet-a u komp/switch?
Ne znam kako ce biti vremenom ali prelazak sa 2.4ghz na 5ghz je prava stvar, za sada samo pohvale
Pa i ovde u Nisu je na 2.4GHz nekada problem (retko do duse, ali lokacija gde je gusto), mogu da zamislim Beograd tek, naravno da je 5.4GHz spas :)
A evo za straleta domaci zadatak, da otkoci torrente malo i da ima ovakav ping :) Kad vec hoce da ima e-veliki:
Klik za full res pic
A evo za straleta domaci zadatak, da otkoci torrente malo i da ima ovakav ping :) Kad vec hoce da ima e-veliki:
Klik za full res pic
Sleepless_mind pomagaj, ovo se dogadja obicno uvece ili vikendom, prijavio sam odavno t.p. ali nista :(
Code:
C:\Users\krle>ping -t www.google.com
Pinging www.l.google.com [209.85.135.104] with 32 bytes of data:
Reply from 209.85.135.104: bytes=32 time=100ms TTL=49
Reply from 209.85.135.104: bytes=32 time=81ms TTL=49
Reply from 209.85.135.104: bytes=32 time=243ms TTL=49
Reply from 209.85.135.104: bytes=32 time=326ms TTL=49
Reply from 209.85.135.104: bytes=32 time=340ms TTL=49
Reply from 209.85.135.104: bytes=32 time=355ms TTL=49
Reply from 209.85.135.104: bytes=32 time=301ms TTL=49
Ping statistics for 209.85.135.104:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 355ms, Average = 249ms
C:\Users\krle>ping -t www.google.com
Pinging www.l.google.com [209.85.135.104] with 32 bytes of data:
Reply from 209.85.135.104: bytes=32 time=100ms TTL=49
Reply from 209.85.135.104: bytes=32 time=81ms TTL=49
Reply from 209.85.135.104: bytes=32 time=243ms TTL=49
Reply from 209.85.135.104: bytes=32 time=326ms TTL=49
Reply from 209.85.135.104: bytes=32 time=340ms TTL=49
Reply from 209.85.135.104: bytes=32 time=355ms TTL=49
Reply from 209.85.135.104: bytes=32 time=301ms TTL=49
Ping statistics for 209.85.135.104:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 355ms, Average = 249ms
Code:
C:\Users\krle>tracert -d www.google.com
Tracing route to www.l.google.com [209.85.135.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.3.1
2 1 ms 1 ms 1 ms 10.151.247.2
3 1 ms 2 ms 3 ms 10.151.247.1
4 1 ms 3 ms 2 ms 10.151.232.1
5 3 ms 4 ms 4 ms 10.151.173.1
6 98 ms 108 ms 185 ms 10.151.225.1
7 * * * Request timed out.
8 143 ms 187 ms 191 ms 194.106.163.201
9 144 ms 159 ms 153 ms 79.101.96.57
10 86 ms 114 ms 126 ms 149.6.182.21
11 38 ms 59 ms 44 ms 130.117.48.225
12 95 ms 103 ms 66 ms 130.117.49.146
13 171 ms 174 ms 156 ms 130.117.3.25
14 120 ms 105 ms 101 ms 130.117.49.29
15 129 ms 123 ms 89 ms 130.117.3.77
16 116 ms 127 ms 149 ms 130.117.0.73
17 108 ms 172 ms 196 ms 74.125.50.233
18 170 ms 263 ms 225 ms 209.85.240.64
19 186 ms 197 ms 160 ms 72.14.238.128
20 95 ms 74 ms 59 ms 209.85.241.189
21 146 ms 145 ms 123 ms 209.85.253.26
22 86 ms 101 ms 123 ms 209.85.135.104
Trace complete.
C:\Users\krle>tracert -d www.google.com
Tracing route to www.l.google.com [209.85.135.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.3.1
2 1 ms 1 ms 1 ms 10.151.247.2
3 1 ms 2 ms 3 ms 10.151.247.1
4 1 ms 3 ms 2 ms 10.151.232.1
5 3 ms 4 ms 4 ms 10.151.173.1
6 98 ms 108 ms 185 ms 10.151.225.1
7 * * * Request timed out.
8 143 ms 187 ms 191 ms 194.106.163.201
9 144 ms 159 ms 153 ms 79.101.96.57
10 86 ms 114 ms 126 ms 149.6.182.21
11 38 ms 59 ms 44 ms 130.117.48.225
12 95 ms 103 ms 66 ms 130.117.49.146
13 171 ms 174 ms 156 ms 130.117.3.25
14 120 ms 105 ms 101 ms 130.117.49.29
15 129 ms 123 ms 89 ms 130.117.3.77
16 116 ms 127 ms 149 ms 130.117.0.73
17 108 ms 172 ms 196 ms 74.125.50.233
18 170 ms 263 ms 225 ms 209.85.240.64
19 186 ms 197 ms 160 ms 72.14.238.128
20 95 ms 74 ms 59 ms 209.85.241.189
21 146 ms 145 ms 123 ms 209.85.253.26
22 86 ms 101 ms 123 ms 209.85.135.104
Trace complete.
Code:
C:\Users\krle>ping -t 10.151.225.1
Pinging 10.151.225.1 with 32 bytes of data:
Reply from 10.151.225.1: bytes=32 time=131ms TTL=59
Reply from 10.151.225.1: bytes=32 time=118ms TTL=59
Reply from 10.151.225.1: bytes=32 time=20ms TTL=59
Reply from 10.151.225.1: bytes=32 time=49ms TTL=59
Reply from 10.151.225.1: bytes=32 time=40ms TTL=59
Reply from 10.151.225.1: bytes=32 time=65ms TTL=59
Reply from 10.151.225.1: bytes=32 time=102ms TTL=59
Reply from 10.151.225.1: bytes=32 time=224ms TTL=59
Reply from 10.151.225.1: bytes=32 time=117ms TTL=59
Reply from 10.151.225.1: bytes=32 time=188ms TTL=59
Reply from 10.151.225.1: bytes=32 time=69ms TTL=59
Reply from 10.151.225.1: bytes=32 time=15ms TTL=59
Reply from 10.151.225.1: bytes=32 time=125ms TTL=59
Reply from 10.151.225.1: bytes=32 time=29ms TTL=59
Reply from 10.151.225.1: bytes=32 time=200ms TTL=59
Reply from 10.151.225.1: bytes=32 time=135ms TTL=59
Reply from 10.151.225.1: bytes=32 time=345ms TTL=59
Reply from 10.151.225.1: bytes=32 time=304ms TTL=59
Reply from 10.151.225.1: bytes=32 time=232ms TTL=59
Reply from 10.151.225.1: bytes=32 time=570ms TTL=59
Ping statistics for 10.151.225.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 570ms, Average = 153ms
C:\Users\krle>ping -t 10.151.225.1
Pinging 10.151.225.1 with 32 bytes of data:
Reply from 10.151.225.1: bytes=32 time=131ms TTL=59
Reply from 10.151.225.1: bytes=32 time=118ms TTL=59
Reply from 10.151.225.1: bytes=32 time=20ms TTL=59
Reply from 10.151.225.1: bytes=32 time=49ms TTL=59
Reply from 10.151.225.1: bytes=32 time=40ms TTL=59
Reply from 10.151.225.1: bytes=32 time=65ms TTL=59
Reply from 10.151.225.1: bytes=32 time=102ms TTL=59
Reply from 10.151.225.1: bytes=32 time=224ms TTL=59
Reply from 10.151.225.1: bytes=32 time=117ms TTL=59
Reply from 10.151.225.1: bytes=32 time=188ms TTL=59
Reply from 10.151.225.1: bytes=32 time=69ms TTL=59
Reply from 10.151.225.1: bytes=32 time=15ms TTL=59
Reply from 10.151.225.1: bytes=32 time=125ms TTL=59
Reply from 10.151.225.1: bytes=32 time=29ms TTL=59
Reply from 10.151.225.1: bytes=32 time=200ms TTL=59
Reply from 10.151.225.1: bytes=32 time=135ms TTL=59
Reply from 10.151.225.1: bytes=32 time=345ms TTL=59
Reply from 10.151.225.1: bytes=32 time=304ms TTL=59
Reply from 10.151.225.1: bytes=32 time=232ms TTL=59
Reply from 10.151.225.1: bytes=32 time=570ms TTL=59
Ping statistics for 10.151.225.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 570ms, Average = 153ms
Citat:
Zoran Milovanovic: Pa i ovde u Nisu je na 2.4GHz nekada problem (retko do duse, ali lokacija gde je gusto), mogu da zamislim Beograd tek, naravno da je 5.4GHz spas 
A evo za straleta domaci zadatak, da otkoci torrente malo i da ima ovakav ping Kad vec hoce da ima e-veliki:
Klik za full res pic
A evo za straleta domaci zadatak, da otkoci torrente malo i da ima ovakav ping
Kad vec hoce da ima e-veliki:Klik za full res pic
Zoco ne zafrkavaj
izmenjeno 1 put, poslednji put Zoran Milovanovic 24.01.2010. u 18:41
Izmene poruke
- Zoran Milovanovic24.01.2010. u 18:41zapis iz teksta poruke
Ne razumem na sta mislis? Ukoliko ne verujes, mogu da ti serujem screen pa da gledas live rezultate. ;)
Screen je napravljen na laptopu, ali posto sam na kucnom wifiju, ping do gatewaya (zbog losih drajvera na gateway-u mi je 1-5ms u praznom hodu, a na opterecenju oko 300kB zabada i na 50ms, zato sam se sshaovao na gateway i uradio trace i ping. Znam da ne verujes, tvoje pravo. Ja nemam nameru da te ubedjujem ili lazem.
Sta mislis kako pikam cs, skidam torrente, na ostalim racunarima se surfuje? (ok, ima limita po grupama - dinamickog) Ali, dok god link nije zauzet vise od 90-95% meni sve radi savreseno (ok, malo se poveca, ali sitno). To je ono zasto ne bih presao ni na jedan adsl. Ovde 4 sobe dele net, i svima u svakom trentutku radi savrseno. Bojim se da bi smo na adslu imali povecih problema.
Evo koliko me deli od telekomove optike ;) Kada je link prazan, svega 10kB down i 6kB up (razgovor na skype i sitnice)
opsss, sada sam proverio link nije prazan, jedan racunar seeduje torrente na 30kB, ali kazem ti, to ne utice na vezu :)
Screen je napravljen na laptopu, ali posto sam na kucnom wifiju, ping do gatewaya (zbog losih drajvera na gateway-u mi je 1-5ms u praznom hodu, a na opterecenju oko 300kB zabada i na 50ms, zato sam se sshaovao na gateway i uradio trace i ping. Znam da ne verujes, tvoje pravo. Ja nemam nameru da te ubedjujem ili lazem.
Sta mislis kako pikam cs, skidam torrente, na ostalim racunarima se surfuje? (ok, ima limita po grupama - dinamickog) Ali, dok god link nije zauzet vise od 90-95% meni sve radi savreseno (ok, malo se poveca, ali sitno). To je ono zasto ne bih presao ni na jedan adsl. Ovde 4 sobe dele net, i svima u svakom trentutku radi savrseno. Bojim se da bi smo na adslu imali povecih problema.
Evo koliko me deli od telekomove optike ;) Kada je link prazan, svega 10kB down i 6kB up (razgovor na skype i sitnice)
opsss, sada sam proverio link nije prazan, jedan racunar seeduje torrente na 30kB, ali kazem ti, to ne utice na vezu :)
Citat:
Sleepless_mind pomagaj, ovo se dogadja obicno uvece ili vikendom, prijavio sam odavno t.p. ali nista :(
Ima li nade?
Mkrle koji net koristis 5ghz ili 2.4ghz