To clarify; at bootup Puppy should automatically load the hostap_pci driver for this device.

That was a quick reply!

Yep, that looks like the critter, alright!

How do I know if it is loading the hostap_pci driver at bootup ... I mean, is there some config file or script that I can take a look thru and check to be sure that it is (and that I haven't messed something up somewhere along the lines)?

I was able to connect with the network wizard ("Connect" app) only after I copied the contents of the wpa_supplicant2.conf file to a file named .WPA2.conf in the same directory (/etc/network-wizard/wireless/wpa_profiles.

The reason I created this file is that the program gave me an error message saying there was no supplicant file named .WPA2.conf.

I didn't notice a mention of this file in this thread, so I posted this.

My wireless module is: ath_pci
On the same pc i have 2 puppy 4.30 (old kernel), one for each hard disk (full installation).
All went well during last months. Yesterday, suddenly, wifi connection of puppy installed in hda1 failed whereas the other one in hdb1 is still perfect (I am using it now).
Network-wizard reported:
-----------------
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
-----------------
I went to /var/run , made a "wpa_supplicant" directory but
it was erased as soon as i attempted to restart the connection (by Network wizard).

Is there any file in hdb1 (where connection is OK) to copy in hda1 (where connection fails) to solve the problem by a file-transfusion?
Saluti.
I downgraded to wep-128. So i solved. _________________Qui si usa Linux
http://www.puppylinux.org
Sulmona - ItalyLast edited by Spaccafumo on Wed 21 Dec 2011, 09:17; edited 1 time in total

When forum member rarsa announced the initial development of the wifi component of the Network Wizard approximately 3 years ago, I warned him that it was near-impossible to accommodate the configuration differences of all wifi adaptors and access points, and that he would probably receive no thanks from the majority of users whose configurations work perfectly, but more likely abuse from the minority whose configurations don't work perfectly.
The earlier post is a sad confirmation of this prediction.

It needs to be noted, at the outset, that we're talking about an individual instance here.
It should also be noted that hidden SSID's can be a problem in Linux usually with WPA encryption (even though the poster failed to indicate the type of encryption being used). This is a shortcoming of wpa_supplicant, the application running behind the Network Wizard, and this will be the case (obviously) with all Linux distributions. But more fairly, it's also a shortcoming of certain Linux drivers which fail to interact with wpa_supplicant in a standardised manner.
So again, success or failure will often depend on the nuances of the particular combination of wifi device and router.
Forum member JustGreg did some thorough testing with hidden SSID's here
http://www.murga-linux.com/puppy/viewtopic.php?t=29205

You will see that some wifi devices (and their Linux drivers) work fine, some don't.

Windows XP contains very few, if any, wifi drivers. Most are provided by the individual vendors, and the only reason opensource drivers and utilities need to be used in Linux is because of the discriminatory practice of many wifi vendors in not providing Linux drivers, themselves.
Ultimately, any "failure" under Linux is directly the fault of the wifi device manuafacturers.

And in this particular instance, the wifi connection failure was actually due to the user setting their router for hidden SSID (which is not the default setting on a wifi router) ...
which is not such a bad thing, because hiding your router's SSID, ironically, makes your wifi network less secure.
This has been discussed in technical detail on the forum before
"HOW-TO have a more secure wireless network"
http://www.murga-linux.com/puppy/viewtopic.php?p=207892#207892

The network wizard works great for me, except for the bit about saving a profile and automatically using it on the next boot. I have to re-run the network wizard every boot. Before I resort to trying to trying to determine all the correct parameters for a command line script to leave on my desktop, does anyone have any suggestions for me?

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum