Puppy Linux Discussion Forum

[davidknibb]

The have been lots of posts about WPA encryption - and it's got difficult to find out where workingsolutions have been posted - some of the posts are useful discussions that don't seem to have culminated in a solution.
I'm using
Puppy 2.02, Hard Disk install on an HP XE2 laptop.
My network card is Linksys WPC54G (ver1.2)

I've worked manually with NDISWRAPPER, and it all works fine with WEP - but not quite with WPA. But my output from

#iwlist wlan0 scan

looks very promising -

wlan0 Scan completed :
Cell 01 - Address: 00:0F:B5:BD:0D:3C
ESSID:"davidsnetwork"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:0/100 Signal level:-17 dBm Noise level:-256 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:bcn_int=200
Extra:atim=0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

----------------------------
It sees that the encryption is WPA in TKIP mode.

So I think that there might be an easy next step (optimism) to
supplying the password
bringing up the interface.

Something that I know well enough how to do in Debian
(iwpriv wlan0 set WPAPSK=xxxxxxxxx)
But don't seem to be able to do in Puppy.

I've looked through dozens of posts and not seen an answer.

Can anyone point me please to the post where an answer is provided.

Many thanks

David

[PaulBx1]

I don't know if iwpriv is appropriate, maybe it's just for WEP?

The usual way is to use a wpa_supplicant.conf file. Do you have one of those? The readme's for the drivers seem to be pretty good, and should tell you how to use it.

What is your error indication? Some boot message? It would be good for you to print that portion of "dmesg" out here, and give us your wpa_supplicant.conf, and show us what your rc.wireless and rc.local scripts look like also.

I am using ndiswrapper and wpa_supplicant. Getting it running was pretty painful, and I still don't know what the difficulty was. But it is working.

[tempestuous]

iwpriv is used to access features of wifi drivers which are unique to that driver. This would include control of WPA setup ONLY if the wifi driver has inbuilt support for WPA, but currently there is only one such driver: Ralink.

All other drivers (and ndiswrapper) require the "helper" utility wpa_supplicant. http://www.dotpups.de/dotpups/Wifi/wireless-drivers/wpa_supplicant_README.txt gives detailed information.

I believe your chipset is Broadcom.

[davidknibb]

Thanks - I've been away for a few days - I'll follow these up later today if I have time.

Much obliged.

David