All,
I’ve been working for some time to resolve some
throughput dropout issues with a WDS wireless LAN connection.
I’ve done extensive wireless debugging without finding
a clear wireless mechanism that explains drastic and/or complete throughput
dropouts, such as the attached run shows.
In some cases, rebooting the PC driving the wireless unit
restores normal operation.
So my question is, is there any mechanism between iperf,
windows, TCP/IP, and/or lan NIC drivers that might cause a stalled condition
during an iperf run, and how can I debug or differentiate between a stall
condition on the PC side of the wired LAN and a similar stall in the WLAN
internal firmware.
The iperf client below is executing on a Dell D800 laptop
with a dedicated PCMCIA 100Mb LAN NIC direct connected to a 802.11g WDS client
bridge unit, wireless connected to a D-Link DWL-2700AP direct connected to a HP
desktop computer (iperf endpoint server) via it’s motherboard LAN
NIC. Both are running win XP pro and standard LAN/TCP/IP stacks.
When not stalled, this wireless link has the capability to
consistently clock at least 15 Mb, but, of course, the client bridge firmware
could be causing the stall on either the wired or wireless sides.
Any help would be greatly appreciated.
Thanks,
