On Tue, Sep 10, 2013 at 02:07:48PM +0530, Sujith Manoharan wrote: > Seth Forshee wrote: > > I posted some wireshark traces in case someone else can find something > > else informative that I've missed. They're at > > http://people.canonical.com/~sforshee/wndap350/: > > > > * iperf-iwlwifi.pcapng.gz: Trace from iperf client on Linux STA with > > iwlwifi > > * iperf-server.pcapng.gz: Trace from the iperf server for the same test > > as iperf-iwlwifi > > * iperf-osx.pcapng.gz: Trace from iperf client on OSX, using Broadcom > > wireless > > The link with the iwlwifi client seems to be drowning in RTS/CTS exchanges > compared with the osx client. > > iwlwifi: total: 109087, RTS - 9782 (9.0 %) > osx: total: 522581, RTS - 8366 (1.6 %) Yes, but I don't think that's behind the APs failure to send us frames for long periods of time. I can better compare the RTS/CTS exchanges between the two when I can get an otherwise stable connection to the AP from Linux. Seth -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
