It looks like you are seeing a couple of issues here: 1) We don't seem to know the security mode
This is strange since we do populate the security setting from wlan_t entries of a scan or from the wlan cache. Can you verify that the contents of that structure are consistent with what you expect. 2) On entry of the key, where it doesn't allow you to connect. This is because of an empty bssid being appended to the bssid list because we were assuming that the contents of the wlan_info were all valid when we received a NEED_KEY event, but in reality it's only the essid that's valid. This was logged as a defect which has been fixed in SVN (and also slightly on the nwamd side since it wasn't initialising all the the values leaving them with random values). Thanks, Darren. On 26/08/2009 16:38, Michael Hunter wrote: > On Mon, 24 Aug 2009 13:13:26 +0100 > Darren Kenny <Darren.Kenny at Sun.COM> wrote: > >> I've uploaded a set of the latest GUI packages for Phase 1 to : >> >> /net/jdsserv.ireland/scratch/month/darrenk/NWAM_Manager_Phase_1/i386/2009-08-24 >> >> /net/jdsserv.ireland/scratch/month/darrenk/NWAM_Manager_Phase_1/sparc/2009-08-24 >> >> These were built upon the 2009-08-23-nd build of NWAM Phase 1. >> >> This also includes an updated version of the /usr/bin/network-admin script to >> launch the appropriate tool based on whether nwam is enabled or not. > > When connecting to a wireless network it seems to start out thinking it > doesn't have security and then get confused. I've only tried this with > my latest build so there is a chance this involves some mismatch > although there appears to be inconsistency within the GUIs on idea of > the security of the wlan. > > mph > >> >> Thanks, >> >> Darren. >> _______________________________________________ >> nwam-dev mailing list >> nwam-dev at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/nwam-dev
