<div>Hi,</div>
<div> </div>
<div> One more doubt about disassociation. In my code I will enable wpa supplicant using </div>
<div>system("./wpa_supplicant -ieth0 -Dmarvell -c./wpa_supplicant.conf -B");</div>
<div>So it will be a daemon. Now to disassociate I need socket fd using which wpa_supplicant is communicating, How to get that. If I store the opened socket fd in some temp file then can I use same sock fd to disassociate and then kill wpa_supplicant using kill command or is there any better approach for the same.
</div>
<div> </div>
<div>-Raghu.</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 12/7/07, <b class="gmail_sendername">Dan Williams</b> <<a href="mailto:dcbw@redhat.com">dcbw@redhat.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Fri, 2007-12-07 at 17:20 +0530, Raghavendra. S wrote:<br>> Hi Dan,<br>><br>> Actually in my case I want to get scan result first then configure
<br>> wpa_supplicant.conf and then I will enable wpa_supplicant. Because<br>> user has to first see the scanned result and after that he can<br>> configure to which AP he want to associate with and security models he
<br>> want to use. So I need some independent small AP scan code similar to<br>> "iwlist eth0 scan".<br><br>Again, look at driver_wext.c. Code to scan and get results is there.<br>You can print out whatever you want given the information it returns.
<br>You can create a tool that incorporates that code, prints out what the<br>user wants from scan result information passed back by the driver, and<br>then spawn wpa_supplicant however you like.<br><br>Dan<br><br>> -Raghu.
<br>><br>><br>> On 12/7/07, Dan Williams <<a href="mailto:dcbw@redhat.com">dcbw@redhat.com</a>> wrote:<br>> On Fri, 2007-12-07 at 16:45 +0530, Raghavendra. S wrote:<br>> > Hi,<br>> >
<br>> > Does any one know small AP scan code which gives<br>> similar/same<br>> > output as that of "iwlist eth0 scan". I dont want to use<br>> iwlist<br>> > because of its size.
<br>><br>> Look at the driver_wext.c code from wpa_supplicant at<br>> wpa_driver_wext_scan() and<br>> wpa_driver_wext_get_scan_results(). You<br>> don't need to screenscrape output if you can just use the
<br>> values<br>> directly.<br>><br>> Dan<br>><br>><br>><br>><br>><br>><br>> --<br>> Regards & Thanks<br>> Raghavendra. S<br><br></blockquote></div><br><br clear="all">
<br>-- <br>Regards & Thanks<br>Raghavendra. S