393725 – "Automatic configuration" option doesn't manage to setup a working configuration with multiple NICs

Bug 393725 - "Automatic configuration" option doesn't manage to setup a working configuration with multiple NICs

Summary: "Automatic configuration" option doesn't manage to setup a working configurat...

Status:	RESOLVED DUPLICATE of bug 389131

Alias:	None

Product:	openSUSE 11.0
Classification:	openSUSE
Component:	Installation (show other bugs)
Version:	Beta 3
Hardware:	x86-64 openSUSE 11.0

Priority:	P5 - None Severity: Major (vote)
Target Milestone:	---
Assignee:	Michal Zugec
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2008-05-22 19:04 UTC by Markus Koßmann
Modified:	2008-05-23 07:41 UTC (History)
CC List:	0 users

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

Attachments
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 Markus Koßmann 2008-05-22 19:04:03 UTC

I have a system with 3 NICs :
00:13.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) ( onboard)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 15) ( onboard )
04:07.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01) ( addon card) 

The "Automatic configuration" option decides to configure only the Atheros wireless NIC. This is a bad idea because there is only a chance to get a working automatic configuration for a wireless NIC if the user is running his WLAN without encryption. The installer should try to configure one ( or better both) non-wireless ethernet controlers instead.

Comment 1 Michal Zugec 2008-05-23 07:41:38 UTC

This was already fixed, but after beta3
YaST now configures first device (in case ifup - no NetworkManager) with link:yes  - that means connected device

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