Bugzilla – Bug 5390
Using wrong WEP key during inital setup gives misleading error
Last modified: 2007-11-06 09:11:27 UTC
Jive nightly for 9/5. Use out of box setup to connect to WEP64 network. Enter wrong key. Error is given as unable to obtain DHCP address.
Not sure what to do about this, the problem is you can't tell that a WEP key is wrong. The only error is that DHCP or other network traffic will fail.
In the case that that it's WEP and DHCP fails, use this string: Problem connecting to wireless network or getting an IP address. Go back to change your password or press go to try to reconnect.
Created attachment 2334 [details] Screenshot
Dean, I've attached a screenshot where this message should be displayed. I think it needs more than a different help message, maybe an additional menu item to "Edit WEP key" and a different title "Connection Problem"?
Crap, I thought I rewrote this, but it hasn't appeared in the bug.... Connection Problem Try again > Edit WEP Password > Use static IP > Couldn't connect to your network. This may be caused by an incorrect WEP password or other network problem such MAC filtering or missing DHCP server. The MAC address of this device is 00:04:20:12:34:56. That's a lot of text. Not sure if it will fit.
No chance, not after translation. Also note 'WEP Password' is technically incorrect, and we use 'wireless key' in the other strings. How about: Connection Problem Try again > Edit wireless key > Use self-assigned address > Use static IP > Couldn't connect to your network. This may be caused by an incorrect wireless key or other network problem such as a missing DHCP server.
I intentionally left out the auto assign choice. It's incredibly unlikely that it will ever be used except incorrectly. I added the MAC address because this is often the place where folks realize that they need to add their MAC address to their filter and it's stuck inside behind the battery. But if it won't fit, it won't fit.
So your saying that if your using WEP an auto assigned ip is not possible, so why include it for wpa too?
Hm, good point. I was just trying to reduce the number of choices to reduce confusion, but it's a hard problem. The _right_ way to use auto-ip is to fail over to it when DHCP fails automatically and transparently. The problem is that DHCP failing is more common than intentional auto-ip. The unfortunate thing is that when using ad hoc, you often _do_ want use auto-ip. The real problem here is that we can't distinguish the errors at the various levels (data link vs network). Would it be possible to arp the AP or something like that to see if we have basic connectivity. (Arp wouldn't work, I know, but there's got to be some way to know that we've got authenticated, no?) WPA is different, because we do know when we get authenticated there. So in the case that DHCP fails, auto-ip is a reasonable choice. So, the best solution would be to be able to positively know that WEP is working. Second choice would be to put the auto-ip choice back in.
Fixed in r808. Please review the text on the device, I think it's a little long for translation.
Could you paste the text here as well, for review?
Connection Problem Try again > Edit wireless key > Self-assign address > Use a static address > Couldn't connect to your network. This may be caused by an incorrect wireless key or other network problem such as MAC filtering or missing DHCP server.