[PATCH] P2P: Fix for multi channel concurrency

Jouni Malinen j
Fri Nov 22 07:58:29 PST 2013

On Thu, Sep 12, 2013 at 06:19:30PM +0530, Sreenath Sharma wrote:
> In case of GO-NEGOTIATION, the connected STA channel is set as the forced
> frequency even though the device is multi channel concurrent capable.
> This will cause only that channel getting added in the channel list of
> GO-NEGOTIATION request packet. So if both the peers try to force their
> receptive STA channels and if both are different, there will be
> failure - "no common channel" (7).
> Ideally in case of multi channel concurrency, the connected STA channel
> should not be set as forced channel and should only be set as preferred
> channel. This will cause full channel list getting updated in the
> GO-NEGOTIATION request packet, so that there can be channel intersection
> if the peer's proposed channel is different.
> This is a regression from commit 0d08efa447a5c5fb20bbed18a2ced36a8afe9221.

Sorry, I somehow missed this in the queue and just noticed it now that I
went through some fixes in AOSP. The changes here look fine in general,
but the debug prints were a bit off. I fixed this in equivalent way
functionality, but with the debug messages modified to make more sense.

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list