From: Ben Greear <greearb@candelatech.com>
To: "Jörg Pommnitz" <j.pommnitz@gmail.com>,
"Adrian Chadd" <adrian@freebsd.org>
Cc: Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Joerg Pommnitz <pommnitz@yahoo.com>
Subject: Re: Please don't puke: Modifying Frame Version, Beacon and Probe-Response values
Date: Wed, 1 Jun 2016 12:43:08 -0700 [thread overview]
Message-ID: <574F3ACC.3040008@candelatech.com> (raw)
In-Reply-To: <CAEvAWuHgna4cdgkhQrQY4xo4XyaCAhkkf1zo8iDA_Gqgjc1Jeg@mail.gmail.com>
On 06/01/2016 12:38 PM, Jörg Pommnitz wrote:
> This is about IBSS mode. The nodes form an ad-hoc backbone. Clients use normal, standard conforming APs.
So, about IBSS. Only ancient QCA firmware and 'CT' firmware supports IBSS as far as I know.
I was never able to get RSN to work with IBSS reliably in CT firmware, so it would have to be un-encrypted
traffic. And, AMSDU + IBSS has hardware bugs, evidently, so firmware will disable AMSDU for you.
That said, adding a few more hacks for fake beacon ids might not make it any worse :)
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
prev parent reply other threads:[~2016-06-01 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 8:44 Please don't puke: Modifying Frame Version, Beacon and Probe-Response values jpo
2016-05-31 10:50 ` Michal Kazior
2016-05-31 15:53 ` Adrian Chadd
2016-06-01 11:34 ` Joerg Pommnitz
2016-06-01 19:18 ` Adrian Chadd
2016-06-01 19:29 ` Ben Greear
2016-06-01 19:33 ` Adrian Chadd
2016-06-01 19:37 ` Ben Greear
[not found] ` <CAEvAWuHgna4cdgkhQrQY4xo4XyaCAhkkf1zo8iDA_Gqgjc1Jeg@mail.gmail.com>
2016-06-01 19:43 ` Ben Greear [this message]
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=574F3ACC.3040008@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=j.pommnitz@gmail.com \
--cc=michal.kazior@tieto.com \
--cc=pommnitz@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox