Small doubt about wpa supplicant.
raghavendra.akkasali at gmail.com
Thu Dec 6 21:22:58 EST 2007
Thanx for your reply.
Will you please tell me how to disassociate using supplicant. In my
case after enabling supplicant as daemon, i will get ip using dhcp client
and then start working. Once my work is done. I have to disassociate with
the AP rt? or just killing wpa_supplicant is enough?
Also as I am integrating wpa supplicant to some device. using iwlist to scan
is must or is there some other way by which I can get almost same output as
that of scan. If using iwlist is must then I have to port iwlist also. So I
am asking some thing that does provide same output like iwlist but with less
On 12/6/07, Dan Williams <dcbw at redhat.com> wrote:
> On Thu, 2007-12-06 at 12:54 +0530, Raghavendra. S wrote:
> > Hi All,
> > I am newbie to wireless. So only this silly question comes from
> > me...:)
> > I am using wpa supplicant. Now on our device. we have some WLAN code
> > which does scanning..association ..etc all those basic wireless events
> > and then it call dhcp client to get IP.
> > Now they asked me to integrate wpa supplicant to provide security.
> > I saw even wpa supplicant does scanning, association....authentication
> > and then connects. In short wpa supplicant is a binary with config
> > file....which establishes secure channel.
> > My question is if I integrate wpa supplicant I guess I dont need
> > previous code which does scanning..association...etc. I can directly
> > invoke wpa supplicant and then use dhcp client to get IP. Am I
> > correct?
> That is correct. Get rid of your own scanning and association code.
> Create the right config file for wpa_supplicant, let it do it's job, and
> then when it's connected you do the DHCP manually.
Regards & Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the HostAP