As documented in bug 180369, NetworkManager stopped connecting my madwifi wireless card after the change from NetworkManager-0.5.1-8 to NetworkManager-0.5.1-10. I use the CVS versions of the madwifi drivers. I use WEP for authorization.
Today I downloaded the SRPM for NetworkManager-0.6.0-2 and removed the special-case-madwifi.patch and built the binary. This version of NM can connect to my madwifi card. The patch is trying to work around a WPA problem in the madwifi drivers. My question is has the fix for WPA broken WEP?
Hi,
Today I downloaded the SRPM for NetworkManager-0.6.0-2 and removed the special-case-madwifi.patch and built the binary. This version of NM can connect to my madwifi card. The patch is trying to work around a WPA problem in the madwifi drivers. My question is has the fix for WPA broken WEP?
It certainly looks like...
TTFN
Paul (trying to get his Atheros AR5212 card to work)
On Thu, 2006-03-09 at 14:52 +0000, Paul F. Johnson wrote:
Hi,
Today I downloaded the SRPM for NetworkManager-0.6.0-2 and removed the special-case-madwifi.patch and built the binary. This version of NM can connect to my madwifi card. The patch is trying to work around a WPA problem in the madwifi drivers. My question is has the fix for WPA broken WEP?
It certainly looks like...
Hmm, you did try the Fedora version of that exact package before getting rid of the patch, right? I had the same problem for a while and tried to solve it in the same way, by rebuilding without the patch which improved things but was still unstable (wadwifi, currently using madwifi-old driver since madwifi-ng was refusing to do anything for me for a while) but with 0.6.0-2 everything works fine again (sometimes the first association attempt on boot still fails but trying again gives me a perfect connection). There was a note in the changelog for the 0.6.0-2 version that wpa_supplicant wasn't used for the non-wpa scanning any longer, that seems like a significant change which might fix things.
/Per
On Thu, 2006-03-09 at 06:13 -0800, Brian Anderson wrote:
As documented in bug 180369, NetworkManager stopped connecting my madwifi wireless card after the change from NetworkManager-0.5.1-8 to NetworkManager-0.5.1-10. I use the CVS versions of the madwifi drivers. I use WEP for authorization.
Today I downloaded the SRPM for NetworkManager-0.6.0-2 and removed the special-case-madwifi.patch and built the binary. This version of NM can connect to my madwifi card. The patch is trying to work around a WPA problem in the madwifi drivers. My question is has the fix for WPA broken WEP?
Are you using madwifi drivers, of the madwifi-ng drivers? wpa_supplicant must be compiled for one or the other, and right now its compiled for madwifi-ng. So if you're not using madwifi-ng, NM + wpa_supplicant won't work for your card.
In general though, madwifi-ng has been _very_ touchy, with every other revision of the drivers being pretty much useless. Not sure about the older madwifi drivers though.
Dan
I use madwifi-ng from CVS. I have to say that when I downgraded to NetworkManager-0.5.1-8 they have always worked, but never for later NM. I have only now had success with later NM versions after removing the patch.
Dan Williams wrote:
On Thu, 2006-03-09 at 06:13 -0800, Brian Anderson wrote:
As documented in bug 180369, NetworkManager stopped connecting my madwifi wireless card after the change from NetworkManager-0.5.1-8 to NetworkManager-0.5.1-10. I use the CVS versions of the madwifi drivers. I use WEP for authorization.
Today I downloaded the SRPM for NetworkManager-0.6.0-2 and removed the special-case-madwifi.patch and built the binary. This version of NM can connect to my madwifi card. The patch is trying to work around a WPA problem in the madwifi drivers. My question is has the fix for WPA broken WEP?
Are you using madwifi drivers, of the madwifi-ng drivers? wpa_supplicant must be compiled for one or the other, and right now its compiled for madwifi-ng. So if you're not using madwifi-ng, NM + wpa_supplicant won't work for your card.
In general though, madwifi-ng has been _very_ touchy, with every other revision of the drivers being pretty much useless. Not sure about the older madwifi drivers though.
Dan