Bug 16781
Summary: | Timeout with a PCI WiFi card D-Link DWL-G520 | ||
---|---|---|---|
Product: | Drivers | Reporter: | Frederic MASSOT (frederic) |
Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
Status: | CLOSED INSUFFICIENT_DATA | ||
Severity: | normal | CC: | linville, me, mickflemm |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.34, 2.6.35 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
Wireshark capture
Wireshark capture from Eeepc |
Description
Frederic MASSOT
2010-08-22 15:40:19 UTC
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... |