Hi Jouni, > -----Original Message----- > From: Jouni Malinen [mailto:j@xxxxx] > Sent: Saturday, November 21, 2015 18:34 > To: Peer, Ilan > Cc: hostap@xxxxxxxxxxxxxxxxxxx > Subject: Re: [PATCH 4/6] tests: Test no P2P GO move when invitation is in > progress > > On Tue, Nov 03, 2015 at 04:24:59PM +0200, Ilan Peer wrote: > > Add a test to verify that a P2P GO does not start a CSA once > > invitation signalling is done, and the P2P client is about to connect. > > Could you please clarify how this is supposed to work? The long wait for CSA > seems to be completed before starting the invitation and there is no checks > for CSA after the invitation is started. > 1. This is based on the timing of P2P GO move which is 30 seconds after the P2P GO has started. The test waits 29.9 seconds after the P2P GO has started and starts the invitation flow, assuming that the P2P GO CSA evaluation is going to happen in 100ms. As this is timing sensitive, I'll change this so it would depend on testing configuration over the control interface. 2. A P2P GO CSA after the invitation is no longer expected, as during the invitation signaling the P2P GO includes only its current operating channel in the channel list. Since the P2P spec requires that the channels in the channel list in the invitation response are a subset of the channels in the channel list in the invitation request, the invitation signaling ends up with only a single channel in the group common frequencies, so when a P2P CSA is considered again, there are no valid channels to move to. I'll clarify this in the test. Thanks, Ilan. _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
