MW - velke pakety sa stracaju ???

[Rainbow]

Ako si mam vysvetlit toto

root@server:~# ping -s 2048 -c 20 10.2.20.1
PING 10.2.20.1 (10.2.20.1): 2048 octets data
2056 octets from 10.2.20.1: icmp_seq=1 ttl=64 time=207.1 ms
2056 octets from 10.2.20.1: icmp_seq=3 ttl=64 time=130.1 ms
2056 octets from 10.2.20.1: icmp_seq=7 ttl=64 time=205.5 ms
2056 octets from 10.2.20.1: icmp_seq=8 ttl=64 time=159.2 ms
2056 octets from 10.2.20.1: icmp_seq=10 ttl=64 time=153.2 ms
2056 octets from 10.2.20.1: icmp_seq=12 ttl=64 time=190.6 ms
2056 octets from 10.2.20.1: icmp_seq=15 ttl=64 time=133.5 ms

--- 10.2.20.1 ping statistics ---
20 packets transmitted, 7 packets received, 65% packet loss
round-trip min/avg/max = 130.1/168.4/207.1 ms
root@server:~# ping -s 1024 -c 20 10.2.20.1
PING 10.2.20.1 (10.2.20.1): 1024 octets data
1032 octets from 10.2.20.1: icmp_seq=1 ttl=64 time=92.5 ms
1032 octets from 10.2.20.1: icmp_seq=4 ttl=64 time=62.4 ms
1032 octets from 10.2.20.1: icmp_seq=5 ttl=64 time=55.6 ms
1032 octets from 10.2.20.1: icmp_seq=6 ttl=64 time=50.3 ms
1032 octets from 10.2.20.1: icmp_seq=8 ttl=64 time=69.1 ms
1032 octets from 10.2.20.1: icmp_seq=9 ttl=64 time=80.9 ms
1032 octets from 10.2.20.1: icmp_seq=10 ttl=64 time=55.1 ms
1032 octets from 10.2.20.1: icmp_seq=11 ttl=64 time=171.7 ms
1032 octets from 10.2.20.1: icmp_seq=14 ttl=64 time=66.0 ms
1032 octets from 10.2.20.1: icmp_seq=15 ttl=64 time=73.0 ms
1032 octets from 10.2.20.1: icmp_seq=16 ttl=64 time=69.6 ms

--- 10.2.20.1 ping statistics ---
20 packets transmitted, 11 packets received, 45% packet loss
round-trip min/avg/max = 50.3/76.9/171.7 ms
root@server:~# ping -s 512 -c 20 10.2.20.1 
PING 10.2.20.1 (10.2.20.1): 512 octets data
520 octets from 10.2.20.1: icmp_seq=2 ttl=64 time=49.5 ms
520 octets from 10.2.20.1: icmp_seq=4 ttl=64 time=32.6 ms
520 octets from 10.2.20.1: icmp_seq=6 ttl=64 time=56.6 ms
520 octets from 10.2.20.1: icmp_seq=7 ttl=64 time=26.5 ms
520 octets from 10.2.20.1: icmp_seq=8 ttl=64 time=62.8 ms
520 octets from 10.2.20.1: icmp_seq=9 ttl=64 time=20.6 ms
520 octets from 10.2.20.1: icmp_seq=10 ttl=64 time=37.4 ms
520 octets from 10.2.20.1: icmp_seq=11 ttl=64 time=27.4 ms
520 octets from 10.2.20.1: icmp_seq=12 ttl=64 time=22.8 ms
520 octets from 10.2.20.1: icmp_seq=14 ttl=64 time=22.4 ms
520 octets from 10.2.20.1: icmp_seq=16 ttl=64 time=49.3 ms
520 octets from 10.2.20.1: icmp_seq=18 ttl=64 time=54.2 ms

--- 10.2.20.1 ping statistics ---
20 packets transmitted, 12 packets received, 40% packet loss
round-trip min/avg/max = 20.6/38.5/62.8 ms
root@server:~# ping -s 256 -c 20 10.2.20.1
PING 10.2.20.1 (10.2.20.1): 256 octets data
264 octets from 10.2.20.1: icmp_seq=0 ttl=64 time=66.8 ms
264 octets from 10.2.20.1: icmp_seq=1 ttl=64 time=27.2 ms
264 octets from 10.2.20.1: icmp_seq=2 ttl=64 time=32.5 ms
264 octets from 10.2.20.1: icmp_seq=4 ttl=64 time=18.0 ms
264 octets from 10.2.20.1: icmp_seq=5 ttl=64 time=94.2 ms
264 octets from 10.2.20.1: icmp_seq=7 ttl=64 time=116.5 ms
264 octets from 10.2.20.1: icmp_seq=9 ttl=64 time=59.5 ms
264 octets from 10.2.20.1: icmp_seq=10 ttl=64 time=18.8 ms
264 octets from 10.2.20.1: icmp_seq=11 ttl=64 time=20.1 ms
264 octets from 10.2.20.1: icmp_seq=12 ttl=64 time=28.2 ms
264 octets from 10.2.20.1: icmp_seq=13 ttl=64 time=20.2 ms
264 octets from 10.2.20.1: icmp_seq=14 ttl=64 time=20.6 ms
264 octets from 10.2.20.1: icmp_seq=17 ttl=64 time=25.2 ms
264 octets from 10.2.20.1: icmp_seq=18 ttl=64 time=21.2 ms
264 octets from 10.2.20.1: icmp_seq=19 ttl=64 time=42.2 ms

--- 10.2.20.1 ping statistics ---
20 packets transmitted, 15 packets received, 25% packet loss
round-trip min/avg/max = 18.0/40.7/116.5 ms
root@server:~# ping -s 128 -c 20 10.2.20.1
PING 10.2.20.1 (10.2.20.1): 128 octets data
136 octets from 10.2.20.1: icmp_seq=0 ttl=64 time=14.1 ms
136 octets from 10.2.20.1: icmp_seq=2 ttl=64 time=18.9 ms
136 octets from 10.2.20.1: icmp_seq=3 ttl=64 time=14.8 ms
136 octets from 10.2.20.1: icmp_seq=7 ttl=64 time=17.9 ms
136 octets from 10.2.20.1: icmp_seq=8 ttl=64 time=36.1 ms
136 octets from 10.2.20.1: icmp_seq=9 ttl=64 time=38.7 ms
136 octets from 10.2.20.1: icmp_seq=10 ttl=64 time=17.5 ms
136 octets from 10.2.20.1: icmp_seq=11 ttl=64 time=22.1 ms
136 octets from 10.2.20.1: icmp_seq=12 ttl=64 time=31.8 ms
136 octets from 10.2.20.1: icmp_seq=13 ttl=64 time=48.4 ms
136 octets from 10.2.20.1: icmp_seq=14 ttl=64 time=45.0 ms
136 octets from 10.2.20.1: icmp_seq=15 ttl=64 time=30.8 ms
136 octets from 10.2.20.1: icmp_seq=16 ttl=64 time=24.5 ms
136 octets from 10.2.20.1: icmp_seq=17 ttl=64 time=19.8 ms
136 octets from 10.2.20.1: icmp_seq=18 ttl=64 time=20.7 ms
136 octets from 10.2.20.1: icmp_seq=19 ttl=64 time=19.2 ms

--- 10.2.20.1 ping statistics ---
20 packets transmitted, 16 packets received, 20% packet loss
round-trip min/avg/max = 14.1/26.2/48.4 ms
root@server:~# ping -s 64 -c 20 10.2.20.1 
PING 10.2.20.1 (10.2.20.1): 64 octets data
72 octets from 10.2.20.1: icmp_seq=0 ttl=64 time=16.6 ms
72 octets from 10.2.20.1: icmp_seq=1 ttl=64 time=23.2 ms
72 octets from 10.2.20.1: icmp_seq=2 ttl=64 time=22.6 ms
72 octets from 10.2.20.1: icmp_seq=3 ttl=64 time=34.4 ms
72 octets from 10.2.20.1: icmp_seq=4 ttl=64 time=21.5 ms
72 octets from 10.2.20.1: icmp_seq=5 ttl=64 time=9.4 ms
72 octets from 10.2.20.1: icmp_seq=6 ttl=64 time=8.4 ms
72 octets from 10.2.20.1: icmp_seq=7 ttl=64 time=12.6 ms
72 octets from 10.2.20.1: icmp_seq=8 ttl=64 time=73.2 ms
72 octets from 10.2.20.1: icmp_seq=9 ttl=64 time=14.0 ms
72 octets from 10.2.20.1: icmp_seq=10 ttl=64 time=15.5 ms
72 octets from 10.2.20.1: icmp_seq=11 ttl=64 time=15.5 ms
72 octets from 10.2.20.1: icmp_seq=12 ttl=64 time=25.0 ms
72 octets from 10.2.20.1: icmp_seq=13 ttl=64 time=20.2 ms
72 octets from 10.2.20.1: icmp_seq=14 ttl=64 time=41.2 ms
72 octets from 10.2.20.1: icmp_seq=16 ttl=64 time=15.6 ms
72 octets from 10.2.20.1: icmp_seq=18 ttl=64 time=18.3 ms
72 octets from 10.2.20.1: icmp_seq=19 ttl=64 time=17.7 ms

--- 10.2.20.1 ping statistics ---
20 packets transmitted, 18 packets received, 10% packet loss
round-trip min/avg/max = 8.4/22.4/73.2 ms

Male pakety sa nestracaju skoro vobec - takze napriklad Unreal Tournament sa hrat da. Stracaju sa velke pakety, ale len smerom odo mna - "vdaka" tomu mam hrozne problemy s uploadom. Napriklad 200KB mail som musel posielat asi 30 krat, lebo vzdy sa to po par KB uploadnutych dat zastavi a nic to nerobi (o chvilu pride timeout).

[Jezevec]

To je hodne spatny, me se pakety nestracej vubec (sem tam nakej). Merkni jestli nemas nekde nastavenou max velikost nako blbe. Taky merkni na signal, ale muze to bejt na druhej strane a to nezmeris.

[Dade_Marfi]

co to mas za linku od koho a co je za AP tam kam se pripojujes ??

[Rainbow]

Link Quality:34/92  Signal level:-59 dBm  Noise level:-93 dBm
Link Quality:26/92  Signal level:-64 dBm  Noise level:-94 dBm
Link Quality:30/92  Signal level:-61 dBm  Noise level:-93 dBm
Link Quality:20/92  Signal level:-68 dBm  Noise level:-94 dBm

Netusim, ake APcko je na druhej strane. Vzdialenost odhadujem na 1 az 2km, antenu mam len plechovku, karta ma slaby vykon (len 13dBm) Ale niekedy to ide uplne bez problemov.

[Jezevec]

hmm, na tu dalku je plechovka malo. Co je na druhej strane ? Jestli vsesmer, tak AP ma signal uplne v haji. Mozna ti to taky nekdo rusi, testni jestli najdes jinej signal.

[Rainbow]

Roznych APciek je tu okolo plno - bez pohnutia anteny/plechovky chytam najmenej 4... Cim by sa do dalo prescanovat? Skusal som Wavemon, ale vypise mi Access Point list not available Kismet som si tiez stiahol, aj skompiloval, ale ma to milion suborov a nechce sa mi to cez SCP prenasat na router a hladat, do akych adresarov to mam vsetko nakopirovat
BTW.: Uz viem, podla coho sa ta firma vola FastWeb :

[Rainbow]

Zaujimave - teraz mi to stahuje 12KB/s, ale upload blbne stale rovnako. Aj tu na fore niekedy kliknem a nic sa nedeje, potom kliknem znovu a skoro okamzite sa to otvori... To bude asi ten packet loss Nechapem, preco mi to pred niekolkymi dnami islo uplne bez problemov Pamatam si, ze rovnako to blblo aj na zaciatku, potom prestalo a teraz to robi znovu. Asi by som si mal kupit/pozicat/urobit nejaku lepsiu antenu.

[Nigga]

Hele, ty ides cez FastWeb? Ja tiez. Ozvi sa mi prosim ta na ICQ, pokecame, ze kde si, ako si pripojeny a tak .
A co sa tyka pripojenia, tak ja s tym nemam najmensie problemy. Z 1000 poslanych paketov sa aj 1000 vrati. Ale to zrejme preto, lebo k serveru idem kablom , tzn. problem bude asi v tvojej plechovke, predsa len sa to neda uplne presne vyrobit.

[Maxik]

i 10% packetloose pri malejch paketech je strasne moc, to by se melo imho pohybovat max -+2-3% prinejhorsim Na 2km je plechovka fakt blba ta je podle me tak do 500-800m. Problem mas nejspis v tom ze ty signal z ap chytis v pohode, ale od tebe signal k AP uz doleti blbe... skus si postavit treba biqada http://www.simandl.cz/stranky/czfree...eny/anteny.htm pripadne si skus nekde pucit treba nejaky 12db profi sito a uvidis...

packetloss 65% pri 2kB paketech je drsnej

[root@Maxik-server root]# ping -s 2048 -c 20 10.100.11.1
PING 10.100.11.1 (10.100.11.1) from 10.100.11.12 : 2048(2076) bytes of data.
2056 bytes from 10.100.11.1: icmp_seq=1 ttl=64 time=9.40 ms
2056 bytes from 10.100.11.1: icmp_seq=2 ttl=64 time=22.5 ms
2056 bytes from 10.100.11.1: icmp_seq=3 ttl=64 time=12.0 ms
2056 bytes from 10.100.11.1: icmp_seq=4 ttl=64 time=16.7 ms
2056 bytes from 10.100.11.1: icmp_seq=5 ttl=64 time=12.4 ms
2056 bytes from 10.100.11.1: icmp_seq=6 ttl=64 time=12.3 ms
2056 bytes from 10.100.11.1: icmp_seq=7 ttl=64 time=27.9 ms
2056 bytes from 10.100.11.1: icmp_seq=8 ttl=64 time=31.8 ms
2056 bytes from 10.100.11.1: icmp_seq=9 ttl=64 time=23.7 ms
2056 bytes from 10.100.11.1: icmp_seq=10 ttl=64 time=28.5 ms
2056 bytes from 10.100.11.1: icmp_seq=11 ttl=64 time=22.8 ms
2056 bytes from 10.100.11.1: icmp_seq=12 ttl=64 time=12.3 ms
2056 bytes from 10.100.11.1: icmp_seq=13 ttl=64 time=9.32 ms
2056 bytes from 10.100.11.1: icmp_seq=14 ttl=64 time=8.90 ms
2056 bytes from 10.100.11.1: icmp_seq=15 ttl=64 time=8.70 ms
2056 bytes from 10.100.11.1: icmp_seq=16 ttl=64 time=10.0 ms
2056 bytes from 10.100.11.1: icmp_seq=17 ttl=64 time=23.4 ms
2056 bytes from 10.100.11.1: icmp_seq=18 ttl=64 time=11.4 ms
2056 bytes from 10.100.11.1: icmp_seq=19 ttl=64 time=12.0 ms
2056 bytes from 10.100.11.1: icmp_seq=20 ttl=64 time=12.0 ms

--- 10.100.11.1 ping statistics ---
20 packets transmitted, 20 received, 0% loss, time 19044ms
rtt min/avg/max/mdev = 8.708/16.437/31.803/7.360 ms

[root@Maxik-server root]# ping -f 10.100.11.1
PING 10.100.11.1 (10.100.11.1) from 10.100.11.12 : 56(84) bytes of data.
..
--- 10.100.11.1 ping statistics ---
1598 packets transmitted, 1596 received, 0% loss, time 4999ms
rtt min/avg/max/mdev = 2.034/3.077/23.170/1.611 ms, pipe 2, ipg/ewma 3.130/2.849 ms

[VOiD]

Nějak extra do toho nevidím, ale podle mě máš špatnou anténu na vysílání. Download jede v pohodě protože pouze příjmáš a odeslané ACK od tebe nejsou velké pakety takže je to OK. Při vysílání od tebe má druhá strana špatný příjem -> neodesílá ACK signál, proto ten packet loss a pomalá rychlost. Zkusil bych lepší anténu, ta plechovka se mi moc nezdá.

[Rainbow]

Ty vole, teraz som dal plechovku prec a nechal som tam trcat iba kabel, do konektora som zasunul kusok a ono to ide asi rovnako zle ako predtym , link quality mam az 32/92

[Glottis]

LOL tak to tu plechovku mas dost blbe postavenou ne? nemas ji treb ablbe natocenou na jinej smer polarizace nebo blbe udelanej zaric? dobre je to postribrit a vylestit.

[Rainbow]

Tu plechovku som nerobil ja, niekto ju uz rok pouzival a vraj mu to chodilo Teraz som ju dal naspat a ide to este horsie ako bez nej Na taku pracu sa mozem vy***t Zajtra po skuske idem kupit antenu

[Maxik]

udlej si nakou plechovku sam, je to jednoduchy a kdyz to dobre udelas tak je to ok, ale neni to na moc velky vzdalenosti...

[Glottis]

sem cetl ze jeden typek ji ma na asi 6Km. jde o presnost, polarizaci a fakt to chce dobre udelat ten ctvrvlnej unipolek dovnitr. pekne vylestit skinefekt je bestie a pak dobre natocit

[Rainbow]

Tato vyzera byt spravena pekne, akurat neviem ci rozmery presne sedia. Najhorsie je na tom konektor - plechovka ma rovnaky konektor ako kabel takze som tam urobil taku "redukciu" - tam bude asi najvacsi problem. Da sa kupit redukcia M/M (alebo je to F/F ) na N-konektory?

Este rozmyslam, ze zrusim ten 5m kabel, co tam mam. Je to sice skoro 1cm hruby koax ale je zbytocne dlhy. Mozno z pigtailu odstrihnut konektor, nakripmovat tam normalny BNC a dat tam nejake 2m sietoveho koaxu?

[Maxik]

spravny rozmery zavisej taky na rozmerech plechovky na www.simandl.cz na strance o czfree tam neco urcite vyhrabes...

no ono je nejlepsi mit na kabelu co nejmin konektoru a co nejlepsi kabel (co nejmensi utlum) pokad budes mit kabel 1-1.5m tak ej to suma fuk ale pri 2m+ to chce uz asi lepsi kabel aby se ti ten signal po ceste nezku**** na ty redukci se ti ztraci ze signalu tak +-1-2db a na kazdej konektor pocitej s utlumem 1db. F-F redukce se prodava urcite M-M nevim neshanelsem ale asi jo.

BTW: jaky oznaceni ja na tom tlustym koaxu ?

Glottis, dybys videl co mam namireny na kamose tak by ses skoro divil ze to vubec funguje

[Jezevec]

Koax na BNC bych tam nedaval, je moc tenkej = bude velkej utlum. Metr toho tlustyho stoji od 70Kc.

[Rainbow]

No pocitam, ze pigtail s konektormi najmenej -3db (je to tenky shit), na tom kabli mozno -1db, a na tej home-made super-redukcii -10db

[Maxik]

Koax na BNC bych tam nedaval, je moc tenkej = bude velkej utlum. Metr toho tlustyho stoji od 70Kc.

ses moc drahej, da se sehnat od 35kc EDIT: hmm ale to mam po znamejch

[Dade_Marfi]

H155 45,- za metr ... Konektory N - za 110,- RSMA - za 145,- ... to je zatim asi nejlepsi s cim sem se setkal ... skus mrknout na czfree

[Maxik]

N-kovy konektory www.rasel.cz od 60,-

P.S.: neskryta reklama

[Dade_Marfi]

dik to se hodi ... potrebuju jich ted 120ks

[Dade_Marfi]

mhm tak trosku vic popisu by neskodilo ... treba na ktery kabely to bylo skousene ... pac mam X metru H155 a tudis potrebuju konektory na nej ... predpokladam ze kdys za konektorem neni crimp. tak je to normalni co se mu hrot pripaji a pak se to sesroubuje ?

EDIT: ceny sou s dani ??
- ty redukce SMA->N kolik je na tom utlum ?? je to lepsi nez delat si pigtail ?

[Rainbow]

Ta redukcia bude asi pigtail lebo SMA konektor je malicky a N je obrovsky