Hi Jouni,<div><font><span style="background-color:rgba(255,255,255,0)">Is ANQP information consumption limited to wpa_supplicant? I thought that any client could read the ANQP information through BSS command?</span></font></div>
<div><font><span style>Is this understanding correct.?<br></span></font><br>On Monday, March 24, 2014, Shyam <<a href="mailto:shyamms2003@gmail.com">shyamms2003@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div><div><div>Thanks Jouni for your reply.<br></div>Okay, Its a bit clear now..However I am curious to know one thing from your reply:<br></div>Is ANQP information consumption limited to wpa_supplicant? I thought that the client could read the ANQP information through BSS command?<br>
<br></div>Thanks,<br></div>Shyam<br><div><div><div><div><br>> As I understand from the code the ANQP fetch is supported by 2 commands<br>
> 1. FETCH_ANQP- To Fetch ANQP information from all the BSSIDs.<br>
> 2. ANQP_GET- Fetch BSSID for a single BSSID.<br>
> Now what was interested to see is that the FETCH_ANQP banks upon the<br>
> in-memory cache maintained in the BSS structure. If the wifi is turned<br>
> on-off or when the BSS flush happens this cache is cleared and hence we<br>
> loose the data. Was there any reason why you didnt think about writing the<br>
> anqp information into a file/DB in which case the data would be available<br>
> upon state resets?<br>
<br>
I'm not sure whether any ANQP information should really be expected to<br>
remain constant and since there is no other way of confirming its<br>
current validity apart from fetching it again, I don't see much point in<br>
storing it to a file. The BSS table should not really be flushed during<br>
normal operation, so the information there remains valid as long as the<br>
AP is in range (and then for three minutes, by default, after that to<br>
avoid temporary out-of-range state dropping an entry).<br>
<br>
> Were you suggesting that clients read ANQP information from the BSS command<br>
> and they cache it?<br>
<br>
No.<br>
Okay, so the <br>
What type of ANQP information are you thinking of here and what is the<br>
justification in assuming it to remain static for longer periods of<br>
time?<br>
<br>
> in-memory cache maintained in the BSS structure. If the wifi is turned<br>
> on-off or when the BSS flush happens this cache is cleared and hence we<br>
> loose the data. Was there any reason why you didnt think about writing the<br>
> anqp information into a file/DB in which case the data would be available<br>
> upon state resets?<br>
<br>
I'm not sure whether any ANQP information should really be expected to<br>
remain constant and since there is no other way of confirming its<br>
current validity apart from fetching it again, I don't see much point in<br>
storing it to a file. The BSS table should not really be flushed during<br>
normal operation, so the information there remains valid as long as the<br>
AP is in range (and then for three minutes, by default, after that to<br>
avoid temporary out-of-range state dropping an entry).<br>
<br>
> Were you suggesting that clients read ANQP information from the BSS command<br>
> and they cache it?<br>
<br>
No.<br>
<br>
What type of ANQP information are you thinking of here and what is the<br>
justification in assuming it to remain static for longer periods of<br>
time?<br>
<br>
</div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 20, 2014 at 11:09 PM, Shyam <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','shyamms2003@gmail.com');" target="_blank">shyamms2003@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div><div>Hi Jouni,<br>
</div>As I understand from the code the ANQP fetch is supported by 2 commands<br></div></div></blockquote><div> 1. FETCH_ANQP- To Fetch ANQP information from all the BSSIDs.<br></div><div> 2. ANQP_GET- Fetch BSSID for a single BSSID.<br>
</div><div>Now what was interested to see is that the FETCH_ANQP banks upon the in-memory cache maintained in the BSS structure. If the wifi is turned on-off or when the BSS flush happens this cache is cleared and hence we loose the data. Was there any reason why you didnt think about writing the anqp information into a file/DB in which case the data would be available upon state resets?<br>
</div><div>Were you suggesting that clients read ANQP information from the BSS command and they cache it?<br><br></div><div>Pls share your thoughts?<br><br></div><div>Thanks<span><font color="#888888"><br>
</font></span></div><span><font color="#888888"><div>Shyam <br></div></font></span></div></div></div>
</blockquote></div><br></div>
</blockquote></div>