Hi, I have a strange problem with a WiFi connection on a Freebox. The PC has a PCI WiFi card D-Link DWL-G520, it uses the ath5k driver. The card is recognized by the kernel 2.6.3x: cfg80211: Calling CRDA to update world regulatory domain ath5k 0000:05:04.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 ath5k 0000:05:04.0: registered as 'phy0' ath: EEPROM regdomain: 0x30 ath: EEPROM indicates we should expect a direct regpair map ath: Country alpha2 being used: AM ath: Regpair used: 0x30 phy0: Selected rate control algorithm 'minstrel' ath5k phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45) cfg80211: Calling CRDA for country: AM With Network-Manager (0.8.0.999-1), iwlist or iw we can see the Freebox (WEP for testing): $ sudo iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:11:22:33:44:55 Channel:6 Frequency:2.437 GHz (Channel 6) Quality=21/70 Signal level=-89 dBm Encryption key:on ESSID:"freebox_TOTO" 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=0000000bacdc167c Extra: Last beacon: 684ms ago IE: Unknown: 000E66726565626F785F525156485545 IE: Unknown: 010482848B96 IE: Unknown: 030106 IE: Unknown: 050400010000 IE: Unknown: 2A0104 IE: Unknown: 32080C1218243048606C $ sudo iwconfig wlan0 wlan0 IEEE 802.11bg ESSID:"freebox_TOTO" Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:MY-WEP-KEY Power Management:off And when I try to connect, I have a timeout: NetworkManager[1347]: <info> Activation (wlan0/wireless): connection 'Auto freebox_TOTO' has security, and secrets exist. No new secrets needed. NetworkManager[1347]: <info> Config: added 'ssid' value 'freebox_TOTO' NetworkManager[1347]: <info> Config: added 'scan_ssid' value '1' NetworkManager[1347]: <info> Config: added 'key_mgmt' value 'NONE' NetworkManager[1347]: <info> Config: added 'auth_alg' value 'OPEN' NetworkManager[1347]: <info> Config: added 'wep_key0' value '<omitted>' NetworkManager[1347]: <info> Config: added 'wep_tx_keyidx' value '0' NetworkManager[1347]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. NetworkManager[1347]: <info> Config: set interface ap_scan to 1 NetworkManager[1347]: <info> (wlan0): supplicant connection state: inactive -> scanning wpa_supplicant[1368]: Trying to associate with 00:11:22:33:44:55 (SSID='freebox_TOTO' freq=2437 MHz) NetworkManager[1347]: <info> (wlan0): supplicant connection state: scanning -> associating kernel: wlan0: direct probe to 00:11:22:33:44:55 (try 1) kernel: wlan0: direct probe to 00:11:22:33:44:55 (try 2) kernel: wlan0: direct probe to 00:11:22:33:44:55 (try 3) kernel: wlan0: direct probe to 00:11:22:33:44:55 timed out wpa_supplicant[1368]: Authentication with 00:11:22:33:44:55 timed out. NetworkManager[1347]: <info> (wlan0): supplicant connection state: associating -> disconnected NetworkManager[1347]: <info> (wlan0): supplicant connection state: disconnected -> scanning wpa_supplicant[1368]: Trying to associate with 00:11:22:33:44:55 (SSID='freebox_TOTO' freq=2437 MHz) NetworkManager[1347]: <info> (wlan0): supplicant connection state: scanning -> associating kernel: wlan0: direct probe to 00:11:22:33:44:55 (try 1) kernel: wlan0: direct probe to 00:11:22:33:44:55 (try 2) kernel: wlan0: direct probe to 00:11:22:33:44:55 (try 3) kernel: wlan0: direct probe to 00:11:22:33:44:55 timed out I tried with a vanilla kernel 2.6.34 recompile without module and with an Debian image package linux-image-2.6.35, I removed the filter rules (netfilter), always the same timeout ... On the PC with Network-Manager (0.8.0.999-1) I can connect to Ethernet, I also tried a 3G dongle successfully. The Freebox works because I can connect to with WiFi from a EeePC which also uses a Debian with LXDE and Network-Manager (0.8.0.999-1). The lspci -vnn : 05:04.0 Ethernet controller [0200]: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter [168c:0013] (rev 01) Subsystem: D-Link System Inc D-Link AirPlus DWL-G520 Wireless PCI Adapter(rev.B) [1186:3a13] Flags: bus master, medium devsel, latency 168, IRQ 17 Memory at ff7e0000 (32-bit, non-prefetchable) [size=64K] Capabilities: [44] Power Management version 2 Kernel driver in use: ath5k What is causing this kernel timeout? Regards.
Are you able to connect to other access points with the device in question? Could you use wireshark on another box (e.g. the EeePC you mentioned) with it's wireless device in monitor mode to capture the association attempt and post the trace here?
(In reply to comment #1) > Are you able to connect to other access points with the device in question? > > Could you use wireshark on another box (e.g. the EeePC you mentioned) with > it's > wireless device in monitor mode to capture the association attempt and post > the > trace here? Hi, Thank you for responding. Unfortunately, I am not able to try another access point. I put in attachment the capture of the association attempt. Regards.
Created attachment 27911 [details] Wireshark capture
Just to be clear, that capture was done from a different box (i.e. not the source of the messages in the original comment in this report)? Assuming that is true, the capture shows that the probe requests are going on the air, but the AP is not responding to them. It does seem odd that the probe requests are not specifying an SSID. Can you switch to WEP (or turn-off encryption) on the AP and establish a connection without using NetworkManager and wpa_supplicant?
(In reply to comment #4) > Just to be clear, that capture was done from a different box (i.e. not the > source of the messages in the original comment in this report)? Hi, Yes, the capture was made on the Eeepc. It connects easily to the AP with Wifi and use the same versions of NetworkManager and wpa-supplicant as those installed on the PC. > Assuming that is true, the capture shows that the probe requests are going on > the air, but the AP is not responding to them. It does seem odd that the > probe > requests are not specifying an SSID. The PC and the EeePC is one beside the other. > Can you switch to WEP (or turn-off encryption) on the AP and establish a > connection without using NetworkManager and wpa_supplicant? AP (freebox) does not allow to disable the encryption, the minimum is WEP. For the previous capture the encryption was WEP. Below is the output of commands iwconfig and dhclient on the PC: $ sudo iwconfig wlan0 wlan0 IEEE 802.11bg ESSID:"freebox_RQVHUE" Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:XXXX-XXXX-XX Power Management:off $ sudo ifconfig wlan0 up ; sudo dhclient -v wlan0 Internet Systems Consortium DHCP Client 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/wlan0/00:1c:f0:9d:3e:f2 Sending on LPF/wlan0/00:1c:f0:9d:3e:f2 Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6 No DHCPOFFERS received. No working leases in persistent database - sleeping. I put in attachment the capture from Eeepc of the association attempt. Regards.
Created attachment 27971 [details] Wireshark capture from Eeepc
Do you still have the problem with latest wpa_supplicant/kernel ?
Closing due to lack of response...