All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: David Herrmann <dh.herrmann@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] P2P setup timeout
Date: Mon, 09 Dec 2013 15:03:17 +0100	[thread overview]
Message-ID: <52A5CDA5.7000601@rempel-privat.de> (raw)
In-Reply-To: <CANq1E4R--OowH-LCUX4oSxsJu7yf_2e6Jei8tP+i_BQ_QHiKkw@mail.gmail.com>

Am 06.12.2013 11:18, schrieb David Herrmann:
> Hi
> 
> I am currently working on user-space helpers for P2P setup as part of
> an Open-Source Miracast implementation (openwfd). I can set up a
> P2P-group with my Android test-device just fine, however, it only
> works if initiated by the GNU/Linux host. Once I initiate the
> p2p-connect from the Android device, it creates a group and sends me a
> p2p-invitation which I am unable to accept.
> 
> I am running wpa_supplicant-git from today (but also tried older
> versions), ath9k-htc from linus-git (3.13-rc2) and the relevant log
> files are appended.
> 
> My wpa-config is:
>   ctrl_interface=/var/run/wpa_supplicant
>   update_config=1
>   p2p_go_ht40=1
> 
> And I do nothing else than open wpa_cli and run:
>   p2p_find
>   p2p_connect <peer> pbc
> 
> This works perfectly well if I don't touch the Android device before
> issuing the p2p_connect. However, if I initiate the first connect on
> the Android device, my linux host gets a p2p-invitation:
>   <3>P2P-INVITATION-RECEIVED sa=12:68:3f:4e:39:f2
> go_dev_addr=12:68:3f:4e:39:f2 bssid=12:68:3f:4e:b9:f2 unknown-network
> 
> I tried accepting this invitation via p2p_connect, but just nothing
> happens. I also tried any combination of arguments
> (auth/join/persistent, pbc/pin/PIN#, playing with go_intent=), didn't
> help..
> 
> Looking at the wpa-log, I see a timeout firing repeatedly:
>   P2P: GO Negotiation Request TX callback: success=1
>   P2P: State CONNECT -> CONNECT
>   P2P: Set timeout (state=CONNECT): 0.500000 sec
>   P2P: Timeout (state=CONNECT)
> Below you can see the whole sequence of wpa-messages that repeat over
> and over again until I cancel the connection-request.
> 
> For WFD I need to initiate the connect from the Android device,
> otherwise their WFD stack won't recognize the connection. So if anyone
> has hints what might be wrong here, I'd gladly try out any patches or
> configurations.
> I cannot test whether this happens with other drivers, too, as I
> couldn't get my hands on a device other than ath9k-htc which supports
> p2p on linux.
> 
> If anyone is interested, I'll be presenting OpenWFD at FOSDEM in the
> graphics-devroom. It would be awesome if I can get my Nexus-4 as a
> working demo until then. Otherwise, it'll be just linux<->linux demos
> (non-android), which is already working fine.

Is it related to your "Atheros AR9280: NULL-deref during P2P setup"
issue? Or it is not reproducible any more?

-- 
Regards,
Oleksij

  reply	other threads:[~2013-12-09 14:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 10:18 [BUG] P2P setup timeout David Herrmann
2013-12-09 14:03 ` Oleksij Rempel [this message]
2013-12-09 14:30   ` David Herrmann
2013-12-16 12:00 ` David Herrmann
2013-12-16 12:36 ` Johannes Berg
2013-12-16 13:39   ` David Herrmann
2013-12-16 13:45     ` Johannes Berg
2013-12-16 13:51       ` David Herrmann
2013-12-16 14:57         ` [ath9k-devel] " Oleksij Rempel
2013-12-16 14:57           ` Oleksij Rempel
2013-12-16 15:09           ` [ath9k-devel] " David Herrmann
2013-12-16 15:09             ` David Herrmann
2013-12-16 15:15             ` [ath9k-devel] " Johannes Berg
2013-12-16 15:15               ` Johannes Berg
2013-12-16 15:26               ` [ath9k-devel] " Oleksij Rempel
2013-12-16 15:26                 ` Oleksij Rempel
2013-12-16 15:29                 ` [ath9k-devel] " Johannes Berg
2013-12-16 15:29                   ` Johannes Berg
2013-12-16 15:37                   ` [ath9k-devel] " Oleksij Rempel
2013-12-16 15:37                     ` Oleksij Rempel
2013-12-16 15:53                     ` [ath9k-devel] " David Herrmann
2013-12-16 15:53                       ` David Herrmann
2013-12-17  5:50       ` Ujjal Roy
2013-12-17  7:19         ` 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=52A5CDA5.7000601@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=dh.herrmann@gmail.com \
    --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 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.