Bug 11847 - Failed to get wireless working
: Failed to get wireless working
Status: RESOLVED DUPLICATE of bug 11840
Product: SB Touch
Classification: Unclassified
Component: Networking
: unspecified
: Other Other
: -- normal (vote)
: 8.0.0
Assigned To: Felix Mueller
:
Depends on: 11840
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-18 07:50 UTC by andrew
Modified: 2009-09-08 09:13 UTC (History)
0 users

See Also:
Category: ---


Attachments
/var/log/messages (137.00 KB, text/plain)
2009-04-18 07:50 UTC, andrew
Details

Note You need to log in before you can comment on or make changes to this bug.
Description andrew 2009-04-18 07:50:49 UTC
Created attachment 5142 [details]
/var/log/messages

Anybody good at interpreting logs about wireless setup? I cannot get my fab4 to work on my wlan. Attached will be /var/log/messages. I added -dd to wpa_supplicant to try to get more useful info.

My dhcp server sees no DHCP requests when fab4 tries to use wireless, but wpa_supplicant seems happy. The networking is setup such that the ethernet cable from fab4 goes into the 4port switch on my linksys WRT54GL AP. So the AP is seeing the same MAC address on both the wired and wireless side. This might make it a bit unhappy?

I double checked the WEP key, it is the same as my laptop is using:

eth1      IEEE 802.11g  ESSID:"(AL)squared"  
          Mode:Managed  Frequency:2.422 GHz  Access Point: 00:21:29:99:11:AE   
          Bit Rate:54 Mb/s   Tx-Power=20 dBm   Sensitivity=8/0  
          Retry limit:7   RTS thr:off   Fragment thr:off
          Encryption key:2C7C-573B-718E-1AE6-3E3B-D1EF-92   Security mode:open
          Power Management:off
          Link Quality=93/100  Signal level=-35 dBm  Noise level=-92 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

So i'm stuck scratching my head as to what is wrong.
Comment 1 Felix Mueller 2009-04-18 13:02:01 UTC
Unfortunately WEP doesn't give any indication of what might be the issue when it doesn't connect. Also a WEP connection might look ok even if the WEP key is wrong.

Could you try without ethernet connected just to rule that out? (I don't think that is the issue though as I do that all the time.)

Also would it be possible to temporarily remove the WEP key altogether from your AP just to see if it's a general AP issue?

Do you have MAC filtering on your AP turned on by any chance?
Comment 2 Felix Mueller 2009-04-18 13:09:05 UTC
Maybe you are also running into a similar issue as in bug 11840?

Could you therefore also try with a changed SSID, i.e. without the brackets? '(' and ')'?
Comment 3 Felix Mueller 2009-04-21 05:35:08 UTC
The issue are special characters in SSID, i.e. "'" or "(" etc.
Comment 4 Felix Mueller 2009-04-21 05:47:41 UTC

*** This bug has been marked as a duplicate of bug 11840 ***