ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: ANQP to second AP while associated to a first.
Date: Tue, 30 Jun 2015 08:20:27 -0700	[thread overview]
Message-ID: <5592B3BB.2080909@candelatech.com> (raw)

In our testing we are trying to do 802.11r roaming with ANQP.

After initial association, we do not see ANQP on the air when trying
to roam to a new AP.

I think the problem might be that the firmware has issues sending
packets to a second AP when we are already associated to a first.

I am curious if anyone has successfully tested any sort of
.11r roaming with ath10k?

And, I am curious if anyone knows if or how ath10k can send
to a second AP while connected to a different AP  (Like creating a peer for the new
AP, perhaps???)

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

             reply	other threads:[~2015-06-30 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 15:20 Ben Greear [this message]
2015-06-30 19:48 ` ANQP to second AP while associated to a first Janusz Dziedzic

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=5592B3BB.2080909@candelatech.com \
    --to=greearb@candelatech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox