dobar signal, ali paketi se gube

dobar signal, ali paketi se gube 19.06.2010. u 20:48 · pre 199 meseci #1

pozdrav.
imam problem, koji ne znam kako riješiti.
koristim hotspot za pristup internetu,i nekada sam bez problema potezao 12 mbita down i 6-7 up. ali stvar je pred neko vrijeme prestala radit. imam grid antenu, signal sa ap-a mi je pristojan (70% kaže ap, ali ovisno o vremenu sinkronizacija je 24-36 mbita, jedino kad je kiša padne na 1-2). ap ima super signal sa mog ap-a (gotovo uvijek je 48-54 mbita).
problem je šta je internet neupotrebljiv. paketi se strašno gube. pingam si gateway, i ponekad bude i 20% loss. ping prema gatewayu je inače 3-4ms, ali u zadnje vrijeme skače 300-700-200-2500 (2500!!). pa se opet gube...
smanjio sam beacon interval na 20ms , fragmentation treshold na minimum, ack timing je na auto jer ga ne znam podesit, ali i dalje net jedva radi. udaljen sam od ap-a oko 700 m. kad spojim na laptop antenu ništa se ne promijeni, i dalje se gube paketi.
jedino se nisam probao približit hotspotu (negdje u centru grada je), pa da vidim dali se i tamo tako ponaša ili je to zbog udaljenosti. navečer je internet neupotrebljiv, uopće ne otvara stranice, a po danu zna bit sve ok, iako i po danu zna ne radit ili slabo radit.
može li se ikako riješiti problem? probao sam danas okrenut antenu na horizontalnu polarizaciju, ali osim šta je signal pao na 60%, nema promjene.

Re: dobar signal, ali paketi se gube 21.06.2010. u 17:12 · pre 199 meseci #2

>

--0015174ff314a1013504898bbf84
Content-Type: text/html; charset=ISO-8859-1

Imao sam gotovo isti problem, resio sam ga tako sto sam na ap-u promenio
kanal, predpostavljam da i ti koristis 2,4GHz, ako imas pristup apu
probaj to ili probaj da updatujes firmware. <div class="gmail_quote"> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
esauth:402932:e4745deb51ca93b4f8ee172a8dc8e249

Re: dobar signal, ali paketi se gube 22.06.2010. u 00:05 · pre 199 meseci #3

koristim kanal koji je na hotspotu. ne mogu ga ja mijenjat.
inače, prije kojih 3 sata je net bio jedva upotrebljiv, ovo je rezultat kad sam pingao ap.
Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=1493ms TTL=255
Reply from 192.168.1.1: bytes=32 time=32ms TTL=255
Reply from 192.168.1.1: bytes=32 time=810ms TTL=255
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=646ms TTL=255
Reply from 192.168.1.1: bytes=32 time=981ms TTL=255
Reply from 192.168.1.1: bytes=32 time=632ms TTL=255
Reply from 192.168.1.1: bytes=32 time=677ms TTL=255
Reply from 192.168.1.1: bytes=32 time=890ms TTL=255
Reply from 192.168.1.1: bytes=32 time=926ms TTL=255
Reply from 192.168.1.1: bytes=32 time=801ms TTL=255
Reply from 192.168.1.1: bytes=32 time=557ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1056ms TTL=255
Reply from 192.168.1.1: bytes=32 time=694ms TTL=255
Reply from 192.168.1.1: bytes=32 time=262ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1013ms TTL=255
Reply from 192.168.1.1: bytes=32 time=897ms TTL=255
Reply from 192.168.1.1: bytes=32 time=655ms TTL=255
Reply from 192.168.1.1: bytes=32 time=957ms TTL=255
Reply from 192.168.1.1: bytes=32 time=948ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1149ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1140ms TTL=255
Reply from 192.168.1.1: bytes=32 time=738ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1130ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1003ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1399ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1401ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1087ms TTL=255
Reply from 192.168.1.1: bytes=32 time=981ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1002ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1581ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2007ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1118ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1218ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1643ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1388ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2640ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1373ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1457ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1141ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1157ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1047ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1172ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1577ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1850ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2320ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1842ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1423ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1979ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1562ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1508ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2066ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1886ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1904ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1861ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1495ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2012ms TTL=255
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1530ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1506ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1440ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1489ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2005ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1959ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1462ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1939ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2346ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1635ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1873ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1624ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1361ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2915ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1625ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1783ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2116ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2179ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2014ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1701ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1069ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1133ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1745ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1497ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1589ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1627ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1135ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1364ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1544ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1612ms TTL=255
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2172ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2295ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2062ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2592ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1826ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2026ms TTL=255
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2106ms TTL=255
Reply from 192.168.1.1: bytes=32 time=3051ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1768ms TTL=255
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2126ms TTL=255
Reply from 192.168.1.1: bytes=32 time=2192ms TTL=255
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2244ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1215ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1160ms TTL=255
Reply from 192.168.1.1: bytes=32 time=311ms TTL=255
Reply from 192.168.1.1: bytes=32 time=297ms TTL=255
Reply from 192.168.1.1: bytes=32 time=164ms TTL=255
Reply from 192.168.1.1: bytes=32 time=357ms TTL=255
Reply from 192.168.1.1: bytes=32 time=218ms TTL=255
Reply from 192.168.1.1: bytes=32 time=278ms TTL=255
Reply from 192.168.1.1: bytes=32 time=446ms TTL=255
Reply from 192.168.1.1: bytes=32 time=768ms TTL=255
Reply from 192.168.1.1: bytes=32 time=439ms TTL=255
Reply from 192.168.1.1: bytes=32 time=160ms TTL=255
...

a sad je sasvim OK.

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=6ms TTL=255
Reply from 192.168.1.1: bytes=32 time=6ms TTL=255
Reply from 192.168.1.1: bytes=32 time=11ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=5ms TTL=255
Reply from 192.168.1.1: bytes=32 time=5ms TTL=255
Reply from 192.168.1.1: bytes=32 time=5ms TTL=255
Reply from 192.168.1.1: bytes=32 time=6ms TTL=255
Reply from 192.168.1.1: bytes=32 time=6ms TTL=255
Reply from 192.168.1.1: bytes=32 time=8ms TTL=255
Reply from 192.168.1.1: bytes=32 time=6ms TTL=255
Reply from 192.168.1.1: bytes=32 time=11ms TTL=255
Reply from 192.168.1.1: bytes=32 time=10ms TTL=255
Reply from 192.168.1.1: bytes=32 time=5ms TTL=255
Reply from 192.168.1.1: bytes=32 time=5ms TTL=255
Reply from 192.168.1.1: bytes=32 time=10ms TTL=255
Reply from 192.168.1.1: bytes=32 time=8ms TTL=255
Reply from 192.168.1.1: bytes=32 time=5ms TTL=255
Reply from 192.168.1.1: bytes=32 time=11ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1705ms TTL=255
Reply from 192.168.1.1: bytes=32 time=14ms TTL=255
Reply from 192.168.1.1: bytes=32 time=27ms TTL=255
Reply from 192.168.1.1: bytes=32 time=6ms TTL=255
Reply from 192.168.1.1: bytes=32 time=9ms TTL=255
Reply from 192.168.1.1: bytes=32 time=9ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=8ms TTL=255
Reply from 192.168.1.1: bytes=32 time=10ms TTL=255
Reply from 192.168.1.1: bytes=32 time=12ms TTL=255
Reply from 192.168.1.1: bytes=32 time=14ms TTL=255
Reply from 192.168.1.1: bytes=32 time=12ms TTL=255
Reply from 192.168.1.1: bytes=32 time=8ms TTL=255
Reply from 192.168.1.1: bytes=32 time=9ms TTL=255
Reply from 192.168.1.1: bytes=32 time=10ms TTL=255
Reply from 192.168.1.1: bytes=32 time=10ms TTL=255
Reply from 192.168.1.1: bytes=32 time=6ms TTL=255
Reply from 192.168.1.1: bytes=32 time=9ms TTL=255
Reply from 192.168.1.1: bytes=32 time=10ms TTL=255
Reply from 192.168.1.1: bytes=32 time=105ms TTL=255
Reply from 192.168.1.1: bytes=32 time=42ms TTL=255
Reply from 192.168.1.1: bytes=32 time=49ms TTL=255
Reply from 192.168.1.1: bytes=32 time=34ms TTL=255
Reply from 192.168.1.1: bytes=32 time=52ms TTL=255
Reply from 192.168.1.1: bytes=32 time=18ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=42ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=40ms TTL=255
Reply from 192.168.1.1: bytes=32 time=805ms TTL=255
Reply from 192.168.1.1: bytes=32 time=675ms TTL=255
Reply from 192.168.1.1: bytes=32 time=542ms TTL=255
Reply from 192.168.1.1: bytes=32 time=404ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=816ms TTL=255
Reply from 192.168.1.1: bytes=32 time=858ms TTL=255
Reply from 192.168.1.1: bytes=32 time=784ms TTL=255
Reply from 192.168.1.1: bytes=32 time=524ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=6ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255

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

po danu lost paketa ima brdo, 15-20%. mislio sam dali postoji način za to nekako ublažiti, AP je očito preopterećen iako mi nije jasno od čega jer po ovoj kiši nitko živ nije na netu.

vi koji se razumite puno u mreže, dali to može bit do ack timinga? da se AP ne uspijeva prilagodit mojem ap-u jer je udaljen više nego ostali klijenti na mreži? gosti su vjerojatno 50-100 metara od ap-a, a ja sam oko 700, i ack timing na hotspotu se prilagodi bližim klijentima umjesto meni koji sam udaljen?

Re: dobar signal, ali paketi se gube 22.06.2010. u 00:34 · pre 199 meseci #4

ne moze da nekada radi dobro nekada ne, ili radi kako treba ili ne radi,verovatno nije problem do tvoje opreme nego do hotspota.700 metara nije puno mislim na udaljenost posto kazes da imas ap jos ako imas neki grid....ako je ack visok ( veći ack tajming, manja prolaznost),ali ako je jako nizak onda dolazi do nestabilnosti (vraćeni paketi mogu biti dropovani) .ack timing za tvoju udaljenost bi treba da bude koliko metara 700 x 2=1400(od tebe do pristupne tacke i nazad).ali ipak zavisi i od antene koju koristis, ako koristis usmerenu antenu koja pojačava domet tajming bi trebao da se poveca.

Potpis

Long Live Rock 'n' Roll

Re: dobar signal, ali paketi se gube 22.06.2010. u 11:58 · pre 199 meseci #5

meni je ack na auto, jer ga ne znam podesit (nije kao linksysu da ukucam udaljenost, nego me pita vrijednost u mikrosekundama).
ako mi možete objasnit par stvari:
1) ako je na ap spojeno npr 40 klijenata, neki sa jako lošim signalom (laptop) na 1 mbit, tada AP radi svima na 1 mbit? i dali se u tom slučaju taj 1 mbit dijeli na svih 40 klijenata?
2) dali AP može prilagodit njegov ack timing za svakog klijenta posebno, ili se uzima neka srednja vrijednost?

@mantas - da imam grid.
i trenutno net radi fantastično, kada pingam niti jedan paket se ne gubi, i brzina je super

ali za 4-5 sati će to biti blagi disaster, sa 5 KB/s brzinom i 20% paketa koji će se gubit.

Re: dobar signal, ali paketi se gube 22.06.2010. u 12:27 · pre 199 meseci #6

Citat:

miko.s: meni je ack na auto, jer ga ne znam podesit

Neka tako i ostane. Ack zavisi i od udaljenosti, a klijenti imaju različite udaljenosti, nekad i značajno.

Citat:

miko.s: 1) ako je na ap spojeno npr 40 klijenata, neki sa jako lošim signalom (laptop) na 1 mbit, tada AP radi svima na 1 mbit? i dali se u tom slučaju taj 1 mbit dijeli na svih 40 klijenata?

Ne. Najsporiji klijent hoće gušiti mrežu, ali ne proprocionalno svakog klijenta. Ovo je najbolje zamisliti kao prsten, čiji segmenti su vremena svakog klijenta. Onaj koji je sa lošijim signalom povećava svoj deo, a ostali trpe, ali to ne znači da se i drugima srazmerno povećava njihov deo zauzetosti vremena.

Citat:

miko.s: 2) dali AP može prilagodit njegov ack timing za svakog klijenta posebno, ili se uzima neka srednja vrijednost?

Kad je na auto, svakom klijentu se odredjuje i postavlja optimalni ack. Ovo možeš i gledati ako uključiš tu kolonu.

Potpis

Two beer or not two beer...

Re: dobar signal, ali paketi se gube 22.06.2010. u 12:31 · pre 199 meseci #7

kao sto sam rekao nije do tebe najverovtnije,ap tezi da max protok dodeli svakom korisniku ako nije drugacije kofigurisan tj ako protok nije ogrenicen po korisniku i sada kada se vas vise kaci on tezi da svima pusti maximum ali to nije moguce..

a sto se tice ack ovako bi trebalo da bude, probaj pa vidi ako je bolje ti onda polako steluj dodavaj ili smanjuj vrednost

Maksimalni teoretski ACK timeout je oko 744µs (11 km) za 802.11b
372µs 5.5km
186µs 2.2km
93µs 1.1km

372µs (55 km) za 802.11g
186µs 27.5km
93µs 13.5km
45µs 6.7 km
22µs 3.3km
11µs 1.7km
5.6µs 0.8km

Potpis

Long Live Rock 'n' Roll

Re: dobar signal, ali paketi se gube 23.06.2010. u 16:06 · pre 199 meseci #8

nema promjene, zapravo kad probam manualno podesit ack onda ide još sporije. tako da odustajem, problem je do hotspota i ja to ne mogu nikako rješiti. hvala na pomoći. bilo bi super rješenje kad bi me u upravi grada pustili da stavim svoj AP i zaštitim mrežu, jer ionako imaju bijesno brzi internet tamo, ali to se neće desit. dođu mi suze na oči kad vidim da imam 5-8 mbita uplink koji su po danu neupotrebljivi zbog preopterećenog ap-a.

Forum kao aplikacija na telefonu

Srodne teme