<div dir="ltr">

  
    
    
  
  <div bgcolor="#ffffff" text="#000000">
    On 16/05/2011 22:23, Jouni Malinen wrote:
    <blockquote type="cite">
      <pre>On Tue, May 10, 2011 at 07:52:59PM +0300, Mail4Lior wrote:
</pre>
      <blockquote type="cite">
        <pre>I want to understand why the probe request frames are registered at
the wpa_supplicant only when the device is in listen mode?
</pre>
      </blockquote>
      <pre>This is special functionality for P2P device discovery.

</pre>
      <blockquote type="cite">
        <pre>Which component(fw/driver/supplicant) will handle those probe in
active mode(the device in GO state)?
</pre>
      </blockquote>
      <pre>That depends on the driver. Some drivers handle the Probe Request frames
in firmware or kernel, others may use the AP code in
hostapd/wpa_supplicant to process the frames.

</pre>
      <blockquote type="cite">
        <pre>If this response done by lower layers (driver/fw) how the information
element is passing to those layer, which API is used?
</pre>
      </blockquote>
      <pre>That depends on the driver. Full Probe Request frame (and other
management frames) may be delivered to hostapd/wpa_supplicant (e.g.,
through monitor interface in case of mac80211) or
EVENT_RX_PROBE_REQ/EVENT_RX_MGMT driver events may be used for this.
</pre>
    </blockquote>
    <span style="margin:0px"><span>So</span></span> <span>if</span> <span style="margin:0px"><span>I</span></span> <span>understand</span> <span>correctly</span><br>
    1. <span style="margin:0px"><span></span></span><span>The</span> <span>probe</span> <span>response</span> <span>in</span> <span>P2P</span>
    <span><span>GO</span></span> <span>is</span> <span>always</span>
    <span style="margin:0px"><span>built</span></span> <span>in</span> <span>the</span> <span>wpa_supplicant</span> <span>when using</span> <span>nl80211</span> <span>driver (the</span><span></span> <span>nl80211</span> <span>driver doesn&#39;t have an API for sending the
      Probe Response IE to kernel).</span> <br>
    2. when using nl80211, the drive event EVENT_RX_MGMT
    is used for probe request only at discovery stage(listen mode) the frame registration
    is done only for this period.<br>
    3. The <span>nl80211</span> <span>driver</span> <span>interface</span> is always <span style="text-decoration:none"><span>use</span></span> <span>the</span> <span>monitor</span> <span>interface</span> <span>to</span> <span>indicate/forward</span> <span style="margin:0px"><span>management</span></span> <span>packets</span> <span>to</span> <span>the</span>
    <span>supplicant .</span> when not in
    listen state<br>
    <br>
    <br>
  </div>

</div>