Super-User wrote: > So Quaker, is the bottom line that there is nothing I can do at this > time with the current state of software development to get WPA to work > with my Broadcom 4318? If this is the bottom line, I can stop pursuing > this and focus on other things until a supported build arrives.
Yes. -- Quaker > > Emery > > Quaker Fang wrote: > >> Emery wrote: >> >>> Okay, >>> >>> I am using NDIS 1.1, which was the latest version I could find. >>> Please tell me what version of ndiswrapper I should be using to get >>> WPA support. >> >> >> Sorry, at present, the ndis 1.1 is the latest one, no new version >> available. >> >> -- >> Quaker >> >>> >>> Emery >>> >>> >>> >>> Quaker Fang wrote: >>> >>>> Emery, >>>> >>>> Emery wrote: >>>> >>>>> Quaker, >>>>> >>>>> Please clarify something. You stated that the problem with WPA >>>>> identification is with the NDIS driver. I copied the driver from >>>>> my working Windows XP installation, performed the iconv on the >>>>> .inf file and went through the ndiswrapper >>>>> compilation/configuration without a problem. The driver has built >>>>> in support for WPA, because I am currently sending this over my >>>>> WAP connection within MS XP, which is WPA enabled. With those >>>>> facts how is it that the NDIS driver is not supporting WPA? >>>> >>>> >>>> >>>> "ndiswrapper compilation/configuration" -- the codes of ndiswrapper >>>> you used don't support WPA. >>>> >>>> -- >>>> Quaker >>>> >>>>> >>>>> Emery >>>>> >>>>> ----------------------------------- >>>>> >>>>> >>>>> >>>>> Quaker Fang wrote: >>>>> >>>>>> Hi Emery, >>>>>> >>>>>> Emery Rudolph wrote: >>>>>> >>>>>>> Hello Valerie, >>>>>>> >>>>>>> There is so much conflicting information regarding this matter, >>>>>>> I am glad to speak to a primary developer. My confusion is that >>>>>>> I keep hearing that I would need to upgrade these packages, but >>>>>>> I do not have them installed at all. I have read some >>>>>>> information saying it was included with the build and others >>>>>>> saying I need to download and install them. Can you tell me >>>>>>> which is correct? If I do not have them installed can you send >>>>>>> the the exact link to the packages. >>>>>> >>>>>> >>>>>> >>>>>> I am the developer of Solaris WPA. >>>>>> The answer is, under WPA-PSK mode, if you use DHCP to get IP >>>>>> address, you need SUNWcry installed, if you use static IP, not need. >>>>>> As I know, at present, the SUNWcry package is not downloadable to >>>>>> community users. >>>>>> As Valerie said, this situation will be changed when his project >>>>>> putback. >>>>>> >>>>>>> Additionally, would you know if the lack of these packages would >>>>>>> result in WPA WAPs showing up as WEP in the dladm scan-wifi output? >>>>>>> >>>>>>> >>>>>> No, this is caused by the ndiswrapper driver, the ndiswrapper >>>>>> driver doesn't support WPA. >>>>>> >>>>>> -- >>>>>> Quaker >>>>>> >>>>>>> Emery >>>>>>> >>>>>>> >>>>>>> Hi Emery - >>>>>>> >>>>>>> Yes, you do need to upgrade the SUNWcry/SUNWcryr packages >>>>>>> everytime you upgrade >>>>>>> your system. These are available in the closed-bin tar bundle, >>>>>>> associated >>>>>>> with each build. I'm not sure, specifically, how this affects >>>>>>> WPA driver, but >>>>>>> I do know that changes in the core crypto components often >>>>>>> require all the >>>>>>> modules to be updated as well for other tasks. >>>>>>> >>>>>>> This is documented here: >>>>>>> http://www.opensolaris.org/os/project/crypto/Documentation/sunwcry/ >>>>>>> >>>>>>> This will soon be changing, as I am wrapping up a project to >>>>>>> pull strong >>>>>>> crypto into the base OS. >>>>>>> >>>>>>> hope that helps, >>>>>>> >>>>>>> Valerie >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>> >> >> >>
