Bug 453209
| Summary: | Network Manager fails to properly set essid/? and fails to connect. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Douglas Kilpatrick <kilpatds> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | CC: | dcbw, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-02-17 12:06:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Can you attach some logs from /var/log/messages showing a connection attempt? I need to see what NM is doing and why it might be falling back to usenix. There have been recent issues with wpa_supplicant, mac80211-based drivers, and A-band access points that may affect this issue in the kernel as well. "Falling back to usenix" isn't quite right. It had not yet given up on associating with a-only, but iwconfig in a terminal window showed essid "usenix" instead of the expected usenix-803.11a-only. The logs say it set ssid, not esid. Is this just confusion on my part? (Well, aside from it not associating to a perfectly good network) This looks representative: Jun 27 15:49:32 localhost NetworkManager: <info> Activation (wlan0) starting connection 'Auto usenix-802.11a-only' Jun 27 15:49:32 localhost NetworkManager: <info> (wlan0): device state change: 3 -> 4 Jun 27 15:49:32 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jun 27 15:49:32 localhost NetworkManager: <info> (wlan0): supplicant connection state change: 3 -> 0 Jun 27 15:49:32 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jun 27 15:49:32 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jun 27 15:49:32 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jun 27 15:49:32 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jun 27 15:49:32 localhost NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jun 27 15:49:32 localhost NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto usenix-802.11a-only' requires no security. No secrets needed. Jun 27 15:49:32 localhost NetworkManager: <info> Config: added 'ssid' value 'usenix-802.11a-only' Jun 27 15:49:32 localhost NetworkManager: <info> Config: added 'scan_ssid' value '1' Jun 27 15:49:32 localhost NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' Jun 27 15:49:32 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jun 27 15:49:32 localhost NetworkManager: <info> Config: set interface ap_scan to 1 Jun 27 15:49:32 localhost NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2 Jun 27 15:49:34 localhost NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 3 Jun 27 15:49:57 localhost NetworkManager: <info> Activation (wlan0/wireless): association took too long, failing activation. Jun 27 15:49:57 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 9 Jun 27 15:49:57 localhost NetworkManager: <info> Activation (wlan0) failed for access point (usenix-802.11a-only) Jun 27 15:49:57 localhost NetworkManager: <info> Marking connection 'Auto usenix-802.11a-only' invalid. Jun 27 15:49:57 localhost NetworkManager: <info> Activation (wlan0) failed. I note I forgot to mention kernel version: Jun 27 15:30:46 localhost kernel: Linux version 2.6.25.6-55.fc9.i686 (mockbuild@) (gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC) ) #1 SMP Tue Jun 10 16:27:49 EDT 2008 should have been the relevant boot. Is this better with recent kernels? Connections are highly driver dependent. If it's not, we can proceed with wpa_supplicant debug-level logging to get a better idea of what's really going on. The laptop currently has FC10 on it, and I haven't seen that behavior in a while. But I also haven't been in any situation with a large number of cells either. Ok, closing for now. Don't hesitate to re-open the bug if you do encounter it again. Thanks! |
Description of problem: I tell network manager to connect to usenix-802.11a-only, and it fails, never associating. If I run "iwconfig" while it's trying to associate, it shows the wrong essid ("usenix", a network I previously used). If turn off wireless through the applet, then ifconfig wlan0 up iwconfig wlan0 essid usenix-802.11a-only iwconfig wlan0 channel 36 iwconfig wlan0 ap 00:0F:7D:07:49:52 wlan0 comes up and associates with the specified access point. If I then reenable networking in the applet and select the a-only network, it will associate and get an IP address. Version-Release number of selected component (if applicable): $ rpm -q fedora-release fedora-release-9-2.noarch $ rpm -q NetworkManager NetworkManager-0.7.0-0.9.4.svn3675.fc9.i386 How reproducible: Not that. It sometimes works on a cold boot. It sometimes works when I retry connecting just through the applet. Additional info: ipw3945 adapter Usenix 2008. Lots of wireless networks around: 52? of them, 21 cells of the a-only essid.