maybe this small patch hint here should help to make this patch better
--- rx_desc.h (revision 3655)
+++ rx_desc.h (working copy)
@@ -239,6 +239,9 @@
HTT_RX_MPDU_ENCRYPT_WAPI = 5,
HTT_RX_MPDU_ENCRYPT_AES_CCM_WPA2 = 6,
HTT_RX_MPDU_ENCRYPT_NONE
i suggest the following patch on top of yours. please tell me if my
thoughts are correct here. its mainly a guess
--- htt_rx.c (revision 3656)
+++ htt_rx.c (working copy)
@@ -550,6 +550,11 @@
return IEEE80211_TKIP_IV_LEN;
case HTT_RX_MPDU_ENCRYPT_AES_CCM_WPA2:
Jasmine Strong writes:
> When we tried this patch, it completely broke all wpa2-ccmp-aes
> traffic.
Which patch, Vasanth's or Sebastian's? I even tested myself, with both
CCMP and TKIP on both AP and client modes, and didn't see see any
problems. What kind of setup you have?
I tested on a x86 l
even if he used my patch. my patch should have no influence to wpa2
ccmp. it just adds the new ccmp 256 + gcmp modes
Am 21.10.2017 um 06:42 schrieb Kalle Valo:
Jasmine Strong writes:
When we tried this patch, it completely broke all wpa2-ccmp-aes
traffic.
Which patch, Vasanth's or Sebastian
On Saturday 21 October 2017 01:41 AM, Sebastian Gottschall wrote:
> i suggest the following patch on top of yours. please tell me if my thoughts
> are correct here. its mainly a guess
I agree we need to take care of this for newly added ciphers as well. How about
making it as a separate patch
t
Am 23.10.2017 um 16:24 schrieb Vasanthakumar Thiagarajan:
On Saturday 21 October 2017 01:41 AM, Sebastian Gottschall wrote:
i suggest the following patch on top of yours. please tell me if my thoughts
are correct here. its mainly a guess
I agree we need to take care of this for newly added cip
Jasmine Strong writes:
> That's what I saw. A bcom client was able to associate and not pass
> any traffic. This is on all three of 9882, 9888 and 4019.
Thanks for the report, we'll investigate it. And I see that your email
was now succesfully delivered to the list:
http://lists.infradead.org
On 10/23/2017 09:50 PM, Kalle Valo wrote:
Jasmine Strong writes:
That's what I saw. A bcom client was able to associate and not pass
any traffic. This is on all three of 9882, 9888 and 4019.
Thanks for the report, we'll investigate it. And I see that your email
was now succesfully delivere
That can't be the case here, since we see it break the mesh too (where
the clients are other QCA radios.)
We're now seeing very slow mesh peering with a 9882 leaf to a 4019
gateway, with the second version of this patch.
It took more than five minutes for one of the leaves to successfully
peer (an