Šta je novo?

informacije o Wireless BEOGRIDu!!!

evo

trenutno pokriveni krajevi grada:
novi beograd full
zemun
b.jerkovic
autokomanda
dorcol
kumodraz
radi se:
b.brdo
vidikovac
vozdovac
banjica
batajnica
 
U ovom threadu NEMA OGLASAVANJA.
Samo razmenite tehnicke informacije.
Za oglase: mali oglasi i hot hardware, ali samo u skladu sa pravilima tih soba.
 
lepo... pripejd za wireless... samo da li se rachuna obostrani protok?!?

samo ne znam kome se to isplati...
 
ne sabira se dl i ul,vec sta prvo nabijes do kupljene kolicine,znaci prakticno mozes da napravis 1.99gb protoka u oba smera(odnosi se naravno na paket od 1gb)
nije jeftino,ali cu radije da platim i da imam zverinu od net-a,nego da se cimam sa modemom(nikad nisam bio ispod 2500din za tel. racun+flat 30dana,da ne pricam o tome da sam mogao jedino da surfujem sa tim-a i nije bilo bas komotno ni za tu svrhu)
ko ima novca treba sebi ovo da priusti ukoliko nema neku drugu alternativu...
 
ja u cenovniku ne vide flat...
 
ima i flata ali

Nije webmaster stavio cene na sajt, stavice...
 
Beogrid je napisao(la):
Nije webmaster stavio cene na sajt, stavice...

Dok ne stavi,mogao bi ih objavis ovde,ima dosta zainteresovanih
 
30€ za 256kbit flat plus obaveznih 5€ za odrzavanje mreze,512k je valjda 55€....nije malo
 
dobro....cene necu da komentarisem, sto je nekom malo, drugome je mnogo....ali ja sam kod njih na mrezi i mogu da kazem da sve radi savrseno....bas kako su rekli.....megabit je stvarno megabit, kao i sve ostale brzine....

e sad....nekome odgovara extra brzo sa ogranicenjem, nekome malo sporije bez itd.....lepo je sto moze da se bira....po meni ne bi valjalo ni da ima samo flat i da nikad ne osetis surf na megabit-u :)
 
Ivan® je napisao(la):
dobro....cene necu da komentarisem, sto je nekom malo, drugome je mnogo....ali ja sam kod njih na mrezi i mogu da kazem da sve radi savrseno....bas kako su rekli.....megabit je stvarno megabit, kao i sve ostale brzine....

e sad....nekome odgovara extra brzo sa ogranicenjem, nekome malo sporije bez itd.....lepo je sto moze da se bira....po meni ne bi valjalo ni da ima samo flat i da nikad ne osetis surf na megabit-u :)

Definitvno je odlicno sto imaju i flat tarifu i sa ogranicenjem,jedino sto mislim da bi ona ogranicenja trebala da budu sa barem 50% vecim vrednostima za one pare
 
evo, sad ima informacija o flatu i na zvanicnom sajtu - pogledajte cenovnik....
 
Calibra 4WD je napisao(la):
Definitvno je odlicno sto imaju i flat tarifu i sa ogranicenjem,jedino sto mislim da bi ona ogranicenja trebala da budu sa barem 50% vecim vrednostima za one pare

ipak je to megabit.... ;)
 
Sta ti znaci megabit ako si ogranicen na kolicinu prenetih podataka ???
Za surf je dovoljno i 64k...

Zar Beogrid nije trebao da ima iste cene za flat kao i ostali wifi provajderi? Mnogo su skuplji...
 
npetar je napisao(la):
Sta ti znaci megabit ako si ogranicen na kolicinu prenetih podataka ???
Za surf je dovoljno i 64k...

Zar Beogrid nije trebao da ima iste cene za flat kao i ostali wifi provajderi? Mnogo su skuplji...

ne znam koji ostali....ako mislis na verat i ono sto oni nude....
:S:

imam dosta drugova koji su kod njih i njihovih 512k je najcesce daleeeeko od realnih 512k......
 
Maksnet ima cene kao Verat a i Tehnicom i Memodata su cini mi se jeftiniji...(jedino sto Tehnicom,Memodata i Verat za raliku od Beogrida i Maksnet-a, ne nude lokalni file sharing i sl. ...doduse koliko sam shvatio Beogrid naplacuje 5e za lokal? ).

Nisi mi odgovorio sta nekome znaci 1GB po kolicini prenetih podataka(protokom mbit) kad za iste pare moze da uzme 64k flat kod Beogrida (za iste pare 128k kod Verata i Maksneta)...

Kakvi su pingovi na Beogridu? Procitao sam da je neko iz Beogrida na ES forumu napisao da oni ne dozvoljavaju kacenje karticama vec iskljucivo odredjenim bridzevima (tj. fabrickim AP uredjajima) i odredjenim antenama...znaci pingovi bar mora da su dobri? Aj pinguj npr. svoj AP i google da vidimo kakvi su.

EDIT: btw ja sam na Maksnetu
 
Poslednja izmena:
pingovi su odlicni....

a sto se tice odnosa 1gb - 1 mbit i 64k flat....mislim da poredjenje uopste nema smisla......to su 2 totalno razlicita pristupa......

ne znam, meni je 64k posle ovoga neprihvatiljivo sporo......skoro kao modem......
 
Ajde ti lepo pinguj google, neki server za cs pa postavi ovde rezultate. 1Mbps nema smisla ako si ogranicen sa protokom.
 
evo sto ste trazili i to najgora moguca varijanta, znaci klasican hot-spot u blokovima sa pcmci karticom i laptopom na ulici u BLoku 45
iliti preciznije u kaficu CARLI
inace kacenje u beogrid nije dozvoljeno sa opremom koja je koriscena za ova pingovanja vec iskljucivo usmerene antene sa preko 19dbi pojacanja i
klijent bridzevi


C:\Documents and Settings\n>ping www.verat.net

Pinging home.verat.net [217.26.64.130] with 32 bytes of data:

Reply from 217.26.64.130: bytes=32 time=9ms TTL=56
Reply from 217.26.64.130: bytes=32 time=7ms TTL=56
Reply from 217.26.64.130: bytes=32 time=8ms TTL=56
Reply from 217.26.64.130: bytes=32 time=16ms TTL=56

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

C:\Documents and Settings\n>ping google.com

Pinging google.com [216.239.57.99] with 32 bytes of data:

Reply from 216.239.57.99: bytes=32 time=204ms TTL=232
Reply from 216.239.57.99: bytes=32 time=215ms TTL=232
Reply from 216.239.57.99: bytes=32 time=204ms TTL=232
Reply from 216.239.57.99: bytes=32 time=204ms TTL=232

Ping statistics for 216.239.57.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 204ms, Maximum = 215ms, Average = 206ms

C:\Documents and Settings\n>ping yahoo.com

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=133ms TTL=50
Reply from 216.109.112.135: bytes=32 time=133ms TTL=51
Reply from 216.109.112.135: bytes=32 time=135ms TTL=51
Reply from 216.109.112.135: bytes=32 time=132ms TTL=51

Ping statistics for 216.109.112.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 132ms, Maximum = 135ms, Average = 133ms

C:\Documents and Settings\n>ping 195.230.150.79

Pinging 195.230.150.79 with 32 bytes of data:

Reply from 195.230.150.79: bytes=32 time=52ms TTL=48
Reply from 195.230.150.79: bytes=32 time=57ms TTL=48
Reply from 195.230.150.79: bytes=32 time=54ms TTL=48
Reply from 195.230.150.79: bytes=32 time=63ms TTL=48

Ping statistics for 195.230.150.79:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 63ms, Average = 56ms

C:\Documents and Settings\n>ping 212.124.160.3

Pinging 212.124.160.3 with 32 bytes of data:

Reply from 212.124.160.3: bytes=32 time=77ms TTL=50
Reply from 212.124.160.3: bytes=32 time=72ms TTL=50
Reply from 212.124.160.3: bytes=32 time=74ms TTL=50
Reply from 212.124.160.3: bytes=32 time=63ms TTL=50

Ping statistics for 212.124.160.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 77ms, Average = 71ms



Ping statistics for 213.240.53.162:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\n>ping www.nfl.com

Pinging www.nfl.com [216.19.170.252] with 32 bytes of data:

Reply from 216.19.170.252: bytes=32 time=164ms TTL=50
Reply from 216.19.170.252: bytes=32 time=160ms TTL=50
Reply from 216.19.170.252: bytes=32 time=158ms TTL=50
Reply from 216.19.170.252: bytes=32 time=168ms TTL=50

Ping statistics for 216.19.170.252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 158ms, Maximum = 168ms, Average = 162ms

C:\Documents and Settings\n>


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\n>ping wwww.ptt.yu
Ping request could not find host wwww.ptt.yu. Please check the name and try agai
n.

C:\Documents and Settings\n>ping ptt.yu

Pinging ptt.yu [212.62.32.65] with 32 bytes of data:

Request timed out.

Ping statistics for 212.62.32.65:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C
^C
C:\Documents and Settings\n>ping www.verat.net

Pinging home.verat.net [217.26.64.130] with 32 bytes of data:

Reply from 217.26.64.130: bytes=32 time=9ms TTL=56
Reply from 217.26.64.130: bytes=32 time=7ms TTL=56
Reply from 217.26.64.130: bytes=32 time=8ms TTL=56
Reply from 217.26.64.130: bytes=32 time=16ms TTL=56

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

C:\Documents and Settings\n>ping google.com

Pinging google.com [216.239.57.99] with 32 bytes of data:

Reply from 216.239.57.99: bytes=32 time=204ms TTL=232
Reply from 216.239.57.99: bytes=32 time=215ms TTL=232
Reply from 216.239.57.99: bytes=32 time=204ms TTL=232
Reply from 216.239.57.99: bytes=32 time=204ms TTL=232

Ping statistics for 216.239.57.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 204ms, Maximum = 215ms, Average = 206ms

C:\Documents and Settings\n>ping yahoo.com

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=133ms TTL=50
Reply from 216.109.112.135: bytes=32 time=133ms TTL=51
Reply from 216.109.112.135: bytes=32 time=135ms TTL=51
Reply from 216.109.112.135: bytes=32 time=132ms TTL=51

Ping statistics for 216.109.112.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 132ms, Maximum = 135ms, Average = 133ms

C:\Documents and Settings\n>ping 195.230.150.79

Pinging 195.230.150.79 with 32 bytes of data:

Reply from 195.230.150.79: bytes=32 time=52ms TTL=48
Reply from 195.230.150.79: bytes=32 time=57ms TTL=48
Reply from 195.230.150.79: bytes=32 time=54ms TTL=48
Reply from 195.230.150.79: bytes=32 time=63ms TTL=48

Ping statistics for 195.230.150.79:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 63ms, Average = 56ms

C:\Documents and Settings\n>ping 212.124.160.3

Pinging 212.124.160.3 with 32 bytes of data:

Reply from 212.124.160.3: bytes=32 time=77ms TTL=50
Reply from 212.124.160.3: bytes=32 time=72ms TTL=50
Reply from 212.124.160.3: bytes=32 time=74ms TTL=50
Reply from 212.124.160.3: bytes=32 time=63ms TTL=50

Ping statistics for 212.124.160.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 77ms, Average = 71ms

C:\Documents and Settings\n>ping netgames.drenik.net

Pinging drenik24.drenik.net [195.252.112.24] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 195.252.112.24:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\n>ping rts.co.yu
Ping request could not find host rts.co.yu. Please check the name and try again.


C:\Documents and Settings\n>ping www.rts.co.yu

Pinging www.rts.co.yu [213.240.53.162] with 32 bytes of data:

Reply from 194.247.195.155: Destination net unreachable.
Reply from 194.247.195.155: Destination net unreachable.
Reply from 194.247.195.155: Destination net unreachable.
Request timed out.

Ping statistics for 213.240.53.162:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\n>ping www.nfl.com

Pinging www.nfl.com [216.19.170.252] with 32 bytes of data:

Reply from 216.19.170.252: bytes=32 time=164ms TTL=50
Reply from 216.19.170.252: bytes=32 time=160ms TTL=50
Reply from 216.19.170.252: bytes=32 time=158ms TTL=50
Reply from 216.19.170.252: bytes=32 time=168ms TTL=50

Ping statistics for 216.19.170.252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 158ms, Maximum = 168ms, Average = 162ms



C:\Documents and Settings\n>tracert google.com

Tracing route to google.com [216.239.57.99]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms 10.100.23.129
2 5 ms 7 ms 5 ms b11-b61.bb.beogrid.net [10.100.200.84]
3 7 ms 8 ms 7 ms 10.100.201.254
4 13 ms 6 ms 7 ms policy.beogrid.net [10.100.254.1]
5 9 ms 5 ms 5 ms login.beogrid.net [10.100.254.18]
6 7 ms 10 ms 5 ms 80.93.225.233
7 9 ms 7 ms 24 ms 62.108.111.17
8 9 ms 13 ms 11 ms 62.108.96.66
9 21 ms 20 ms 25 ms stm-de.vline.verat.net [62.108.96.22]
10 43 ms 33 ms 41 ms f-ea1.F.DE.net.DTAG.DE [62.154.17.182]
11 125 ms 47 ms 34 ms 62.156.139.130
12 54 ms 43 ms 44 ms P6-0.AUVCR2.Aubervilliers.opentransit.net [193.2
51.132.74]
13 49 ms 43 ms 44 ms P13-0.AUVCR1.Aubervilliers.opentransit.net [193.
251.243.217]
14 120 ms 119 ms 120 ms P14-0.OAKCR1.Oakhill.opentransit.net [193.251.24
3.170]
15 209 ms 205 ms 205 ms P8-0.PALCR2.Palo-alto.opentransit.net [193.251.2
43.213]
16 204 ms 205 ms 205 ms Google-EU-Customers.GW.opentransit.net [193.251.
249.18]
17 212 ms 210 ms 247 ms 216.239.48.246
18 208 ms 207 ms 209 ms 216.239.49.13
19 288 ms 208 ms 204 ms 216.239.49.168
20 213 ms 206 ms 205 ms 216.239.49.2
21 203 ms 204 ms 206 ms 216.239.57.99

Trace complete.
 
Nazad
Vrh Dno