Bug 195411
| Summary: | Network Manager doesn't work with madwifi any more | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Torrey Hoffman <thoffman> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | chemobejk, mail, triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | bzcl34nup | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-05-06 16:00:03 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: | |||
|
Description
Torrey Hoffman
2006-06-15 02:54:59 UTC
Is the madwifi driver from livna "madwifi" or "madwifi-ng", and what SVN revision is it? I believe it was madwifi-ng -- as I mentioned in the original bug report, it was "madwifi-0.0.0.20060520-6.lvn5". However the machine in question is now running Ubuntu, (which does not have this problem) so I can't investigate further. NetworkManager-0.6.4-1.fc5 still has the special case code to request the driver
"madwifi" instead of "wext" from wpa_supplicant when it detects the ath_pci
driver. The NetworkManager packager in Rawhide for FC6 dropped this patch already.
From the log above:
INTERFACE_ADD ath0 madwifi /var/run/wpa_supplicant
But the latest madwifi releases, e.g. 0.9.2, implement wireless extension
support, making the madwifi driver in wpa_supplicant unnecessary. When I ran
wpa_supplicant by hand my access point was only recognized with the following
combinations:
driver madwifi AP_SCAN 1
driver wext AP_SCAN 2
On my machine NetworkManager always uses AP_SCAN=2, although in the log above it
uses AP_SCAN 1:
NetworkManager: <information> SUP: sending command 'AP_SCAN 1'
I don't know how NetworkManager decides to use AP_SCAN 1 or 2. Anyway I modified
the string "ath_pci" in /usr/sbin/NetworkManager and now it requests the wext
driver from wpa_supplicant and everything works OK for me.
The easiest way to test this is to run wpa_supplicant by hand as root with the
following configuration file:
------------------------ test.conf --------------------------
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2
network={
ssid="Arnor"
scan_ssid=1
key_mgmt=NONE
wep_key0=<insert your WEP key here>
wep_tx_keyidx=0
}
------------------------ test.conf --------------------------
Try which of the following commands creates a valid association with the AP:
# wpa_supplicant -dd -c test.conf -D madwifi -i ath0
# wpa_supplicant -dd -c test.conf -D wext -i ath0
Try the same commands with ap_scan=1. Now the result should be reversed.
I have exactly the same problem on an FC5 notebook here. Installing the FC6 devel RPM of NetworkManager is not an option to fix this bug because this RPM's dependencies require a lot of RPMs to be updated to devel. So NetworkManager is completely useless for me on this notebook at the moment. It would be a great help if there is a fix of this bug for FC5. Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |