linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: ath10k 10.1 firmware cannot do ANQP queries
Date: Tue, 19 May 2015 11:39:50 -0700	[thread overview]
Message-ID: <555B8376.3090600@candelatech.com> (raw)

I took some time to debug this in my 10.1 CT firmware.

It appears that the problem is the ANQP queries may be destined
for APs that the station is not currently connected to.  So, the
firmware cannot find the peer, and then it just fails to put the
management frame on the air.

I have fixed my CT firmware to use the 'bss-peer' when the real peer
for a mgt-frame cannot be found.  That appears to work.

Unless upstream firmware does something similar, I think ANQP
(GAS) queries are going to remain broken on ath10k.  I am not
sure of any sane way to do a work-around in the driver, unless
you want to add fake peers and then make them go away sometime
later (when you assume the mgt frame has been properly put on the air).

A simple test case is to use recent wpa_cli:

> anqp_get 00:0e:8e:f8:73:96 1
OK
<3>GAS-QUERY-START addr=00:0e:8e:f8:73:96 dialog_token=0 freq=5180
<3>GAS-QUERY-DONE addr=00:0e:8e:f8:73:96 dialog_token=0 freq=5180 status_code=0 result=SUCCESS
<3>ANQP-QUERY-DONE addr=00:0e:8e:f8:73:96 result=SUCCESS
>

That MAC addr is an AP that the station is NOT connected to.  Even if you
have no ANQP support in the AP, this should still put a packet on
the air I believe...so you should be able to do simple testing with
a sniffer.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


                 reply	other threads:[~2015-05-19 18:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=555B8376.3090600@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).