User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3 I cannot see or connect to my wireless network which is using WPA2 Personal from Network Manager in Fedora 10. I can see my neighbors access points, but they are all using WEP. I've got a HP 6710b, lspci shows that I'm using Intel 3935ABG Rev 02, lsmod show that I'm using iwl3945. This was working fine on Beta 1, but somewhere along the way an update has killed it, so I reverted back to Ubuntu 8.04. I've just checked on the live CD preview release and it's still the same. Reproducible: Always Steps to Reproduce: 1. Boot up 2. Open Network Manager 3. No WPA networks are available.
Created attachment 323327 [details] dmesg output
Created attachment 323328 [details] wpa_supplicant -dd output, while trying to connect to MOZ877W
Could you grab a new log with "-dddt" debug options? Just "-dd" isn't quite verbose enough.
Created attachment 323773 [details] wpa_supplicant with -ddtt
FYI, I've also tried a Ubuntu 8.10 live CD and I've got the same problem there, I can only see WEP enabled AP's
Hmm, is that log with "-dddt" (ie, 3 'd' and 1 't')? Still doesn't look quite verbose enough...
Created attachment 323778 [details] wpa_supplicant with -dddt Hopefully the correct attachment this time, sorry I didn't read your first request properly.
Yeah, the driver is simply unable to see the AP with scans. The Ap is supposed to be 'MOZ877W', right? Can you do the following? 1) /sbin/service NetworkManager stop 2) killall -TERM wpa_supplicant 3) ifconfig wlan0 up 4) iwlist wlan0 scan essid MOZ877W 5) after the results come in, check if MOZ877W shows up in the results 6) if not, wait 5 seconds, then do go back to step 4 again Basically, if the AP isn't showing up in the scan results from the driver, NM won't be able to see it either. Then it's either an AP bug, or a driver bug.
Hi Dan, I've done the above and I still can't see my AP (MOZ877W), I think the driver it's using is iwl3945 (from lsmod). On Ubuntu 8.04 where it is working, I can see my AP using iwlist, it's using iwl3945, but it's also got iwlwifi_mac80211 loaded, I don't know if this is relevant. I've also tried the first beta of F10 and it's not working there either, so my info above about it been broken by a update since the first beta is wrong. Does this bug need to be moved to another component ? Maurice
Yeah, over to kernel. Can you grab the 'iwlist wlan0 scan' output from Ubuntu (where you can see it) and paste it into this report? Feel free to xx-out the AP's MAC address if you like. It's useful to see what capabilities the AP is reporting. Do you know what brand and model the AP is?
Created attachment 323929 [details] iwlist output from Ubuntu 8.04 where I can see my AP
The AP is a Cisco 877W, I can connect to this using WPA on older versions of Fedora (F8 was the last one that I know of) Windows, Ubuntu 8.04 (but not 8.10).
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I've realised that this problem is down to the channel selection, the AP has chosen channel 13 automatically, I changed it to use Channel 1 (without realising) when adding a GuestWLAN and I can see it now. If configure the router to use channel 1 to 11 it's fine, if I choose 12 or 13 it doesn't work. As I can see the router using channel 12 and 13 in Ubuntu 8.04 and Windows XP, I would still consider it a bug, but I'm ok now so I've changed the priority to low. If you need more info then I'm happy to help. Maurice
Please add the following to /etc/modprobe.conf: options cfg80211 ieee80211_regdom="EU" Then reboot. Do you find that you can see channels 12 and 13 now?
Creating a modprobe.conf with options cfg80211 ieee80211_regdom="EU" allows me to see both channel 12 and 13. Maurice
Excellent! FWIW, we (or at least I) hope to have a more friendly alternative for configuring this available in F11.