Problems with DWL-900AP+ and DWL-810+

We have a small wireless network made of three DWL-810+ and one
DWL-900AP+. It works relatively well, but we often have dupes in out
ping tests. Sometimes we even have one dupe for each ping and, worse,
sometimes they are almost 10, like this:

64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=5.43 ms
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=6.76 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=7.37 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=10.2 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=15.2 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=32.1 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=34.9 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=35.8 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=36.6 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=37.5 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=38.4 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=39.5 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=40.9 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=42.4 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=18 ttl=128 time=44.4 ms (DUP!)

The pratical problem is slow data transfers, since I assume that the
problem occurs also with "non-ping" traffic.

This is a real example of a ping test to a DWL-810+ from a Linux
server wired to the DWL-900AP+:

PING 172.16.5.195 56(84) bytes of data.
64 bytes from 172.16.5.195: icmp_seq=1 ttl=127 time=4.32 ms
64 bytes from 172.16.5.195: icmp_seq=2 ttl=127 time=3.73 ms
64 bytes from 172.16.5.195: icmp_seq=3 ttl=127 time=2.91 ms
64 bytes from 172.16.5.195: icmp_seq=3 ttl=127 time=4.02 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=4 ttl=127 time=4.66 ms
64 bytes from 172.16.5.195: icmp_seq=4 ttl=127 time=5.76 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=5 ttl=127 time=2.72 ms
64 bytes from 172.16.5.195: icmp_seq=5 ttl=127 time=3.29 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=6 ttl=127 time=2.10 ms
64 bytes from 172.16.5.195: icmp_seq=7 ttl=127 time=2.81 ms
64 bytes from 172.16.5.195: icmp_seq=7 ttl=127 time=3.48 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=8 ttl=127 time=2.76 ms
64 bytes from 172.16.5.195: icmp_seq=8 ttl=127 time=3.41 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=9 ttl=127 time=2.27 ms
64 bytes from 172.16.5.195: icmp_seq=10 ttl=127 time=4.57 ms
64 bytes from 172.16.5.195: icmp_seq=10 ttl=127 time=5.66 ms (DUP!)
64 bytes from 172.16.5.195: icmp_seq=11 ttl=127 time=4.63 ms
64 bytes from 172.16.5.195: icmp_seq=11 ttl=127 time=5.44 ms (DUP!)

--- dwl810-esanof ping statistics ---
11 packets transmitted, 11 received, +7 duplicates, 0% packet loss,
time 10106ms rtt min/avg/max/mdev = 2.101/3.811/5.765/1.110 ms

The server is at 172.16.5.129, the AP at 172.16.5.130 and the bridges
are at 172.16.5.193, 194 and 195, netmask 255.255.255.0 no gateway
(0.0.0.0).

Any clues? Thanks in advance.

--
Luiz Lima
Image Link Internet
http://www.imagelink.com.br

Luiz Lima <(E-Mail Removed)> writes:

> --- dwl810-esanof ping statistics ---
> 11 packets transmitted, 11 received, +7 duplicates, 0% packet loss,
> time 10106ms rtt min/avg/max/mdev = 2.101/3.811/5.765/1.110 ms

> Any clues? Thanks in advance.

No but I sometimes see the same thing when I scan one of my networks
to see which systems are on-line. I have one 900AP+ talking to a 650+
card in a Toshiba notebook running XP - sometimes I'll see 4 or 5 dupes
coming back from it...

Billy Y..