Bug 261588 - networkmanager fails to set up WPA (broadcom/ndiswrapper)
Summary: networkmanager fails to set up WPA (broadcom/ndiswrapper)
Status: RESOLVED DUPLICATE of bug 164394
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Mobile Devices (show other bugs)
Version: Final
Hardware: x86-64 SuSE Linux 10.1
: P5 - None : Normal with 5 votes (vote)
Target Milestone: ---
Assignee: Tambet Ingo
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-06 07:58 UTC by Tom Malfrere
Modified: 2008-03-29 17:11 UTC (History)
1 user (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
log of failed WPA connect (13.07 KB, application/octet-stream)
2007-04-10 20:44 UTC, Tom Malfrere 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Malfrere 2007-04-06 07:58:36 UTC 
I tried to set WPA TKIP with knetworkmanager but I never get a connection.

My notebook is an ASUS A6KT with a broadcom wifi card. I use ndiswrapper (1.10) as a driver.
WEP encryption with a 128 key works with knetworkmanager!
WPA does not.

I got WPA working, following the instructions on this page :
http://ndiswrapper.sourceforge.net/mediawiki/index.php/WPA

Note: 
-I replaced the wpa_* in /usr/sbin with the new ones
-I used the "wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd" litteraly.

Why isn't it working with knetworkmanager.

Is there a possibility to make knetworkmanager verbose or make a log of it's actions so I can see what it's doing?
Comment 1 Will Stephenson 2007-04-10 14:30:02 UTC 
/var/log/NetworkManager is what we need to see here.
Comment 2 Tom Malfrere 2007-04-10 20:44:38 UTC 
Created attachment 130213 [details]
log of failed WPA connect
Comment 3 Timo Hoenig 2007-04-12 11:21:22 UTC 
Adjusting summary and reassigning.
Comment 4 Joachim Gleissner 2007-04-12 12:19:06 UTC 
The problem is that using ap_scan=2 (what networkmanager does) requires specification of the used ciphers (what networkmanager does not, at least not necessarily). You can try this by selecting "Connect to other wireless network" from knetworkmanager, enter SSID and other values, and then select TKIP or CCMP from the "WPA protocol" drop-down box. The connection should get established then.

*** This bug has been marked as a duplicate of bug 218842 ***
Comment 5 Joachim Gleissner 2007-04-19 06:33:51 UTC 
Excerpt from e-mail correspondence with Tom: his access point is not hidden, so besides the fact, that NM does not enforce cipher settings when using ap_scan=2, NM uses ap_scan=2 superfluously. IIRC this is not intended.
Comment 6 JP Rosevear 2008-03-29 17:11:28 UTC 

*** This bug has been marked as a duplicate of bug 164394 ***