Bug#361314: can't connect to wireless interface anymore
On Wed, May 17, 2006 at 11:18:45PM +0200, Matijs van Zuijlen wrote: > On Mon, May 15, 2006 at 03:35:31AM +0200, Michael Biebl wrote: > > So, wpa_supplicant is the way to go. That is why I won't change NM to > > make wpa_supplicant support optional because I don't want to divert that > > much from upstream. So I tagged this bug wontfix. > > Agreed. The problem for my case simply is that wpa_supplicant supports less > drivers than libiw. I'm sure this will change. I have now 'fixed' wpa_supplicant's wext-driver to support the airport card. Part my fix it is a bona fide bug fix, since the WEP key setting method was broken or at least sufficiantly different from iwlib's 'reference implementation' that it didn't work. I will try to make that one into a patch. The other part is a hackish attempt at stopping the wpa_supplicant driver from issuing ioctls related to WPA when the kernel driver doesn't support them. That needs some work. In any case, my card now works when I use wpa_supplicant on its own with a configuration file. In combination with nm, it still doesn't work, but debugging is a little difficult since I seem to be missing part of wpa_supplicant's output in nm's log. -- Matijs van Zuijlen http://www.matijs.net/ signature.asc Description: Digital signature
Bug#361314: can't connect to wireless interface anymore
On Mon, May 15, 2006 at 03:35:31AM +0200, Michael Biebl wrote: > So, wpa_supplicant is the way to go. That is why I won't change NM to > make wpa_supplicant support optional because I don't want to divert that > much from upstream. So I tagged this bug wontfix. Agreed. The problem for my case simply is that wpa_supplicant supports less drivers than libiw. I'm sure this will change. > The best way is to fix the driver (supporting the wext inteface) and not > NM to add workarounds for each buggy driver. > Chances are good that your network card will be supported in 2.6.17, > they added the BCM43xx driver which should work with your card and > according to [1] even support WPA. > Would you mind to test 2.6.17-rc4 and report back if it works (with NM)? I have an Airport card. The BCM43xx driver is, AFAICS, for the Airport Extreme card. The Airport card is working fine with the current kernel, except the driver has no support for WPA (but I'm ok with using WEP for now). -- Matijs van Zuijlen http://www.matijs.net/ signature.asc Description: Digital signature
Bug#361314: can't connect to wireless interface anymore
tags 361314 wontfix thanks Matijs van Zuijlen wrote: > On Mon, Apr 10, 2006 at 10:37:21AM +0200, Michael Biebl wrote: >> With 0.6 you need wpa_supplicant for both WEP and WPA encryption. There >> is currently no other way. > > That's what I feared. > >> I tried to start a discussion on the >> NetworkManager mailing list to fall back on libiw (iwconfig) for WEP >> encryption if no wpa_supplicant is available. Let's hope that the NM >> devs will consider that option. > > That would be good. Also, it probably shouldn't be too hard for > wpa_supplicant to support Airport cards. That would be a good thing, since > then I can finally start using WPA. I discussed this issue with Dan Williams, the upstream developer and here is his response: >> > since NM 0.6, wpa_supplicant is a dependency for WEP encrypted wireless >> > networks. If the wpa_supplicant binary is not found, the connection >> > fails. Wouldn't it make sense if NM falls back in this case to the >> > wireless extensions library libiw and sets the WEP key without the need >> > for a running wpa_supplicant? > > Yes, but IMHO requiring wpa_supplicant isn't that much of an issue for a > few reasons: > > 1) you need it for WPA and 802.1x stuff anyway > 2) it overlaps a lot with NM > 3) Using it exclusively removes quite a bit of nasty code from NM > > You can argue either way, but I decided that since using wpa_supplicant > for everything makes NetworkManager a lot simpler, it was the way to go. > > Dan > So, wpa_supplicant is the way to go. That is why I won't change NM to make wpa_supplicant support optional because I don't want to divert that much from upstream. So I tagged this bug wontfix. The best way is to fix the driver (supporting the wext inteface) and not NM to add workarounds for each buggy driver. Chances are good that your network card will be supported in 2.6.17, they added the BCM43xx driver which should work with your card and according to [1] even support WPA. Would you mind to test 2.6.17-rc4 and report back if it works (with NM)? Cheers, Michael http://bcm43xx.berlios.de/ -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#361314: can't connect to wireless interface anymore
On Mon, Apr 10, 2006 at 10:37:21AM +0200, Michael Biebl wrote: > With 0.6 you need wpa_supplicant for both WEP and WPA encryption. There > is currently no other way. That's what I feared. > I tried to start a discussion on the > NetworkManager mailing list to fall back on libiw (iwconfig) for WEP > encryption if no wpa_supplicant is available. Let's hope that the NM > devs will consider that option. That would be good. Also, it probably shouldn't be too hard for wpa_supplicant to support Airport cards. That would be a good thing, since then I can finally start using WPA. > I'm sorry that I can't provide you a working solution atm. If you want > WEP encryption it's probably best if you go back to 0.5.1 for now and > set the packet on hold. I will do that and hope for the best :). -- Matijs van Zuijlen http://www.matijs.net/ signature.asc Description: Digital signature
Bug#361314: can't connect to wireless interface anymore
Matijs van Zuijlen wrote: > On Sat, Apr 08, 2006 at 01:05:06AM +0200, Michael Biebl wrote: >> Hi Matijs, > > Hi Michael, > > Thanks for the quick reply. > >> I prepared a new release 0.6.2-2 which makes wpasupplicant optional. >> Please add >> deb http://debs.michaelbiebl.de/ unstable main >> to your /etc/apt/sources.list file, upgrade to this new revision and >> tell me if it works for you. If it still fails, remove the wpasupplicant >> package and try again. > > Sorry, my architecture is powerpc, so the debs don't work. I have built the > package from source (I had to change the .dsc file, since it had a different > hash and size for the orig.tar.gz file than the 0.6.2-1 version; I hope that's > not a problem). After removing wpasupplicant, I now do get a connection, > but it is to the wrong network: nm-applet reports the one I want: > > Wireless connection to 'slinky' > > Whereas iwconfig reports connection to 'linksys': > > eth2 IEEE 802.11b ESSID:"linksys" Nickname:"HERMES I" > Mode:Managed Frequency:2.462 GHz Access Point: 00:14:BF:B1:AD:1A > Bit Rate:5.5 Mb/s Sensitivity:1/3 > Retry limit:4 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality=5/92 Signal level=-97 dBm Noise level=-102 dBm > Rx invalid nwid:0 Rx invalid crypt:5 Rx invalid frag:336 > Tx excessive retries:5918 Invalid misc:0 Missed beacon:0 > > The access point I'm trying to connect to is encrypted with WEP. With 0.6 you need wpa_supplicant for both WEP and WPA encryption. There is currently no other way. I tried to start a discussion on the NetworkManager mailing list to fall back on libiw (iwconfig) for WEP encryption if no wpa_supplicant is available. Let's hope that the NM devs will consider that option. I'm sorry that I can't provide you a working solution atm. If you want WEP encryption it's probably best if you go back to 0.5.1 for now and set the packet on hold. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#361314: can't connect to wireless interface anymore
Michael Biebl wrote: > I prepared a new release 0.6.2-2 which makes wpasupplicant optional. > Please add > deb http://debs.michaelbiebl.de/ unstable main > to your /etc/apt/sources.list file, upgrade to this new revision and > tell me if it works for you. If it still fails, remove the wpasupplicant > package and try again. I have similar issues with the rt2570 driver, wpasupplicant is not supported. These new packages works much better, but for some reason DHCP does not work for the wireless anymore. (It works fine for the wired network) I'm trying to connect to an unencrypted network using Ad-hoc mode. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: Digital signature
Bug#361314: can't connect to wireless interface anymore
Hi Matijs, I prepared a new release 0.6.2-2 which makes wpasupplicant optional. Please add deb http://debs.michaelbiebl.de/ unstable main to your /etc/apt/sources.list file, upgrade to this new revision and tell me if it works for you. If it still fails, remove the wpasupplicant package and try again. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature