I was on eBay not long ago and happened across a listing for the WIP330 (big brother to the WIP300) for much less than local retail. I decided to take advantage of: a) the good price, b) the current strong position of the A$ versus the US$, and c) it was within 1 hour of closing and the vendor was giving 10% off… and bought it. I honestly should not have bothered: this is a terrible piece of equipment, and now sits beside my bricked Cisco 7970 as the worst online auction purchase I’ve made. But first, a little history…
Some time ago I saw some reports of Linksys releasing a couple of Wi-Fi VoIP handsets. Reviews looked moderately promising, but as one of the devices (the “prestige” version) was based on Windows CE I was disappointed in the lost potential of the device. But then I saw that eBay listing, and I jumped immediately into Gadget Acquisition Syndrome justification mode. “Sure, it’s based on Windows CE, but haven’t you always told people that you believe in horses-for-courses?” said my inner gadget-junkie.
So about a fortnight later the thing arrived. I charged it for a decent amount of time, then configured it for my wireless.
“Failed to connect”.
Google then revealed a litany of people being driven crazy by this device’s inability to connect to a WPA-PSK network. At this point I began to feel very much like Stuart Langridge of LugRadio fame, who only discovered after buying a new laptop that his research had failed him and he had indeed bought a laptop of “military-grade proprietariness” (as I seem to recall one of his fellow LugRadio presenters described it). Had I known that in 2007 a manufacturer of networking equipment (backed by probably the biggest name in corporate and Internet networking today) could release a device that would not connect to a secure network created by THEIR OWN BRAND OF ACCESS POINT (a Linksys WRT54GS[1]), I might have researched that issue further.
Some hope was provided in the form of a firmware update. Unfortunately, like most pieces of networking kit, firmware updates are delivered over the network… In this case, the thing couldn’t connect to the network! I had to shut off encryption on my network for the length of time it took to perform the update — which was doubled by the fact that the firmware on my unit required an interim upgrade to a staging release before the final update (to wip330_v1_02_12S) could be applied.
So with firmware upgraded and encryption re-enabled on my wireless, I tried again…
Same error.
At this point I was very keen to follow this advice and eject the rotten device from my life, but on that page I found the hint that got things working: my access point had AES as well as TKIP enabled, and the WIP330 seems to choke on AES. Disabling AES on the access point finally got the WIP330 on the network. At this point my son wanted to watch something via XBMC, and I found that the client Wi-Fi device through which his XBox attaches still had AES defined so could not connect to the network… Turn AES back on, get the other device attached again, disable AES in it, disable AES in the access point again, and I was set.
Or so I thought. Later in the day, the WIP330 was off the network again. Trying to re-connect to my network brought failure, but power-cycling the device got it online again. Sure enough though, an hour later it was off the network.
One hour. 3600 seconds. The (default) rekeying interval of a WPA-PSK network. The chuffing thing fails to complete rekeying and drops the wireless connection. This time Google has been no help — I guess not enough people persisted through the AES problem to have the thing on the network long enough to hit the rekeying failure.
So right now the thing is useless to me. I’m even contemplating dragging out my old 802.11b access point for the phone (and another couple of old WPA-incapable devices) to run on, but I think the last thing my neighbourhood needs is another 2.4GHz wireless network.
To try and balance this, I will mention a couple of things I like about it. While it was on the network, it was easy to connect to Asterisk and get talking. The device is light (bordering on too light) and the screen is just brilliant. Sound quality was a bit dodgy, but then I haven’t had a chance to use it for long enough to know for sure (and then I was only talking to myself via the Asterisk echo test application). One other thing that’s nice is that Windows CE is largely hidden. There is a browser on the device, which uses the Windows flag as its progress spinner, but other than that it’s out of the way and not screaming “look at me, i’m CE”.
Like I said, however, the fact that in 2007 Linksys can release a device that has such problems just getting connected to a network is a great disappointment. At this stage I think the best that can come of this device is that enough bad press is spread that they don’t sell at their RRP, forcing the price down and making it affordable enough for some crafty Linux hackers who could put an Open firmware on it. Or, hope against hope, perhaps Linksys will see their channel back-up with units that won’t move, and switch to a Linux firmware themselves to get them going.
In the meantime, I’ll keep Googling for “wip300 wpa-psk piece of junk”…
[1] To be fair, my WRT54GS is running OpenWRT and not the stock Linksys firmware. But the binary that provides WPA-PSK in OpenWRT does come straight from Linksys’ firmware…
Crossed Wires 
test
LikeLike