From: Ben Greear <greearb@candelatech.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Unicast packets stop being transmitted to a particular station, under load, when WPA2 is enabled
Date: Sun, 11 May 2014 21:05:28 -0700 [thread overview]
Message-ID: <53704888.9060602@candelatech.com> (raw)
In-Reply-To: <CAHqTa-3Rj-=4A3BoQoD0fb7P=jDd53KvGjxW_BnkoF_+hdWW5g@mail.gmail.com>
On 05/11/2014 08:54 PM, Avery Pennarun wrote:
> On Sun, May 11, 2014 at 11:09 PM, Ben Greear <greearb@candelatech.com> wrote:
>> Can you reproduce with any other type of station
>> device?
>
> I'll try. It's a little tricky since it seems to involve running
> Chrome, etc, rather than my usual command-line tests for which I have
> a wider variety of clients.
>
>> Also, have you tried sniffing with a third device to see if
>> the AP actually puts the ICMP responses on the air?
>
> I did try that. As far as I can tell, the ICMP responses are simply
> not being sent at all.
I haven't dug into many of the stats yet, but it's possible the
ath10k debugfs file would show some types of transmit errors in this case?
Might be interesting to see how long it takes the AP to generate
the tx status response for the transmitted ICMP packets. My firmware
has some extended tx status, but I'm not sure it has anything overly
useful for your case...I was mostly concerned with the tx rate reporting
when writing it.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-05-12 4:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 1:57 Unicast packets stop being transmitted to a particular station, under load, when WPA2 is enabled Avery Pennarun
2014-05-12 2:07 ` Dave Taht
2014-05-12 2:29 ` Avery Pennarun
2014-05-12 2:42 ` Dave Taht
2014-05-12 2:46 ` Dave Taht
2014-05-12 14:49 ` Adrian Chadd
2014-05-12 3:09 ` Ben Greear
2014-05-12 3:54 ` Avery Pennarun
2014-05-12 4:05 ` Ben Greear [this message]
2014-05-12 4:56 ` Avery Pennarun
2014-05-12 5:05 ` Ben Greear
2014-05-12 5:19 ` Avery Pennarun
2014-05-12 7:07 ` Avery Pennarun
2014-05-12 8:21 ` Avery Pennarun
2014-05-12 14:10 ` Ben Greear
2014-05-14 19:07 ` Avery Pennarun
2014-05-14 19:26 ` Dave Taht
2014-05-14 19:38 ` Adrian Chadd
2014-05-15 6:12 ` Avery Pennarun
2014-05-16 20:01 ` Dave Taht
2014-05-16 20:10 ` Adrian Chadd
2014-05-19 21:04 ` Adrian Chadd
2014-05-19 21:07 ` Dave Taht
2014-05-19 21:09 ` Adrian Chadd
2014-05-14 20:20 ` Adrian Chadd
2014-05-14 20:46 ` Adrian Chadd
2014-05-14 21:45 ` Avery Pennarun
2014-05-27 9:53 ` Kalle Valo
2016-06-17 0:01 ` Ben Greear
2014-05-12 14:53 ` Adrian Chadd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53704888.9060602@candelatech.com \
--to=greearb@candelatech.com \
--cc=apenwarr@gmail.com \
--cc=ath10k@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.