Bug 152095

Summary:	NetworkManager does not work with hex WLAN passphrases
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Rasmus Plewe <rplewe>
Component:	Network	Assignee:	Robert Love <rml>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	suse-beta
Version:	Beta 4
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Log file with the output from the Network Manager during the failed attempt to connect with hex wep key. NetworkManager logfile

Description Rasmus Plewe 2006-02-19 15:38:33 UTC

Giving the right hex passphrase for the WLAN network simply results in NetworkManager to return to the configuration dialogue. The network connection is not set up (the DHCP server e.g. does not get any DHCP queries, although DHCP queries are sent). Using the same hex passphrase while configuring the WLAN card in yast2 works without problems.

Comment 1 Robert Love 2006-02-27 20:42:32 UTC

Hex != passphrase.

You need to select "WEP 40/128-bit hex" if you have a hexadecimal WEP key.

Can you please try that and confirm?

Comment 2 Robert Love 2006-03-08 23:14:23 UTC

Assuming this is fixed and closing.

Comment 3 Rasmus Plewe 2006-03-22 13:26:27 UTC

The problem still exists with beta8, apparently. Just by changing the "Network Setup Method" in yast2 from NM to "Traditional", the connection gets set up. So the configuration is correct.

Comment 4 Robert Love 2006-03-22 13:56:10 UTC

NM doesn't necessarily use the YaST configuration.

In the applet, do you see your network in the scan list?  Click it.  Select "128-bit WEP Hex Key" presuming that your key is 104-bits long.  Enter the hex key.  Click OK.

It does not connect?  What happens?  I need significantly more details.

Can you attach the output of the log /var/log/NetworkManager, during the ordeal?

Comment 5 Michael Brasse 2006-03-23 15:22:49 UTC

The same problem here. I am using a Dell Latitude C640 with the Orinoco card built in. The connection seems to come true, but an IP address never gets assigned. As described above it works fine without Network Manager. This problem exists at least since Beta6, probably already earlier. I attach the log.

Comment 6 Michael Brasse 2006-03-23 15:25:16 UTC

Created attachment 74761 [details]
Log file with the output from the Network Manager during the failed attempt to connect with hex wep key.

Comment 7 Robert Love 2006-03-23 15:29:33 UTC

Michael: Problems with Orinoco cards are known and unrelated to the use of hex keys.  That bug is tracked in bug #144268.

Rasmus: I still need to know exactly what is happening and what your driver is, and get a copy of /var/log/NetworkManager.

Comment 8 Rasmus Plewe 2006-03-24 08:56:16 UTC

OK, I got back to that hex-encrypted network. The yast2 workflow is confusing, to say the least (I will file a seperate bug for that). But despite that, it does not work:

- Setting network setup to "NetworkManager" in yast2.
- Insert WLAN card. After some seconds, an authentication window pops up
  (note: If the card is already inserted when I set to NM, the window 
  does not seem to pop up. Or I was not patient enough)
- I change "Wireless Security" to 40/128-bit hex, click on "Login to Network". 
- The DHCP client gets started, the DHCP server does not see any DHCPREQUESTs.
- The authentication window pops up again. Back to the start.

- I then set the network setup to "traditional" in yast2, configured with 
  the same hex key. Exit yast2, connection gets established -> not a HW/WLAN
  setup problem.

Comment 9 Rasmus Plewe 2006-03-24 08:59:38 UTC

Created attachment 74861 [details]
NetworkManager logfile

Comment 10 Robert Love 2006-03-24 15:37:42 UTC

Issues with orinoco are known and tracked in bug #144268.

Marking this as a dupe, please follow that bug.

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