Registrován: 23.02.2004
Příspěvků: 254

Mame proti sobe dva 900AP+ (rev. C2 fw 3.07b2) v rezimu bridge Spojeni zatim testujem bez jakekoliv dalsi zateze a chova se dost divne.

Test pingem:
Pri 1k5 paketech se spoj chova vcelku zpusobne (viz test 2). Pri normalnich paketech (viz test 1) se kazda odezva 8x - 20x duplikuje.

Test FTP prenosem:
Pri FTP downloadu je na eth portu incoming traffic cca 2 MBit/sec (!), outgoing zanedbatelny ale FTP bezi cca 60 KBytes/sec.
Pri FTP uploadu je na eth portu incoming traffic cca 350 kBit/sec (!), outgoing cca 680 kBit/sec FTP bezi cca 80 KBytes/sec..

STATUS APcka (Traffic Statistics display Receive and Transmit Packets Passing through the DWL-900AP+) ukazuje ve
"Wireless/Send Good Packets" i ve "Wireless/Send Dropped Packets" uplne stejny hodnoty (+/- jeden paket)

Daji se duplicity nejak ovlivnit nastavenim D-linku? Predstavuju si neco jako delsi cekani na potvrzeni, v krajnim pripade to potvrzovani treba i potlacit...

*******************************************************************************
*** TEST 1 - normalni pakety
*******************************************************************************

PING 192.168.0.20 (192.168.0.20) 56(84) bytes of data.
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=4.00 ms
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=4.84 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=6.97 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=8.27 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=14.8 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=18.3 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=30.5 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=31.3 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=32.0 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=32.8 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=33.5 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=34.3 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=34.9 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=35.6 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=36.5 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=40.5 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=41.2 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=43.8 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=44.4 ms (DUP!)

...
...
...

64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=3.19 ms
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=4.60 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=5.33 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=7.01 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=9.37 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=15.2 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=16.0 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=17.0 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=17.6 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=18.7 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=19.8 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=20.4 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=21.2 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=22.2 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=23.5 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=24.5 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=25.4 ms (DUP!)
64 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=26.1 ms (DUP!)

--- 192.168.0.20 ping statistics ---
1000 packets transmitted, 998 received, +10352 duplicates, 0% packet loss, time 1008964ms
rtt min/avg/max/mdev = 1.884/30.102/164.516/18.322 ms
*******************************************************************************

*******************************************************************************
*** TEST 2 - 1500 B pakety
*******************************************************************************

PING 192.168.0.20 (192.168.0.20) 1500(1528) bytes of data.
1508 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=24.1 ms
...
...
...
1508 bytes from 192.168.0.20: icmp_seq=1000 ttl=64 time=26.9 ms

--- 192.168.0.20 ping statistics ---
1000 packets transmitted, 967 received, 3% packet loss, time 1008666ms
rtt min/avg/max/mdev = 20.354/41.507/94.202/11.307 ms

*******************************************************************************

__________________

Registrován: 25.06.2002
Příspěvků: 474

__________________

Registrován: 23.02.2004
Příspěvků: 254

__________________

Registrován: 30.10.2002
Příspěvků: 733

zdravim

s dlinkama 900 je to hrozna alchymie, musis mit spravny firmware, to je alfa a omega. napis kamosovi na icq 227230827 (v pracovni dobe, jestli muze). jestli nemuzes dopoledne tak na 266176453 a zeptej se ho jakej je ten spravnej firmware. jiank na to ma vliv long/short preamble. base rate nastav na 1-2Mbit a az tu druhou rychlost o radek niz nastav jak chces.

zdenek

__________________

Registrován: 09.05.2002
Příspěvků: 312

Team Member: MOD

Registrován: 23.02.2004
Příspěvků: 254

__________________

Registrován: 23.02.2004
Příspěvků: 254

__________________

Registrován: 11.09.2003
Příspěvků: 3

Registrován: 30.10.2002
Příspěvků: 16

Pokud mas tak dobrej signal tak tem APckum sniz vykon. Nam to dost pomohlo... I na dlouhe spoje jedu 12,5%, jsem v limitu CTU a DUP jsou fuc )))

Pokud do toho tlacis velkej vykon, tak to je jak kdyby se to prervavalo...

V siti mi jede 34 D-LINKu DWL-900AP+ a TP-LINKu TL-WA200+ a s DUP paketama nemam problem

Registrován: 09.10.2003
Příspěvků: 123

2 mischel

Příspěvek č. 10

mam stejny problem jako ty, a Pha centrum. Sum bych tipla ze je tu obrovskej, chytim ze strechy pres 20 siti a samosebou kazdej channel full :-( kazdych cca 5 minut se mi to deje ale nekdy to vydrzi i hodinu, nicmene to tak jedine o vikendech vnoci. mam rezim wireless client, revizi ale Bckovou. :-/