Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dariusz Gadomski <dariusz.gadomski@canonical.com>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org,
	Jay Vosburgh <jay.vosburgh@canonical.com>
Subject: Re: Cisco's Wi-Fi Direct Client Policy and iwlwifi (8260)
Date: Thu, 21 Sep 2017 17:53:48 +0200	[thread overview]
Message-ID: <20170921155348.fcos6iootplin6uj@leonard> (raw)
In-Reply-To: <1503076802.15969.322.camel@coelho.fi>

On Fri, Aug 18, 2017 at 08:20:02PM +0300, Luca Coelho wrote:
Hello Luca,

Thank you and Johannes for looking into this.

> > I'll try to dig the thread I had about this and take it again with our
> > system engineers to hear what they have to say about it.

Any news about that thread by any chance?

> > In the meantime, I think it would be helpful if you could contact Cisco
> > about this issue as well.

I heard from them that since there's a P2P IE transmitted from the
client then the behavior is correct. They recommended switching the
option in the AP to xconnect-not-allow which is supposed to allow
P2P-capable devices to associate as long as they won't use P2P
functionality.

> Also, as a workaround if you are really not interested in using P2P is
> to start wpa_supplicant with “p2p_disabled=1” in the configuration. 
> This should prevent the P2P IE from being sent.

Unfortunately that didn't help. Although I was not able to run any
P2P-specific commands in wpa_cli (e.g. p2p_find, p2p_listen all
return FAIL) connecting to the AP in question kept failing.
Do you have any further hints on debugging this?

> --
> Cheers,
> Luca.

Thanks!
Dariusz

  reply	other threads:[~2017-09-21 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 12:48 Cisco's Wi-Fi Direct Client Policy and iwlwifi (8260) Dariusz Gadomski
2017-08-18 17:16 ` Luca Coelho
2017-08-18 17:20   ` Luca Coelho
2017-09-21 15:53     ` Dariusz Gadomski [this message]
2017-09-05 13:23   ` Johannes Berg

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=20170921155348.fcos6iootplin6uj@leonard \
    --to=dariusz.gadomski@canonical.com \
    --cc=jay.vosburgh@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@coelho.fi \
    /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