RE: Throughput dropouts
Marc,
Yes, I've used wireshark, ethereal, airopeek, netstumbler, Chariot,
spectrum analyzer with waterfall plots, etc. I'll admit that there's a
possibility that there's some WDS-specific management packet sequence
that I haven't found, but it's not for lack of looking. I've even
received some "help" from the manufacturer, but it always comes down to
either "environmental" or "host PC test setup", and no solid supporting
evidence to differentiate between the two, so I'm here making one last
attempt to rule out "host PC test setup", or maybe get lucky and find
something that can be fixed. I've been much less deep as a user of
iperf than a user of the 802.11g and related standards and tools, so
there could be a well-known iperf/PC OS issue that I could have
overlooked too.
As to tcptrace, this looks quite interesting, and new to me. Any
further expert user hints will be appreciated while I bring it up.
Thanks for your help and interest,
Bob Jenness
-----Original Message-----
From: owner-iperf-users --at-- dast.nlanr.net
[mailto:owner-iperf-users --at-- dast.nlanr.net] On Behalf Of Marc Herbert
Sent: Tuesday, April 01, 2008 4:48 PM
To: iperf-users --at-- dast.nlanr.net
Subject: Re: Throughput dropouts
2008/4/1, Bob Jenness <bjenness --at-- geofocus.com>:
> 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.
What do you mean by wireless debugging?
Did you try tools like wireshark and tcptrace.org ?
Cheers,
Marc