Bugzilla – Bug 153536
NetworkManager fails dhcp with ndiswrapper and wep
Last modified: 2006-03-16 22:23:42 UTC
I'm unable to obtain an IP address when using NetworkManager with my ndiswrapper supported notebook (broadcom). By turning WEP off on the AP, NetworkManager successfully gets an IP address. If I shutdown NetworkManager, and connect by setting WEP key using tradition yast mode, I'm able to get an IP address. This did work with version of NetworkManager in SuSE 10.0, just not in NLD 10 beta4.2. Attached will be NetworkManager log from connecting with and without WEP.
Created attachment 70289 [details] NetworkManager with WEP log
Created attachment 70290 [details] NetworkManager no WEP log
jg, any ideas? Has anything changed w.r.t. ndiswrapper? Should this work?
Does your AP broadcast its SSID?
Yes, I broadcast the SSID.
Similar incident just reported on the NM mailing list. Apparently, the broadcom/ndiswrapper driver is busted and drops all settings whenever a scan is initiated.
Robert, what do you think of the patch recently posted on the NM list? Should we package this workaround?
Yes, we should definitely give this patch a try. The first hunk I am unsure of; it might have unintended consequences, although hopefully not. The second junk is great -- if the wpa_supplicant ndiswrapper driver works, then it is a good move. I will build a test package, play around, and if I see no obvious breakage, submit an updated package.
Yes, the first hunk looks absolutely scary ;-) Will this probably also help with setups using ndiswrapper + WPA?
Should, yes.
If you end of happy with the test package, would love to test myself :)
Bill: Yes, definitely! So ... it works for me. I'd like your feedback if this fixes the problem. If not, we can try one more thing, but I hope this does it. I submitted an updated package to autobuild, so it will be in the next beta (version 0.5.1cvs20060302 or later). In the meantime, I also put up packages here: http://primates.ximian.com/~rml/misc/ If you can test and report back, we would appreciate it!
Thanks for jumping on this so fast. Pulled down the packages, and I get a different error message now when connecting to a wep network: Error connecting to wireless network The requested wireless network requires security capabilities unsupported by your hardware.
Hrm, that is a different and unrelated problem. Can you attach the output of `nm-tool`, please?
Also, in addition to the `nm-tool` output, can you specify which wireless network you are attempting to connect to? Thank you.
Sorry it took so long... OK, after rebooting, I don't get the capabilites error now, what I do get is 2 errors: nm-applet doesn't start along with NetworkManager, I have to run it manually after NetworkManager starts. And get prompted for the network key like before, but it still doesn't connect to my wep wireless, but the log looks much different (I see the correct key in the log now). I'm attaching, the NetworkManager log, and nm-tool output. Cavalieri is the network I'm connecting too. Thanks
Created attachment 71090 [details] NetworkManager Wep cvs20060302-2 log
Created attachment 71091 [details] nm-tool log
Alright, thanks Bill. The first problem is caused because we moved the location of the autostart files. An updated gnome-session will fix the problem. The second problem we need to solve. I checked into autobuild a new NM, 0.5.1cvs20060303, which has some additional ndiswrapper fixes. Another ndiswrapper user confirmed that these actually fix his problems, so I have high hopes. I put packages up here, too: http://primates.ximian.com/~rml/misc/NetworkManager/ Please let me know!
Fantastic, fixed my wep connecting problem. VPN, changing networks, changing back to wired, all work as expected. Thanks a lot.
Fixed
*** Bug 156399 has been marked as a duplicate of this bug. ***