p2p start listen
Sun Dec 18 04:55:41 PST 2011
Thanks. My fault that expressed the opposite meaning. I wonder why
wpa_drv_probe_req_report() is called first.
My understanding on remain-on-channel is to ensure that the device is
on the indicated channel to receive the probe req frames.
And besides, for OFFCHANNEL_TX driver, after sending action frame
(like GO neg req) out on peer's listen or operating channel, how does
our own driver/device know how long it should stay on this channel, to
guerantee peer's resp? There is a wait_time parameter when sending
action frame, I think this is to ensure TX success (the max time
waiting for TX_STATUS, right?).
2011/12/18 Jouni Malinen <j at w1.fi>:
> On Wed, Dec 14, 2011 at 02:28:19PM +0800, Huijun Gan wrote:
>> In function: wpas_start_listen(), I found that
>> wpa_drv_remain_on_channel() is called prior to
>> wpa_drv_probe_req_report(). Isn't it more intuitive that calling
>> wpa_drv_probe_req_report() first? Is there any special reason to call
>> wpa_drv_remain_on_channel() first, or is my understanding on
>> remain-on-channel not right?
> Which version of wpa_supplicant are you using and where did you get that
> from? The version in hostap.git seems to call wpa_drv_probe_req_report()
> before wpa_drv_remain_on_channel() in wpas_start_listen().
> Jouni Malinen ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?PGP id EFC895FA
> HostAP mailing list
> HostAP at lists.shmoo.com
More information about the Hostap