From: Ben Greear <greearb@candelatech.com>
To: Avery Pennarun <apenwarr@gmail.com>, 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 20:09:21 -0700 [thread overview]
Message-ID: <53703B61.3050305@candelatech.com> (raw)
In-Reply-To: <CAHqTa-3YUpt3jByNxiEkPGV52CoRDS-R4W33ywKVLa-Ye9d2bQ@mail.gmail.com>
On 05/11/2014 06:57 PM, Avery Pennarun wrote:
> Version: 3.15-rc1 and ath10k-stable-3.11-8 (both via backports to kernel 3.2.26)
> Firmware: 10.1.467.2-1
>
> Steps:
> - Configure ath10k as AP on channel 149, width 80 MHz, WPA2 encryption
> - Connect my 2009 macbook
> - Start a ping of 8.8.8.8 in the background from my macbook
> - Generate some traffic. The trigger varies, but running uTorrent or
> quickly opening a lot of background tabs in Chrome usually seems to
> set it off within a couple of minutes. iperf and isoping don't seem
> to cause any trouble.
>
> Expected:
> - ping keeps pinging
>
> Actual:
> - tcpdump on the ath10k host shows ICMP requests coming in, and
> responses going out.
> - tcpdump on the macbook shows ICMP requests going out, but no
> responses coming back.
> - tcpdump -I (radiotap mode) on the macbook is a little hard to
> understand since it's encrypted, but it shows some packets coming out
> of the ath10k (broadcasts, I think) but no unicast packets to the
> macbook.
> - tcpdump on the macbook *does* show broadcast packets arriving. For
> example, ARP requests and "ping -b 192.168.1.255" (my local subnet IP
> address) get through.
> - Disconnecting and then reconnecting the wifi on my macbook fixes the
> problem until it next triggers.
> - Other STAs connected to the AP are not affected when the one STA
> isn't able to communicate (although each one has the potential to
> trigger the problem)
Can you reproduce with any other type of station
device?
Also, have you tried sniffing with a third device to see if
the AP actually puts the ICMP responses on the air?
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 3:09 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 [this message]
2014-05-12 3:54 ` Avery Pennarun
2014-05-12 4:05 ` Ben Greear
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=53703B61.3050305@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.