[Bug 134034] [NEW] WPA doesn't work

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm using 32bit Ubuntu (same on Ubuntu, Xubuntu and Kubuntu so nothing to do with network-manager-gnome or knetworkmanager issues - lower level issue)
If you have a RT2500 or BCM4318 network card you should be able to replicate this... but I have a feeling that it might be possible to replicate on a lot more as the drivers work!

On BCM4318:
bcm43xx kernel module doesn't support wpa - fair enough... use Ndiswrapper...
apt-get install ndiswrapper-util-1.9
ndiswrapper -i bcmwl5.inf
ndiswrapper -m
ndiswrapper -l
output reports card driver ok and hardware present
rmmod bcm43xx (remove module)
edit /etc/modprobe.d/blacklist add "blacklist bcm43xx"
edit /etc/modules add ndiswrapper
modprobe ndiswrapper

use network-manager and try to connect - failed! network-manager recognises hardware and ability to use wpa (asks for wpa psk) but doesn't connect even finds the network
as far as i can tell using dmesg, running network-manager without a daemon and so on there are not obvious bugs!
All of the above works in Dapper!

Exacly the same for RT2500! (my other laptop)

My desktop has bcm4318 card and that doesn't work either!

The forums and everywhere says the issues are with the packages provided by Ubuntu - they don't work!
Ndiswrapper version apparently has problems and wpa_supplicant turns itself off (read UbuntuForums)
This is a major problem - how many laptops can only use wireless with Ndiswrapper + WPA!

I got one laptop to work using a script that updated Ndiswrapper and modified config files I don't understand - now if that's Linux security I'm going back to Windows!
Wireless should work - The above should work and ndisgtk should know if the hardware is present if ndiswrapper reports it is!

Please, please, please sort this out - the ndiswrapper and possibly
wpa_supplicant, network-manager packages need serious bug-fixing and/or
upgrading!

I can edit /etc/interfaces and have done so on my desktop - that didn't
work in Feisty but did in Dapper

bcm4318 is a very, very, very common chipset and so is the rt2500 I have
7 network cards in my house I didn't buy the same brand and between them
I only have 1 that isn't bcm4318 or rt2500!

This bug should be really easy to replicate!
I followed a previous thread that stated just goto the rt2500 entry in wifidocs! I found that site is useless... I don't want to have to edit the interfaces file everytime I move my laptop between 2 work places, university and home!

The reason PCLOS is beating Ubuntu in the distrowatch count is because
of this! There is nothing else going for PCLOS except even the livecd
works with ndiswrapper and you can connect to the network!

I don't believe that this issue is resolved in Gutsy from forum posts
but I might check later and update this to let you know for sure!

** Affects: ndiswrapper (Ubuntu)
     Importance: Undecided
         Status: Confirmed

-- 
WPA doesn't work
https://bugs.edge.launchpad.net/bugs/134034
You received this bug notification because you are a member of Kernel Bugs, which is subscribed to ndiswrapper in ubuntu.