All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jasmine Strong <jas@eero.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath10k <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: rebuild crypto header in RX data frames
Date: Mon, 23 Oct 2017 11:28:18 -0700	[thread overview]
Message-ID: <CAGyitvNj+74HafQ9Aps1HTmknTxa0ZUgV7hao1A8mJ4rV7cibw@mail.gmail.com> (raw)
In-Reply-To: <9407ed1f-2bd9-3fd0-981d-1a20452e8ba9@dd-wrt.com>

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.

On Sun, Oct 22, 2017 at 3:31 AM, Sebastian Gottschall
<s.gottschall@dd-wrt.com> wrote:
> after some tests i have to correct my test
>
> 802.11n qca chipsets can connect to the ap without issues. but another 9984
> based chipset in client mode is able to connect, but no data is passing
> through. there seems to be a encryption problem
> Am 21.10.2017 um 06:46 schrieb Kalle Valo:
>>
>> Jasmine Strong <jas@eero.com> writes:
>>
>>> --94eb2c1c1feaa3aaea055c03c0cd
>>> Content-Type: text/html; charset="UTF-8"
>>> Content-Transfer-Encoding: base64
>>
>> BTW, I think that both ath10k and linux-wireless lists reject HTML mails
>> so only me and Sebastian saw your email.
>>
>
> --
> Mit freundlichen Grüssen / Regards
>
> Sebastian Gottschall / CTO
>
> NewMedia-NET GmbH - DD-WRT
> Firmensitz:  Stubenwaldallee 21a, 64625 Bensheim
> Registergericht: Amtsgericht Darmstadt, HRB 25473
> Geschäftsführer: Peter Steinhäuser, Christian Scheele
> http://www.dd-wrt.com
> email: s.gottschall@dd-wrt.com
> Tel.: +496251-582650 / Fax: +496251-5826565
>

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2017-10-23 18:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 16:28 [PATCH] ath10k: rebuild crypto header in RX data frames Kalle Valo
2017-10-20 16:28 ` Kalle Valo
2017-10-20 19:43 ` Sebastian Gottschall
2017-10-20 19:43   ` Sebastian Gottschall
2017-10-20 20:11 ` Sebastian Gottschall
2017-10-20 20:11   ` Sebastian Gottschall
     [not found]   ` <CAGyitvP0wquoo_8_ma3rcj+riJ5Wgfo7+pmbUOx9pQRwFcQHYA@mail.gmail.com>
2017-10-21  4:42     ` Kalle Valo
2017-10-21  4:42       ` Kalle Valo
2017-10-21  7:58       ` Sebastian Gottschall
2017-10-21  7:58         ` Sebastian Gottschall
2017-10-21  4:46     ` Kalle Valo
2017-10-22 10:26       ` Sebastian Gottschall
2017-10-22 10:31       ` Sebastian Gottschall
2017-10-23 18:28         ` Jasmine Strong [this message]
2017-10-24  4:50           ` Kalle Valo
2017-10-24  4:50             ` Kalle Valo
2017-10-24 16:09             ` Ben Greear
2017-10-24 16:09               ` Ben Greear
2017-10-24 19:19               ` Jasmine Strong
2017-10-24 19:19                 ` Jasmine Strong
2017-10-23 14:24   ` Vasanthakumar Thiagarajan
2017-10-23 14:24     ` Vasanthakumar Thiagarajan
2017-10-23 19:35     ` Sebastian Gottschall
2017-10-23 19:35       ` Sebastian Gottschall

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=CAGyitvNj+74HafQ9Aps1HTmknTxa0ZUgV7hao1A8mJ4rV7cibw@mail.gmail.com \
    --to=jas@eero.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.gottschall@dd-wrt.com \
    /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.