Description of problem: Version-Release number of selected component (if applicable): 3.1.0-0.rc9.git0.0.fc16.i686.PAE How reproducible: Steps to Reproduce: 1. try to connect AP with PEAP, inner authentication MSCHAPv2 2. 3. Actual results: cannot connect Expected results: connect Additional info: lspci 00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02) 00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 02) 00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02) 02:00.0 Network controller: Intel Corporation WiFi Link 5100 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
Please fix this bug. Now I can never connect to PEAP
Did this work in previous kernels? If so, which kernels? Is there an error produced in dmesg or from NetworkManager in /var/log/messages?
Yes it worked in the previous kernel in Fedora 16. I think previous kernel should be 2.6.40. It does not work when I upgrade to fedora 16. Note that the wifi works for WPA & WPA2 personal. I enclose the message file. Please let me know if you need more information
Sorry, previous message has a typo: Yes it worked in the previous kernel in Fedora 15. I think previous kernel should be 2.6.40. It does not work when I upgrade to fedora 16. Note that the wifi works for WPA & WPA2 personal. I enclose the message file. Please let me know if you need more information
Created attachment 529912 [details] error message in /var/log/messages error message in /var/log/messages
Since regression happen between F-15 and F-16 I'm not sure if this is kernel or NetworkManager or maybe an wpa_supplicant issue. Or this could be a kernel issue that happens only with newer NetworkManager/wpa_supplicant. I have to install F-16 and see how it works here (I do not have MSCHAPv2 inner authentification APs, but I can test EAP with GTC). On the mine time can you try downgrade NetworkManager to 0.8, i.e: install: http://koji.fedoraproject.org/koji/buildinfo?buildID=254463 And older F-15 kernel i.e: http://koji.fedoraproject.org/koji/buildinfo?buildID=270368 Downgrading kernel, should be easy by "rpm --force". Downgrading NetwormManager can be problematic, since it depends on external liberalies, you might try to use "yum downgrade"
I've down-grade to 2.6.40. It still does not work. Probably it is the network manager's problem. Would you create a new bug entry? Thank you.
This could be related with channel switching problems we had currently in mac80211. Please try this kernel, which include some channel switching fixes, and tell us if that helps: http://koji.fedoraproject.org/koji/taskinfo?taskID=3482880
It still does not work with this old kernel
The problem still persist in kernel 3.2.2-1. Would you try to fix it? Thank you
*** Bug 751588 has been marked as a duplicate of this bug. ***
I did not try to reproduce problem with MSCHAPv2 inner authentication (I don't know if I have AP, which I could configure in such setup). With GTC things work well here. Is possible that you could build vanilla kernel, or compat-wireless packages (on older kernel) and narrow between which two versions problem start to happen (end eventually continue with bisection)?
We need your assistance to solve this problem. Please run F-15 liveCD with 2.6.38 kernel, and check if that works. If not run F-14 liveCD and check if that works. Install version that works. Then install compat-wireless package and perform bisection using it, this is described here: https://bugzilla.redhat.com/show_bug.cgi?id=716988#c14 And then tell us which version (date) of compat-wireless works, and which not, hence we could compare them to find where the problem can be.
I know that it works in 2.6.40. However, I don't have the kernel. Would you give me a link? I can just install kernel to try. My netbook does not have optical drive.
Here is very first F-15 2.6.40 kernel: http://koji.fedoraproject.org/koji/buildinfo?buildID=256252 and in just in case it will not work 2.6.38: http://koji.fedoraproject.org/koji/buildinfo?buildID=251810 > My netbook does not have optical drive. You can run live CD image from usb pendrive or mmc card (http://fedoraproject.org/wiki/How_to_create_and_use_Live_USB ), but it does not matter, since you can find latest working kernel on hard drive.
Weird, Neither kernel works now. (38 and 40)
It possible that something else changed, i.e. the behaviour of NetworkManager or firmware in the AP, hence we are triggering this bug now, and not before. Ok, let's try with liveCD with old kernel and old NetworkManager/wpa_supplicant, can you find some old software that works?
Oh, please also check these swcrypto=1, swcrypt50=1 options on older kernel.
Jiri, is possible that 1320680376.926836: nl80211: MLME event 37; timeout with 00:23:eb:3a:0f:90 1320680376.926929: SME: Authentication timed out are because of wrong password, or with wrong password we will see different messages?
swcrypto=1, swcrypt50=1? Which shall I set? Which file?
modprobe -r iwlagn modprobe iwlagn swcrypto50=1 See modinfo iwlagn which option is appropriate.
with modprobe -r iwlagn modprobe iwlagn swcrypto50=1 or modprobe iwlagn swcrypto=1 Neither kernel works
Ok, so just try to find live CD image (maybe F-14 or F-15 with downgraded NetworkManager/wpa_supplicant) that works, so we will have some starting point.
Re: https://bugzilla.redhat.com/show_bug.cgi?id=716988#c20 http://mirrors.fedoraproject.org/publiclist/
Fedora 14 and 15 do not work using live CD.
You told in comment 3 that it worked in the past. So what changed? AP configuration? Are you sure you are providing proper password?
Yes. I am using fedora DVD version. but not the live CD. I am sure the password is correct since I can connect with my USB wifi card using the same setting
Yes. I was using fedora DVD version. but not the live CD. I am sure the password is correct since I can connect with my USB wifi card using the same setting
It does not matter if it is DVD or CD. Maybe you used other module option in the past, i.e. 11n_disable=1 or bt_coex_active=1 (this is iwl-core module parameter). Can you connect to any other AP using iwlagn?
I can connect to other AP (WPA personal) using iwlagn. Only PEAP does not work
Ok, configure syslog as described here: > https://fedoraproject.org/wiki/DebugWireless#Configure_syslog_to_log_kernel_debug_messages then log debug messages like in example: $ modprobe -r iwlagn $ echo > /var/log/kernel $ modprobe iwlagn debug=0x47ffffff Try to connect to PEAP AP. $ modprobe -r iwlagn Compress /var/log/kernel file and send it to my email address.
After doing that, /var/log/kernel is empty. Are you sure your instruction is correct?
Do you see verbose messages in dmesg? If so, perhaps you did not configure /etc/rsyslog.conf or did not restart rsyslog? Perhaps it has to be restarted using systemctl i.e: systemctl restart rsyslog.service .
I am so confused. i can open a VNC or ssh and give your IP (public IP). You can login to make it. Do you have gtalk account? Please add me and we can talk online about the bug.
I analyzed the logs from lionghostshop, but unfortunately do not find anything really suspicious. Only thing that looks >[ 1023.039413] iwlwifi 0000:02:00.0: I iwlagn_rx_statistics Statistics notification received (480 bytes). >[ 1023.039432] iwlwifi 0000:02:00.0: I iwlagn_good_plcp_health plcp health threshold 100 delta 135 msecs 105 >[ 1023.039444] iwlwifi 0000:02:00.0: I iwl_force_reset perform force reset (0) >[ 1023.039455] iwlwifi 0000:02:00.0: I iwl_force_rf_reset perform radio reset. and then: > [ 1023.352811] iwlwifi 0000:02:00.0: I iwlagn_good_plcp_health plcp health threshold 100 delta 249 msecs 105 > [ 1023.352823] iwlwifi 0000:02:00.0: I iwl_force_reset force reset rejected What mean that plcp (radio phy) has problem to decode frames. I'm not sure how this could be fixed. Perhaps disabling plcp_check could help? modprobe -r iwlwifi modprobe iwlwifi plcp_check=0
I tried. Still cannot connect. Quite weird
I saw you also opened a bug report for ath9k. In comment https://bugzilla.redhat.com/show_bug.cgi?id=708713#c2 you wrote that the issue is only reproducible in some places. Can you check if you can associate with PEAP AP on some other location (also on F-14 live CD) ?
So how this looks on different locations, is iwlwifi device capable to connect to that PEAP AP when there are good radio conditions?
I will try it in other location. However, I think the signal in my dorm is good.
Let's try to compare iwlwifi with usb dongle you have, which is able to associate PEAP AP. Please do "iwlist wlanX scan" on iwlwifi an usb dongle and attach outputs here.
Please write a script file to dump the output. I will execute it as root.
It's simple. First check what wlanX devices are available by doing iwconfig. Then find-out what driver is assigned to device by doing ethtool -i wlanX . Then if wlan0 is iwlwifi device and wlan1 is usb wireless device do iwlist wlan0 scan > scan_iwlwifi.txt iwlist wlan1 scan > scan_usb.txt and attach scan*.txt files here
Can I do it using my another laptop, which can connect to the wifi?
I need scanning information from laptop (iwlwifi device) that is not capable to connect. You can give me scanning information from other laptop for compare (instead of usb device scanning results).
This one is the laptop that works. [root@localhost shm]# ethtool -i wlan0 driver: ath5k version: 3.2.7-1.fc16.x86_64 firmware-version: N/A bus-info: 0000:03:00.0 supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no scan_iwlwifi.txt ------------------------ wlan0 Scan completed : Cell 01 - Address: 00:23:EB:3A:0F:90 Channel:6 Frequency:2.437 GHz (Channel 6) Quality=51/70 Signal level=-59 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=000014363596501c Extra: Last beacon: 379ms ago IE: Unknown: 000A734D6F62696C654E6574 IE: Unknown: 0104B048606C IE: Unknown: 030106 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B050200008D5B IE: Unknown: 2A0100 IE: Unknown: 2D1A2C181BFFFF000000000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : 802.1x IE: Unknown: 3D1606000700000000000000000000000000000000000000 IE: Unknown: 9606004096001400 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961401 Cell 02 - Address: 00:23:89:71:E0:DA Channel:1 Frequency:2.412 GHz (Channel 1) Quality=38/70 Signal level=-72 dBm Encryption key:on ESSID:"Fedora Linux Wifi" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=00000232c5c04177 Extra: Last beacon: 146ms ago IE: Unknown: 00114665646F7261204C696E75782057696669 IE: Unknown: 010482848B96 IE: Unknown: 030101 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: Unknown: 0406000200000000 IE: Unknown: 2A0100 IE: Unknown: 32088C129824B048606C Cell 03 - Address: 00:23:EB:3A:0D:90 Channel:6 Frequency:2.437 GHz (Channel 6) Quality=34/70 Signal level=-76 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=00000e1ff201781c Extra: Last beacon: 373ms ago IE: Unknown: 000A734D6F62696C654E6574 IE: Unknown: 0104B048606C IE: Unknown: 030106 IE: Unknown: 050400010000 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B050000038D5B IE: Unknown: 2A0100 IE: Unknown: 2D1A2C181BFFFF000000000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : 802.1x IE: Unknown: 3D1606000700000000000000000000000000000000000000 IE: Unknown: 9606004096001400 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961401 Cell 04 - Address: 00:23:EB:3A:10:C0 Channel:6 Frequency:2.437 GHz (Channel 6) Quality=30/70 Signal level=-80 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=000014362254d81d Extra: Last beacon: 369ms ago IE: Unknown: 000A734D6F62696C654E6574 IE: Unknown: 0104B048606C IE: Unknown: 030106 IE: Unknown: 050400010000 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B050200188D5B IE: Unknown: 2A0100 IE: Unknown: 2D1A2C181BFFFF000000000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : 802.1x IE: Unknown: 3D1606000500000000000000000000000000000000000000 IE: Unknown: 9606004096001400 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961401 Cell 05 - Address: 00:23:EB:3A:81:20 Channel:6 Frequency:2.437 GHz (Channel 6) Quality=34/70 Signal level=-76 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=000014363eb3901c Extra: Last beacon: 403ms ago IE: Unknown: 000A734D6F62696C654E6574 IE: Unknown: 0104B048606C IE: Unknown: 030106 IE: Unknown: 050400010000 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B050000058D5B IE: Unknown: 2A0100 IE: Unknown: 2D1A2C181BFFFF000000000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : 802.1x IE: Unknown: 3D1606080400000000000000000000000000000000000000 IE: Unknown: 9606004096001400 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961401 Cell 06 - Address: 00:23:EB:0A:CC:00 Channel:11 Frequency:2.462 GHz (Channel 11) Quality=25/70 Signal level=-85 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=00001436368bc01d Extra: Last beacon: 648ms ago IE: Unknown: 000A734D6F62696C654E6574 IE: Unknown: 0104B048606C IE: Unknown: 03010B IE: Unknown: 050400010000 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B050100008D5B IE: Unknown: 2A0100 IE: Unknown: 2D1A2C181BFFFF000000000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : 802.1x IE: Unknown: 3D160B000500000000000000000000000000000000000000 IE: Unknown: 9606004096001400 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961401 Cell 07 - Address: 00:23:EB:3A:9A:80 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=24/70 Signal level=-86 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=000014363fa9001c Extra: Last beacon: 2847ms ago IE: Unknown: 000A734D6F62696C654E6574 IE: Unknown: 0104B048606C IE: Unknown: 030101 IE: Unknown: 050700010000000000 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B0506000D8D5B IE: Unknown: 2A0100 IE: Unknown: 2D1A2C181BFFFF000000000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : 802.1x IE: Unknown: 3D1601000700000000000000000000000000000000000000 IE: Unknown: 9606004096001400 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961401 Cell 08 - Address: 00:23:EB:3A:8A:D0 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=36/70 Signal level=-74 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=000014363a96181c Extra: Last beacon: 2803ms ago IE: Unknown: 000A734D6F62696C654E6574 IE: Unknown: 0104B048606C IE: Unknown: 030101 IE: Unknown: 050700010000000000 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B050100068D5B IE: Unknown: 2A0100 IE: Unknown: 2D1A2C181BFFFF000000000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : 802.1x IE: Unknown: 3D1601000700000000000000000000000000000000000000 IE: Unknown: 9606004096001400 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961401 Cell 09 - Address: 00:23:EB:3A:81:C0 Channel:11 Frequency:2.462 GHz (Channel 11) Quality=26/70 Signal level=-84 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=000014363b0c08fb Extra: Last beacon: 671ms ago
This one is the laptop that does not work. [root@localhost memory_tmp]# ethtool -i wlan0 driver: iwlwifi version: 3.2.7-1.fc16.i686.PAE firmware-version: 8.83.5.1 build 33692 bus-info: 0000:02:00.0 supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no ---------------------- wlan0 Scan completed : Cell 01 - Address: 00:23:89:71:E0:DA Channel:1 Frequency:2.412 GHz (Channel 1) Quality=70/70 Signal level=-16 dBm Encryption key:on ESSID:"Fedora Linux Wifi" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=00000232e3c25d56 Extra: Last beacon: 3ms ago IE: Unknown: 00114665646F7261204C696E75782057696669 IE: Unknown: 010482848B96 IE: Unknown: 030101 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: Unknown: 0406000200000000 IE: Unknown: 2A0100 IE: Unknown: 32088C129824B048606C Cell 02 - Address: 00:23:EB:3A:0F:9F Channel:36 Frequency:5.18 GHz (Channel 36) Quality=35/70 Signal level=-75 dBm Encryption key:on ESSID:"sMobileNet"
On working laptop, what shows iwconfig ?
On working laptop, what shows iwconfig ? Answer: lo no wireless extensions. vboxnet0 no wireless extensions. wlan0 IEEE 802.11bg ESSID:"sMobileNet" Mode:Managed Frequency:2.437 GHz Access Point: 00:23:EB:3A:0F:90 Bit Rate=54 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=55/70 Signal level=-55 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:45 Invalid misc:18 Missed beacon:0 eth0 no wireless extensions.
00:23:EB:3A:0F:90 is the AP which has signal quality "Quality=51/70 Signal level=-59 dBm" all others sMobileNet APs seen by ath5k device have worse signal. iwlwifi device see only 00:23:EB:3A:0F:9F with "Quality=35/70 Signal level=-75 dBm", that simply too week signal to make wireless network work well. I'm not able to say if with such bad conditions iwlwifi device should work or not. Perhaps there is something wrong with sensitivity/antennas code in the driver, but honestly I do not think this is a bug, and even if it is, this is nothing I can fix (programming iwlwifi sensitivity code is back magic, Intel could help you but I also doubt so). So how to solve this problem? Since iwlwifi device is internal you can not connect better antennas to it. Perhaps you can ask your wireless administrator to increase tx power on 00:23:EB:3A:0F:90 AP. You can also try to increase tx power of iwlwifi device by "iwconfig wlan0 txpower nn" . And at last, not use that laptop in locations where is bad wifi signal. If you will connect usb dongle (without antenna) and on the same location dongle will be able to connect and iwlwifi device not, hence you can suspect that there is something wrong with iwlwifi device, fill bug report on http://bugzilla.intellinuxwireless.org/ I'm closing this bug report with CANTFIX resolution.
I think the driver contains bug since I can connect to AP using my cell phone and my another notebook in the same location. Besides, the wifi still does not work when I move the netbook very close to the access point.
Does iwlist wlan0 scan show the signal is ok near that AP ? Perhaps we do not try to associate with the right AP with good signal. That would be strange. Please provide iwlist wlan0 scan output and dmesg output without any debug options) when laptop is near AP.
The scan result near AP. The distance is about 1.5 meter. How to get result from dmsg? wlan0 Scan completed : Cell 01 - Address: 00:23:EB:3A:8A:D0 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=51/70 Signal level=-59 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=0000143aee8a381c Extra: Last beacon: 5757ms ago IE: Unknown: 000A734D6F62696C654E6574 IE: Unknown: 0104B048606C IE: Unknown: 030101 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B0503000B8D5B IE: Unknown: 2A0100 IE: Unknown: 2D1A2C181BFFFF000000000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : 802.1x IE: Unknown: 3D1601000700000000000000000000000000000000000000 IE: Unknown: 9606004096001400 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961401 Cell 02 - Address: 00:23:89:71:E0:DA Channel:1 Frequency:2.412 GHz (Channel 1) Quality=61/70 Signal level=-49 dBm Encryption key:on ESSID:"Fedora Linux Wifi" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=00000237798b186f Extra: Last beacon: 68ms ago IE: Unknown: 00114665646F7261204C696E75782057696669 IE: Unknown: 010482848B96 IE: Unknown: 030101 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: Unknown: 0406000200000000 IE: Unknown: 2A0100 IE: Unknown: 32088C129824B048606C Cell 03 - Address: 00:23:EB:3A:8B:90 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=30/70 Signal level=-80 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=0000143af195901c Extra: Last beacon: 5757ms ago IE: Unknown: 000A734D6F62696C654E6574 IE: Unknown: 0104B048606C IE: Unknown: 030101 IE: Unknown: 050400010000 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B050100348D5B IE: Unknown: 2A0100 IE: Unknown: 2D1A2C181BFFFF000000000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : 802.1x IE: Unknown: 3D1601000700000000000000000000000000000000000000 IE: Unknown: 9606004096001400 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961401 Cell 04 - Address: 00:23:EB:3A:81:20 Channel:6 Frequency:2.437 GHz (Channel 6) Quality=33/70 Signal level=-77 dBm Encryption key:on ESSID:"sMobileNet" Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=0000143af287d01c Extra: Last beacon: 5504ms ago IE: Unknown: 000A734D6F62696C654E6574 IE: Unknown: 0104B048606C IE: Unknown: 030106 IE: Unknown: 050400010000 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B050100068D5B IE: Unknown: 2A0100 IE: Unknown: 2D1A2C181BFFFF000000000000000000000000000000000000000000 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : 802.1x IE: Unknown: 3D1606080400000000000000000000000000000000000000 IE: Unknown: 9606004096001400 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : 802.1x IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961401 Cell 05 - Address: 28:93:FE:F4:04:04 Channel:11 Frequency:2.462 GHz (Channel 11) Quality=27/70 Signal level=-83 dBm Encryption key:off ESSID:"PCCW" Bit Rates:9 Mb/s; 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=0000078eab3e82ac Extra: Last beacon: 5328ms ago IE: Unknown: 000450434357 IE: Unknown: 0108129618243048606C IE: Unknown: 03010B IE: Unknown: 050400010000 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B050A006F8D5B IE: Unknown: 2A0100 IE: Unknown: 9606004096001C00 IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961400 Cell 06 - Address: 28:93:FE:F4:04:02 Channel:11 Frequency:2.462 GHz (Channel 11) Quality=28/70 Signal level=-82 dBm Encryption key:off ESSID:"Y5ZONE" Bit Rates:9 Mb/s; 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=0000078eab3e831c Extra: Last beacon: 5315ms ago IE: Unknown: 000659355A4F4E45 IE: Unknown: 0108129618243048606C IE: Unknown: 03010B IE: Unknown: 050400010000 IE: Unknown: 0706484B20010B1E IE: Unknown: 0B050A006F8D5B IE: Unknown: 2A0100 IE: Unknown: 9606004096001C00 IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD06004096010104 IE: Unknown: DD050040960305 IE: Unknown: DD050040960B09 IE: Unknown: DD050040961400 Cell 07 - Address: 00:23:EB:3A:0F:9F Channel:36 Frequency:5.18 GHz (Channel 36) Quality=64/70 Signal level=-46 dBm Encryption key:on ESSID:"sMobileNet"
any clue?
Please attach dmesg output when AP is near laptop, and failed to associate. Please do not that in comment since dmesg output can be big, just use "Add an attachment" dmesg > dmesg.txt
What shall I do when I get close to AP? Connect to wifi or do a scan?
Be close to AP and try to connect with it, then do dmesg.
Created attachment 566322 [details] dmesg >msg.txt I run this command as a normal user.
We can associate with AP with good signal, but we deauthenticating shortly after for local reason, probably because of DHCP failure (/var/log/messages should show exact reason of that). > [ 3634.522809] wlan0: authenticate with 00:23:eb:3a:8a:d0 (try 1) > [ 3634.524387] wlan0: authenticated > [ 3634.530076] wlan0: associate with 00:23:eb:3a:8a:d0 (try 1) > [ 3634.534858] wlan0: RX ReassocResp from 00:23:eb:3a:8a:d0 (capab=0x431 status=0 aid=3) > [ 3634.534876] wlan0: associated > [ 3634.534893] wlan0: moving STA 00:23:eb:3a:8a:d0 to state 1 > [ 3634.534905] wlan0: moving STA 00:23:eb:3a:8a:d0 to state 2 > [ 3634.543900] cfg80211: Calling CRDA for country: HK > [ 3634.561746] cfg80211: Regulatory domain changed to country: HK > [ 3634.561755] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) > [ 3634.561765] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) > [ 3634.561774] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) > [ 3634.561783] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > [ 3634.561792] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > [ 3634.561801] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) > [ 3657.034240] wlan0: deauthenticating from 00:23:eb:3a:8a:d0 by local choice (reason=3) Then we try to associate with APs with bad signal, but that is not possible we can not receive a good frame from it. [12747.523456] wlan0: direct probe to 00:23:eb:3a:0f:90 (try 1/3) [12747.723163] wlan0: direct probe to 00:23:eb:3a:0f:90 (try 2/3) [12747.923176] wlan0: direct probe to 00:23:eb:3a:0f:90 (try 3/3) [12748.123069] wlan0: direct probe to 00:23:eb:3a:0f:90 timed out Please attach output of "tail -n 1000 /var/log/messages > messages.txt" (as root), I would like to see reason of 00:23:eb:3a:8a:d0 deautentificate.
Created attachment 566333 [details] tail -n 10000 /var/log/messages >msg tail -n 10000 /var/log/messages >msg
any update?
I do not see the reason of failure in the logs. NetworkManager does not print AP mac address so I'm not able to recognize proper failures in logs. Can you try all the things we did before like swcrypto=1 and other module options, fedora 14 live cd etc.., while being near to AP and see if some of that make things works? Also control during testing that we are trying to associate with best signal AP (by observing iwscan wlan0 list and dmesg).
Created attachment 566800 [details] The dialog with swcrypto=1 in fedora 14 live I found that I enable swcrypto=1 and then it displays two smobilenet APs, which I want to connect. One with very good signal. However, it shows a dialog in the attachment when I try to connect to it. It should be PEAP instead of the authentication method shown in the attachment. If I connect to the one with weaker signal. It shows me the PEAP configuration dialog
Created attachment 566802 [details] msg from fedora 14 live
(In reply to comment #62) > attachment when I try to connect to it. It should be PEAP instead of the > authentication method shown in the attachment. If I connect to the one with > weaker signal. It shows me the PEAP configuration dialog Looks like some old networks with wrong parsed baecon. Click right mouse button on NetworkManager icon then Edit connections -> Wireless and delete all sMobileNetwork. Exit from menu, then rescan by iwlist wlan0 scan, properly detected networks should show up in the Network Manager.
The live fedora 14 is new. I just install it this afternoon. It cannot remember anything.
That problem may happen when cryptography information in beacon is wrong, once such beacon is catches by NetworkManager you will see that network there. Perhaps also restarting NetworkManager can help in that case, but I'm not sure you might try that as well /etc/init.d/NetworkManager restart .
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
No luck. Still not working.
The problem still persists in Fedora 17,
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
It's still not working
I'm sorry, but I do not see any chance to fix this bug ...
hi guys， Maybe something is wrong in NM, the TIMEOUT happened when sending authentication request, as the same time NM sends scan request, so authentication request got TIMEOUT.
In my case, NM change the MAC of wifi interface, cause wpa_supplicant confused.