maemo.org Bugzilla – Bug 10885
Cannot Connect to WPA2 (Linksys WRT54G2 Wireless Router)
Last modified: 2010-09-27 13:38:10 UTC
You need to
before you can comment on or make changes to this bug.
EXACT STEPS LEADING TO PROBLEM:
1. I tried to connect to my linksys wrt54g2 wireless router using Wi-Fi
2. I tried both the Pin Method and pressing Done after pressing the access
button in my router.
3. I tried the other way around by creating new internet connection in the
phone settings, and making the right configuration like setting WPA2-Personal
and entering the shared key.
N900 should connect to the internet through linksys wrt54g2 wireless router.
Network connection error. YES
Try again? NO
EXTRA SOFTWARE INSTALLED:
I can only encounter this problem with my linksys wrt54g2 with my N900... other
devices like desktop PC, laptops (win and mac), netbook (xp), and PSP can
connect without problems.
Also, my N900 can connect without a problem with the wireless routers I have in
my office (both BUFFALO and AZTECH routers).
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199)
What Firmware version does the router have? Is it the latest?
Does setting Power Saving to "Off" help? (Settings > Internet Connections >
Connections > Edit > Next > Next > Next > Advanced > Other > Power saving)
If you are able to reproduce this, can you please provide a syslog (see
http://wiki.maemo.org/Documentation/devtools/maemo5#Installation for more
information) and then enable the wlancond debugging with the two commands
gconftool-2 --set --type int
and after this if you are able to reproduce this attach the /var/log/syslog
from the device here.
If you are not used to Linux, after creating the syslog file you can copy the
syslog file to those folders that are visible in the Maemo File Manager by:
* Starting X Terminal
* cp /var/log/syslog /home/user/MyDocs/.documents/
After that you can find the file in the Maemo File Manager by going to Nokia
N900 > Documents.
Unfortunately, without more information, as requested in one of the last
comments, we are unable to do anything more about this report. Until more
information is available, I'm resolving the report as INVALID.
Please feel free to reopen this bug if you can provide the information asked
for, or if you can still reproduce this.