X51v WPA Wifi Problems

[ksong12]

I have seen people have working WPA connections, albeit not on an Axim. It was a WM6 smartphone, some type of HTC, I don't remember which one.

There are also posts about the Axim working with WPA for some, not with others. Seems to be a router compatability problem, possibly with specific chipsets. Can you try WPA with your Linksys, see if that works? I will try my Axim at school (We have Linksys routers), since the other guy had it working there, once we get back from spring break.

Oh, and copy and paste (ctl+V) doesn't seem to work for me... it'll be a pain to type the 64 characters.

[Zoandar]

The only posts I ran across where it seemed WPA and the Axim worked together were in WPA-Enterprise environments, where they use LEAP servers for certificates instead of PSK. I wrote to one of those folks today and asked if he knew how to set the Axim for WPA-PSK on a home LAN, but I haven't been notified of a response yet.

There was one point in all the settings I tried where WPA was trying to work, but kept insisting I provide a "certificate" to verify my identity before it would complete the connection. I have no idea how to go about doing that, since I am not in an Enterprise environment. But had I been, I might have had it working at that point.

I'll try to set the Linksys back up in a day or so and see if the Axim can use WPA with it. I'll be busy tomorrow.

I am 99.999% reliant on Graffiti, but for a job like entering in a long key, I switch to the on-screen keyboard. When I typed in the 64 character key on the Axim I actually got it right on the first try. It was a router-generated key, so just a jumble of characters. The hardest part was not losing my place. It was certainly stupid on some design engineer's part not to let the paste command work there, or at the very least, provide an option to show the characters while they are being entered.

During later testing, I just used a shorter WPA key on the router and Axim that was easy to enter. But if you are accessing your school LAN, I don't suppose you would have that option.

What adds to the frustration is that sometimes when I tap one of the on-screen letter keys, expecting it to turn black while "depressed", like normal, it does NOT. So I am not sure if the tap "took" as a key press since all I get to see is a maximum of 13 asterisks. But I forged ahead blindly and it did end up being correctly entered. I think whether the on-screen key turns black is an issue with how well the screen is aligned. I used to have a LOT of trouble with that on Palm OS devices, constantly having to re-calibrate the touch screen, so I am familiar with how being out of calibration manifests itself.

[ksong12]

Yep, that problem also annoyed me. I basically gave up trying to enter our school's WPA key on my X51v. Maybe I'll try afterschool one day again. Ah well.

On the iPhone, the letters get "bigger" when you press them, and then you can change the letter before letting go, so it feels safer that I know what letter I am entering, since that has the same limitation: No copy and paste, and just some asterisks that you can't see scrolling.

[Zoandar]

For me, I have to go along very slowly and deliberately. It also helps to re-align the screen right beforehand.

I have become convinced that many design engineers never use the products they bring to market. Either that, or they are way more stupid than I thought. :-)

Similar issues exist with the Messaging app for email in the Axim. Unless I enter at least one character manually first into the message, it also won't allow me to paste anything. Really nuts, IMHO.

[ksong12]

Wow, I never noticed that. That is indeed quite annoying. Sometimes, I think the same thing about the people actually using the products they release. I mean, some bugs are just so obviously. Although, I do believe this was intended for "security" (although I really don't see how its any bit more secure) Let us know how it goes with the Linksys!

[Zoandar]

I have some interesting news to report.

I set up my older Linksys WRT54G ver. 6 router as an access point by connecting its "Internet" (WAN) jack to a LAN jack on the new D-Link DIR655 Wireless Extreme N router, using a standard CAT5 cable. Since Linksys uses the 192.168.1.x domain, and D-Link uses the 192.168.0.x domain, I was assured by Ikehiker in an earlier post that it would be OK. All he said I had to do in addition was to copy the DNS addresses assigned by my ISP from their listings in the DIR655 and use them in the WRT54G. If I didn't there might be a long delay if the Linksys used the D-Link's IP address for its DNS sever, and the Axim might time out before it got connected to the Linksys.

One final step was to make sure the channels used between the 2 routers on wi-fi did not overlap, so he suggested I pick from 1,6, and 11. I set the Linksys to ch6, and the D-Link to ch 11.

Viola! I had the Axim X61v connected to the Linksys. It cannot see the files on the D-Link's LAN, but I am not concerned about that.

Next, I set the Linksys to use WEP encryption, and returned the D-Link to Auto WPA/WPA2 encryption with a 63 character key. Neither system seems to affect the other, yet they are sitting within a foot of each other on a table. I also have the Linksys range extender antennas (longer) still on it.

What really surprised me was how easy this was! And I was actually able to set up BOTH wifi sources on my notebook, and use it to configure the Linksys without connecting a cable between them! I know accessing a router's settings with wi-fi is a crap shoot, but it worked OK (more below).

So, once I got all that up and running, I decided to try the Axim with WPA-PSK encryption on the Linksys, just to know if it would do the same thing I posted regarding my problems with that in the D-Link.

Well, this is where my notebook's accessing the Linksys by its wifi connection failed me. Once I switched encryption that way on the linksys router, I lost it and couldn't reconnect by wi-fi, even with the notebook set up with the right settings. So I strung a cable from the notebook to the Linksys for the remainder of the testing.

It turns out that the Axim X51v WORKS with WPA-PSK encryption when connected as such to the Linksys WRT54G router! So whatever the problem was before, it is an issue between the D-Link router and the Axim's wi-fi.

In the end, I set the both routers to WPA-PSK encryption. Then I set my notebook so it prefers the newer D-Link wi-fi first. But if necessary, I can connect it to either router by wi-fi.

One last fun fact:

There is a website http://www.speakeasy.net/speedtest/speedtest.swf
that one of my ISP techs told us about. You select from several servers around the country, one at a time, and it measures your upload-download speed in Mb/sec. I suspected that wired access would be better performance than wireless, but had never actually checked. What I found was that certain of the 8 server sites in all directions from my Midwest location dropped the mb/s performance anywhere from 10 to as much as 50% using wi-fi, compared to the same server site using a hard wired connection.

Thanks to everyone for the help and suggestions!! :approve::approve:

[Zoandar]

There is one more consideration that I had forgotten. I have a D-Link DP-301U USB print server on the LAN connected to the D-Link router. We all use it to access a common printer, by using an IP address and the "LP" method of setting it up.The actual reason I got it was so I could print wirelessly from my Axim. So, I need the Axim and the print server on the same range, but I also want everyone else to still access the print server.

The solution looks to be in the first of the 2 alternatives Ikehiker posted previously, so I can have the Linksys router on the same 192.168.0.x range as everything else. So I am going to try that next. I'll post the results.

Eventually I'd like to ask D-Link why the WPA-PSK encryption misbehaves on their router but works apparently fine on the Linksys router. Maybe they can tell me what is actually happening when it keeps cycling the connection on precise 20 second intervals.

[Zoandar]

I now have the Linksys and D-Link routers connected, all running on the 192.168.0.x range, with both providing WPA-PSK wifi.

To refer to the instructions by Ikhiker:

To use a router as an access point, you need to disable the DHCP, set a static IP to something in the D-Link's IP set (probably 192.168.0.x where x is something other than 1), set the wireless channel to something different from that used on the D-Link (if D-Link is set to 6, use 1 or 11 on the Linksys), give it a different SSID, set the IP range on the D-Link DHCP so it excludes the one used by the Linksys, plug an ethernet cable from one of the LAN ports on the Linksys (not the WAN) to one of the LAN ports on the D-Link (this may require a crossover cable but I think the Linksys is auto sensing so a normal cable should work).

In this setup, the D-Link should supply the Axim with an IP but in some cases, you need to set a static IP on the device.

I'd like to clarify a couple things I had to figure out on the WRT54G setup as I was following the above.

- There are actually two places where DHCP is "set" on the Setup page of the router. The first one is under Internet Setup / Internet Connection Type, and was "Automatic Configuration - DHCP". That is not the one to change.

- The second one is further down the page, under Network Setup / Network Address Server Settings/DHCP Server. THAT one is the one to disable.

Just above that is where you set the Linksys router's Static IP address to be within the D-Link range.

During these changes, I was using my notebook with a LAN cable going to one of the LAN ports on the Linksys. After the above, and setting the wi-fi channel to 6 ( I have the D-Link on 11) I then saved those settings and opened the Wireless settings page.

When I changed the SSID name, and then clicked Save Settings, I lost connection with the Linksys over that cable. The last thing it said to do was to Release/Renew. But I could no longer access the Linksys on that cable.

So I went to the Linksys and removed the LAN cable feeding it from the D-Link (which was in the Linksys Internet/WAN jack), and moved it to the Linksys LAN port #1. Then I unplugged the cable that I had been using to set up the Linksys from my notebook, and plugged my main LAN cable, from the D-Link, back into the notebook.

I was then able to access the Linksys router on its newly assigned IP address in the 192.168.0.x range.

As Ikehiker suspected, the Linkys did not require a crossover style LAN cable to connect it this way to the D-Link router. A standard cable works fine.

Once accessing the Linksys again, I clicked its Release/Renew buttons as that previous message had said to do. It seems odd that the Status/Internet IP, Subnet mask, and Default Gateway IP are all zeros now. The DNS fields aren't even there! It is blank next to them. But despite these unusual sights, my Axim found the Linksys WPA encrypted wi-fi and connected, with a good signal. And I can now resume accessing my Print Server with the Axim as well. So things are good to go!

Thanks again for everyone's help!! :approve::approve:

[ksong12]

Yep, as I suspected, its an incompatability. My friend who has it working has the same router as you do. Keep in mind that WiFi speed depends on many factors, such as distance to router, etc.

Did you do that test on your Axim? (I hope not ;-)).

With my old Netgear WGR614v6 router (802.11g), speed was indeed slower than with wired, but with my new Belkin router, speed on my laptop using wired and wireless is pretty much the same. Very fast :) Of course, my Axim doesn't work...... but.... heh.

When you tested wireless, did you use your D-Link, or your Linksys?

Also, could you perhaps you could search through the menus of your D-Link compared to your Linksys, maybe some setting is different. Perhaps this is a problem with all Pre-N routers on the market. If so, I hope it's fixed in the final N standard!

[Zoandar]

Did you do that test on your Axim? (I hope not ;-)).

Well, just for fun I tried just now. The test requires Flash 7. But Adobe doesn't list a Flash 7 player for the IE that is in WM5. I did get on the web page for the test with the Axim, but I can't run it.

When you tested wireless, did you use your D-Link, or your Linksys?

I have tested both. The D-Link is a bit faster.

Also, could you perhaps you could search through the menus of your D-Link compared to your Linksys, maybe some setting is different. Perhaps this is a problem with all Pre-N routers on the market. If so, I hope it's fixed in the final N standard!

Having been through them both to set all the above, I think it is safe to assume that the settings are pretty much the same. I didn't notice anything standing out, at least. It is probably a D-Link specific issue. WEP encryption won't support Wireless N data transfer speed, so when I had WEP running on the D-Link, it disabled the N support and ran in mixed mode b and g. I am pretty sure I later tried WPA again while still running in mixed b and g only, no N, and had the same issue. So unless it is a specific method of how the N technology router operates with N turned off, then I would say it isn't likely part of the N specification that is causing the problem.

If I get any enlightenment on what it is actually trying to do when it keeps dropping and reconnecting the Axim on the D-Link in WPA, I'll post that here too. I was afraid it was something unique to the Axim, but since WPA works fine on the Linksys, I don't think that is the case.

[mbloof]

Oh what fun....

The transcever on the Axim is a 'B' radio so it only can understand WPA - TKIP

Having your SSID broadcast during the testing phase makes life much easier for the Axim to connect.

Having a simple 8 char pass phrase while testing makes entering it simpler. (I use '12345678'. Change it once you have it working. (I use mixed UPPERlower1223!@#$, two of each in a random fashon is more than enough to block a dictionary attack)

I gave up on my Di-624 and I'm using a DELL 2300 with DD-WRT v23sp2 installed:

Wireless network mode: Mixed
WPA2 Preshaired key: Mixed
WPA Algorithms: TKIP
CTS Protection mode: AUTO (default is off)

The last setting helps 802.11B radios (like our Axim's) connect.

I hope this helps.

[Zoandar]

Having your SSID broadcast during the testing phase makes life much easier for the Axim to connect.

Yes, I found that to be the case as well.

Having a simple 8 char pass phrase while testing makes entering it simpler. (I use '12345678'. Change it once you have it working.

Interesting! that is exactly what I did during the ordeal. I guess that makes the case to change it when done even stronger. :-)

I gave up on my Di-624 and I'm using a DELL 2300 with DD-WRT v23sp2 installed:

Wireless network mode: Mixed
WPA2 Preshaired key: Mixed
WPA Algorithms: TKIP
CTS Protection mode: AUTO (default is off)

The last setting helps 802.11B radios (like our Axim's) connect.

If your CTS setting corresponds to the D-Link's "Cipher Type" setting, I have it set to "TKIP and AES". The other choices are for either of those individually.

The Axim has not had any trouble at all picking up the Linksys signal anywhere in the house. So I am happy with the way it worked out. Maybe now that the Linksys is no longer handling the incoming cable modem signal and distributing it to our LAN, it won't have to be powered on and off and reset periodically (the whole reason I got the D-Link). But I won't buy another Linksys product. So when it dies, I'll be back to square one again, unless D-Link can figure out the 20-second re-connection issue.

[ksong12]

Well, I have a Belkin, and the same problem exists, so it isn't D-Link specific.

But I don't think it is 802.11b specific either. I have a USB adapter that is 802.11g, and the exact same problem exists on my computer when I use that.

Oh, and the WirelessN standard does apparently support WEP. I've used it on my Belkin router. I have it set to b+g+n, and WEP with no problems. I'm not very happy with using WEP though, so I am unable to use my Axim right now.

[Zoandar]

Oh, and the Wireless N standard does apparently support WEP.

OOPS. Sorry, that was an error on my part. I meant to say that WEP encryption would not support the Wireless N transfer speed (at least, on the D-Link). When I was using WEP on it, before I added the Linksys back in as an AP, I had to settle for Mixed b and g.

802.11n speed was disabled because of my using WEP encryption.

Once I got the Linksys set up as an AP, and went back to WPA-PSK on the D-Link, I could turn on mixed mode b,g,n again.

I'll edit my previous post to reflect the above.

Based on the info just posted, maybe it is totally the Axim's problem, and the fact that the Axim manages to use WPA-PSK on a Linksys router might just be a fluke.

[mbloof]

But I won't buy another Linksys product. So when it dies, I'll be back to square one again, unless D-Link can figure out the 20-second re-connection issue.

Same here. Unless of course the Linksys provides a good platform for flashing DD-WRT or other alternative firmware.

As far as the D-Link goes, I had the Di-624 for years. It was one of D-Links longest running models. I'm kind of sad to see it go (gave it to a friend which it works fine with her laptop).

The 20 second thing is when the access point recalculates its encryption key.
Many versions of Dlink/Linksys firmware's calculation is different then what the Axim expects and the connection is lost as a result.

For those with Di-624's, I was able to get older versions of D-Link firmware to work with the Ax51v and the Oddisey client that Dell includes. The problem was, I could get the AX to work, then my laptops would not work. I could get the laptops to work, but the AX would not.

DD-WRT was the only way I was able to get all devices working at the same time.

It should go without saying that those that are having problems ALREADY have applied the Dell wireless patch to their Axims right?

Lastly, for those that have or are about ready to give up, there IS another option. The Axim does have TWO radios in it. If you leave one of your computers on most of the time, get yourself a 100meter Bluetooth dongle and setup your Axim/computer.

Interestingly enough, the bluetooth radio draws much less power than the WiFi radio and the 'speed' difference is not noticeable. Another added plus is that you can sync wirelessly with bluetooth where you can't with Wifi.