I did not see the ACX module for my Hawking 54g card, which I am using right now to post this from Puppy 3.01, so I know it can be done.BarryK wrote:tempestuous,tempestuous wrote:Yes, that was Dougal and me.BarryK wrote:One of the contributors to the Network Wizard has put that code in that puts up a message about WPA not being supported
Whether the Network Wizard should warn about modules not supporting WPA is up for discussion (I think it should), but the wag-profiles.sh script definitely must be updated whenever new wifi modules are introduced - because wpa_supplicant needs a different "-D" (driver) parameter depending on what module is in use.
You will notice that the WPA section of the wag-profiles.sh script not only defines the modules which are WPA-compatible, but more importantly it specifies what "-D" parameter to pass to wpa_supplicant. The modules and "D" parameters that are currently listed in the wag-profiles script are absolutely correct thus far ... but of course, recent kernels now provide some new wifi kernel modules which must be incorporated.
How to know what -D parameter applies to each wifi module? Careful reading of the wpa_supplicant README and also the documentation provided with the source code of each wifi driver. I discussed this at length with rarsa when he first wrote the Network Wizard. Since then, I have helped Dougal add rt61/rt73 (Ralink) and r8180/r8187 (Realtek). We also added WPA2 support, which requires a significantly different configuration file for wpa_supplicant.
I just downloaded Puppy-4.00-k2.6.25 to have a look at the new wifi modules.
These are the new modules which need to be added to the Wizard:
D parameter "wext" -
ath5k
b43
b43legacy
iwl3945
iwl4965
rndis_wlan (Broadcom USB)
rt61pci
rt73usb
D parameter "ipw" -
rtl8180
rtl8187
Notice that the new rt61pci and rt73usb modules use the "wext" D parameter, whereas the old rt61 and rt73 modules use the "ralink" D parameter. This is because the new modules are from a completely revised development stream; the "next-generation" rt2x00 series.
I cannot guarantee that the new driver parameters I have specified are completely correct. I do not own all of these devices, and the information is difficult to glean from the web. Testing may prove me wrong on some of these.
Thanks very much for figuring that out. I didn't have a clue how to do that, but really wanted it done for 4.00final. I've added the extra modules in the appropriate places in the wag-profiles.sh script.
Interesting, too that the no WPA support message would pop up when the wifi card is not even detected/known...
rokky