WZC: Keeping it on with version 0.5.4
George S. Lockwood
gslockwood at gmail.com
Fri Aug 4 10:24:43 EDT 2006
Actually, I was able to run the 4.9 binary in parallel with the WZC. There
might have sometimes been a slowness to connect but not sure. I did not,
however, see the WZC causing a disconnect???
The primary reason for wanting WZC to run concurrently is for its UI the
"Wireless Network Connections" window for its ability to display the
thanks so much (and I have 2 other questions for you today -I'll open new
threads for them; they aren't related to WZC),
On 8/3/06, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
> On Thu, Aug 03, 2006 at 03:21:43PM -0700, George S. Lockwood wrote:
> > I'd prefer to have the Windows Wireless Service running with the
> > wpa_supplicant. Version 0.5.4 turns WZC off in its init function but
> > commenting that one line does keep WZC alive, the supplicant connects
> > disconnects moments later.
> It's not wpa_supplicant disconnecting later--it's WZC killing the
> connection.. Could you please explain what exactly you are trying to do
> and why WZC should be controlling the same interface as wpa_supplicant
> at the same time?
> > Apparently, there are other issues. What might they be?
> If you have two programs trying to control the same interface, end
> result is not going to be very stable.. WZC requests the driver to
> disconnect in such a case and in addition, it tries to process EAPOL
> packets which makes negotiations quite confusing since two different
> supplicants are trying to process the packets.
> > I know that the earlier versions leave WZC running so I could go back
> > build my modifications on it. However, I'd like to use the very latest
> > not miss the new enhancements and bug fixes.
> With earlier versions, you were required to disable WZC manually. The
> fact that WZC must be disabled has not changed; 0.5.4 is just able to do
> it automatically.
> Jouni Malinen PGP id EFC895FA
> HostAP mailing list
> HostAP at shmoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the HostAP