Wpa-psk With Cacko Rom Options

[Terry]

Anyone try connect WPA-PSK AES access point by cacko ROM? How can I configure with AOSS system from Buffalo??

[stupkid]

As far as I know maslovsky is the only person that has tested the WPA stuff. It worked for him, but I don't know any details about his configuration.

[maslovsky]

From Cacko FAQ:

Q: How to configure WPA?
A: Follow these steps:

Create new network connection uding GUI Network Settings, then edit /etc/pcmcia/wlan-ng.opts, find sections corresponding to the newly created connection and add WPA=y
Edit /etc/wpa-supplicant.conf. File contains detailed comments. Also more informaiton about WPA Supplicant is available here: http://hostap.epitest.fi/wpa_supplicant/

After that connect to your network via Network Applet as usual. Note that sometimes it may take a couple of attempts to connect.

Basicaly anything related to WPA needs to be configured manualy via corresponding config files. Get more details on the web page above. I personaly was able to have WPA-PSK working (such setup is easy though), but I have no idea how to configure more complex setups.

[Terry]

From Cacko FAQ:

Q: How to configure WPA?
A: Follow these steps:

Create new network connection uding GUI Network Settings, then edit /etc/pcmcia/wlan-ng.opts, find sections corresponding to the newly created connection and add WPA=y
Edit /etc/wpa-supplicant.conf. File contains detailed comments. Also more informaiton about WPA Supplicant is available here: http://hostap.epitest.fi/wpa_supplicant/

After that connect to your network via Network Applet as usual. Note that sometimes it may take a couple of attempts to connect.

Basicaly anything related to WPA needs to be configured manualy via corresponding config files. Get more details on the web page above. I personaly was able to have WPA-PSK working (such setup is easy though), but I have no idea how to configure more complex setups.

maslovsky, would you mind to tell me what parameter I need to set in wpa_supplicant.conf when I config to connect to WPA-PSK+AES? Since after i set all of thing, also can't connect to my access point properly. And, is it have a debug mode or related log i can check what problem of it?

[maslovsky]

Sorry, but I have no idea what AES is. My knowledge of WPA is only limited to being able to configure the simpliest case - WPA-PSK. You'll be better off reading wpa supplicant documentation and maybe searching hostap mailing lists.

[Terry]

Finally, I still can't work with WPA-PSK also, but I can connect it by wep128 with AOSS also. So it seems may have some problem in wpa-supplicant.conf. But it have no any debug log so can't trace any problem in it.

[Torsten Wagner]

Hi Terry, Hi Maslovsky,

working on exactly the same stuff.

I followed the FAQ and setup both config files.
I'm using a DLINK DCF-660 card.
However I was unlucky up to know.

I just like to get WPA-PSK but it will not connect. Furthermore I also searched for a log file to see what really happens. But I didn't find something up to now.

I will try today in the evening some more ideas. If I now somethink new I will let you know.

Mybe someone (if I'm successfull I will do) can startup to create a more detailed How-to for this topic since WAP is running off and more and more people like to use WPA. If we are lucky we find a programmer for a little GUI for all the noobs like me.

Greetings

Torsten

[Da_Blitz]

i might be able to shed some light on this, did you put the wpa2-psk in the wpasupplicant.conf file, if you didnt then you have to use one of the helper programs to enter it when the deamon requests the logon password

i would recomend you get a wpasupplicant.conf from a mainline distro such as debian and edit it as at the end of the file it includes alot of examples that are commented out

some useful terms:
tkip: tempory key itegrity protacol, ie WPA1, or WPA
same as wep but passwords change every 4 seconds (not sure about time) so very hard to get enogh weak packets to crack, uses the RC4 cipher (ie wep with rotating keys)
AES: Advanced encryption cypher ie WPA2 also known as WPA-Enterprise or 802.11i
it also has a preshared key version WPA2-PSK, which is what you are looking for, however note that WPA-PSK and WPA2-PSK are not the same thing (first one is still wep based, second uses AES)

i definatly recomend you look at the conf with exapmles and grep for the entry that has both WPA2 and psk (pre shared key) in it

if you need more info just post

[Torsten Wagner]

Hi everyone

just to let you know. I was finally successfull to use my DLINK DCF 660W with WPA-PSK/TKIP
I write this post already on my C1000
As I promised I will write a Newbie-How to and paste it here.....


Happy!!!!!!!!!!!!!!!!

Torsten

[ant]

Hi,

I'm still stuck with the Socket CF + LP WLAN.

After running wellenreiter and stopping/starting the "dhcp client" I see hostap module is loaded:

firmware_class 3840 0 [spectrum_cs]
hermes 4752 0 [spectrum_cs]
hostap 96992 0 [spectrum_cs]
orinoco 40112 0 [spectrum_cs]
...
spectrum_cs 6832 0

Does it mean I have to tweak the hostapd & wlan-ng settings and have WPA-PSK?
Can somebody confirm WPA is now supported by hermes/orinoco?

THX

Ant

[maslovsky]

Hi,

I'm still stuck with the Socket CF + LP WLAN.

Socket WiFi card uses Orinoco/Spectrum drivers, which don;t support WPA.

[gsgmx]

Hi everyone

just to let you know. I was finally successfull to use my DLINK DCF 660W with WPA-PSK/TKIP 
I write this post already on my C1000
As I promised I will write a Newbie-How to and paste it here.....


Happy!!!!!!!!!!!!!!!!

Torsten

Hi,

i'm trying to get WPA working now, no luck.

Same hardware as you.

How about your HOW-TO?


TIA
George

[gsgmx]

Hi,

i'm trying to get WPA working now, no luck.

NOW it works and it looks not too difficult to get it running.
My short description how i got it to work:

Follow what Anton had posted:

Q: How to configure WPA?
A: Follow these steps:

Create new network connection uding GUI Network Settings, then edit /etc/pcmcia/wlan-ng.opts, find sections corresponding to the newly created connection and add WPA=y

Edit /etc/wpa-supplicant.conf. File contains detailed comments. Also more informaiton about WPA Supplicant is available here: http://hostap.epitest.fi/wpa_supplicant/

-------
There they also supply a very short wpa-psk supplicant file i used:

CODE

# WPA-PSK/TKIP

ctrl_interface=/var/run/wpa_supplicant

network={
 ssid="example wpa-psk network"
 key_mgmt=WPA-PSK
 proto=WPA
 pairwise=TKIP
 group=TKIP
 psk="secret passphrase"
}

i added

scan_ssid=1

after ssid=


------- Anton:
After that connect to your network via Network Applet as usual. Note that sometimes it may take a couple of attempts to connect.
-------

After several tries even with eject / insert in between i finally got it running by a Z reboot ...
And it works without any further problems.

Yust resume after a sleep is a little bit problematic. Wlan comes sometimes back after a resume, sometimes not.
If not - it is sometimes enough to use the QT network app to let it associate again sometimes not.
If not a eject / insert eiher physical or by command is needed followed by a new connect thru QT network app.

I would like to put eject / insert and connect into 1 shell script. But i could not find a command for the connect. Only thing which comes near is an idea i found in an other, rather old post http://www.oesf.org/forums/index.php?showt...l=network+start how i might be able to start the wlan association by command:

/sbin/cardctl scheme <name-of-scheme-in-.opt-files>

i tried "cardctl scheme qpewlan1" that fails with a "... wlan0: No such device."


Anybody some ideas/hints?

TIA

George

[Cagilaba]

THANKS gsgmx!! That was really useful -- I've been trying unsuccessfully to get WPA-PSK working with my Linksys WCF12 and SL-C1000 for a day or two. Using the simple wpa_supplicant.conf you pointed out and adding scan_ssid=1 made all the difference.

(Thanks also to speculatrix who sent me useful info!).

I wonder why it doesn't work after waking from suspend? That's a little annoying.

I had to upgrade the station (secondary) firmware on my wifi card before it would work with WPA (flashed it to 1.8.4). All necessary tools are included in Cacko 1.23 full!
Thanks Maslovsky! (donation time, I think...)

I would recommend the following great page to anyone looking to update the firmware on their Prism-based card:

http://linux.junsun.net/intersil-prism/

Now I have to see if I can connect to the WPA (Enterprise - TKIP, MSCHAP, PEAP etc. etc.) wireless at work...

[Torsten Wagner]

Hi everyone,

Sorry for my late response. I was somehow busy the last days.
I promised a How-to but have very little time in the moment.
Therefore, I write here just some quick and dirty hints.

1. Find out whether your network card is correct installed after insertion.
The Zaurus should show the card correctly after insertion if you are unsure, please type
dmesg inside the konsole-window. There you should see what's going on with your WLAN card.

2. If your WLAN cards works correct, create a new network connection under Settings->Network. Go tab by tab. Add a suitable name at first. Type the SSID of your WLAN-network instead of Non-Spec ESS-ID. Do not add WEP settings. All other information should be the same as for your "normal" computers. Mostly you only have to set-up TCP/IP and DNS (ignore all other tabs). Again choose the same settings as for your other machines (if you have to define a IP address of course choose a new resp. free one for your Zaurus)

3. Save the settings.


4. Follow the steps described here already to change the two files.
Add WPA=y at /etc/pcmcia/wlan-ng.opts
You have to search for the setup which you created before under the network settings. The Keyword INFO= will be the same as the name you choose for your network.

MOST IMPORTANT: Never use the GUI again to change settings for this network from now on, since it will overwrite your WPA=y settings. If you do so (e.g. if you change your IP address with the help of the GUI) you have to repeat step 4 again !!!!!
You can use the midnight commander (or any other text-editor) to change the file.
However, you require root privileges. Therefore use su or sudo

CODE

sudo mc -e /etc/pcmcia/wlan-ng.opts
# start the midnight commander in root mode and open the file.
# To use the menu-keys you have to press ALT-Number. ALT is the second Japanese character beside Ctrl.
# Add
WPA=y
# Inside your network connection

This should result in

CODE

qpewlan0,*,*,*)
        INFO='My Network name'
        ..... # more settings about your network
        WPA=y # this line you have to add by hand
       ;;

5. Edit /etc/wpa-supplicant.conf. This file contains a good set of examples. Don't worry about all the preface. Just look at the example and try the one which is as close as possible to your WLAN settings. You can check your WLAN Settings on your access point or on one of the "big" computers in your network.

The easiest way to create a hopefully working configuration file is the following:
type

CODE

cp /etc/wpa_supplicant.conf /etc/wpa_supplicant.conf.bak
# just to backup your old file.
sudo wpa_passphrase your_ssid your_password > /etc/wpa_supplicant.conf
# this generates a new file with the minimum-settings. In addtion your password is not written in clear-text which increases security.
more /etc/wpa_supplicant.conf
# should result in
network={
              ssid="your_ssid"
              psk="your decrypted password in hex-code"
}

If your access point does not broadcast the SSID (check your access point settings) you might have to add the following line to your wpa_supplicant.conf file.

CODE

network={
              ssid="your_ssid"
              psk="your decrypted password in hex-code"
              scan_ssid=1
}

This tells your WLAN-card to communicate with your "hidden" access point even if it can not receive any SSID information at the beginning.

After that reject and insert your WLAN-card again. Now you should be able to connect to your access point. If not check again both files. The standard settings for the wpa_supplicant.conf file will try to use all possible combinations, unless we define a specific one. Therefore, I assume less is more in this case. That means do not try to make to many settings at once. E.g. for me the above example works fine for a WPA-TKIP connection with PSK decryption even without defining specific TKIP and PSK.



I hope all this helps. Furthermore, many many thanks to Anton again, who make all this possible. Thanks Anton. Remember, if you are successful and happy to access the Internet with your Zaurus, go to

Anton's Webpage

and click on the "Make a Donation" button to show him that his work is valuable and important for you. Please consider, that for other PDA-Platforms e.g. under Microsoft-OS you have to pay horrible amounts even for stupid little apps which allow you to connect your access point by WLAN. You can decide how much you like to support open source operated PDAs by place a donation to Anton. This will give him more time for further development.


Two little hints at the end. It seems some WLAN cards need a firmware update before there are able to run in WPA mode. Check this forum for more information.
For me the automatic connection is not useful and sometimes brings me in trouble. I switched it off, since I like to decide whether I will be online or not. Power consumption of a unused but online WLAN connection is a second argument for manual connection.

Bye
Torsten