Bug 256350

Summary:	Configuring wireless network for use with ifup does not work
Product:	[openSUSE] openSUSE 10.3	Reporter:	Casual J. Programmer <casualprogrammer>
Component:	YaST2	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	casualprogrammer
Version:	Alpha 2
Target Milestone:	---
Hardware:	i686
OS:	SUSE Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST2 logs hwinfo --netcard hwinfo --wlan

Description Casual J. Programmer 2007-03-21 11:55:40 UTC

On a FSC Amilo 1520Si running openSuSE 10.3 alpha 2 plus, configuring a wireless connection with "YaST2/Network Card" does not provide the desired result.

In the "Network Setting Dialog" Tab "Global" when choosing "Traditional Method with ifup"for "Intel PRO/Wireless 3945ABG Network Connection" no connection is possible with wpa2 / wpa or wep.

On setting the network interface up with ifup eth1 wpa_supplicant is not started.

When setting up a configuration file ( /etc/wpa_supplicant.conf ) and starting wpa_supplicant manually all three methods work fine.

Comment 1 Casual J. Programmer 2007-03-21 12:01:12 UTC

Created attachment 125692 [details]
YaST2 logs

Comment 2 Michal Zugec 2007-03-23 07:35:33 UTC

could you provide output from "hwinfo --netcard" and "hwinfo --wlan"?

Comment 3 Casual J. Programmer 2007-03-23 14:42:09 UTC

Created attachment 126209 [details]
hwinfo --netcard

Comment 4 Casual J. Programmer 2007-03-23 14:43:52 UTC

Created attachment 126212 [details]
hwinfo --wlan

I just did a complete "clean" install and tried to set the manual configuration during setup, this does not work either.

Comment 5 Casual J. Programmer 2007-03-23 14:48:30 UTC

Not sure whether this should be a bug in its own right:

WPA2 configuration is not possible with YaST network configuration, only with network manager.

Comment 6 Casual J. Programmer 2007-07-01 15:45:33 UTC


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