You must be registered and logged in to post to this forum.
I use WPA without problem; its a complex passphrase with mixed-case letters, numbers and symbols. I have a Linksys WRT54G running Tomato firmware, WPA Personal/TKIP.
No problems, no unusual setup routines to make it work. I hooked-up to spykee using an ad hoc network, put in my ssid and password, shut off spykee and then turned it back on an it simply worked.
Yes, I spoke too soon. Everything worked for about a day (3 beeps of joy).... then I rebooted my Netgear router. Since then, despite the dual WPA mode being set, Spykee again refuses to talk WPA - unlike my PSP, Laptop, IPod and every other wireless device I have lying around which all seem to think the wireless key is fine thank you very much.
I tried fiddling with the router settings again in the vain hope I might work out why it just worked for a period. Alas, to no avail, so I'm stuck with ad-hoc mode and, frankly, I'm unwilling to reset everything else on my network to WEP in order to accommodate the foibles of my Spykee....
I have mine working, of sorts.
I have a Netgear DG834PN(?) running in WPA-PSK + WPA2+PSK mode. It was originally hidden SSID, but I had to make it visible for Spykee to see it (why can't we type the SSID in manually??). My passphrase is in a form "alphabetic*and*asterisks*only".
Anyway, I added the settings to the Spykee, then went back from ad-hoc to WLAN mode, and without really expecting it, I found it popped up in the robot selector.. .so it did successfully connect to my WiFi network. So it does seem to work, at least with these settings on a Netgear router.
BTW, I have noticed one problem: I can connect to Spykee with my girlfriend's laptop, but not with my own. The difference is mine has a bunch of corporate firewalls, all of which I think I've switched off, but still it refuses to connect in any manner (ad-hoc and AP). Looking at the traffic with Wireshark/Ethereal, when I open the 'Connect' dialogue box, it suddenly shows a stream of malformed UDP packet headers (4 rather than min 20 bytes long) - which are most likely the connection attempts - and because of this, I suspect my laptop's stateful firewalls are blocking the traffic.
So... if you have any kind of firewall software on your laptop, it's possible it might interpret the Spykee client as some kind of trojan or exploit, and block the requests.