Recent patch somewhat breaking p2p

Arik Nemtsov arik at wizery.com
Thu Jul 26 06:14:03 EDT 2012


This commit seems to break p2p connections in certain situations:

commit 579a80982ad07619373876c09cdd60e2afcba5b5
Author: Jouni Malinen <jouni at qca.qualcomm.com>
Date:   Fri Jun 8 18:24:08 2012 +0300

    P2P: Assume GO Negotiation failed if GO Neg Conf wait times out


With this patch applied, the GO negotiation sequence effectively
becomes a one-shot process. Once the GO neg response is transmitted,
and a go neg confirm frame is not seen in 100ms, the negotiation
fails.

This is problematic in various scenarios:
1. The GO neg response might not have been acked by the peer. The Tx
status of this frame is currently ignored. In general this is ok -
since the peer maybe got it but switched the channel before the ack.
Unfortunately if the peer didn't get it, the negotiation will fail.
2. Some devices (namely the Galaxy Nexus device) find the 100ms
timeout too harsh. Sometimes 200ms+ go by before a negotiation confirm
is transmitted.

When this patch is reverted, p2p works well.

Arik


More information about the HostAP mailing list