Bug 157026

Summary:	cisco aironet 450 card not used correctly
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Marcus Meissner <meissner>
Component:	Basesystem	Assignee:	Robert Love <rml>
Status:	RESOLVED WORKSFORME	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 7
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	netcard.log messages NetworkManager

Description Marcus Meissner 2006-03-10 12:46:27 UTC

my cisco aironet 450 card (airo_cs kernel driver) exposes two network interfaces: 
eth1 and wifi0

grep fully-supported /var/log/NetworkManager shows eth1 entries

/var/log/messages shows dhclient: wifi0: unknown hardware address type 801

Comment 1 Marcus Meissner 2006-03-10 12:48:19 UTC

Created attachment 72242 [details]
netcard.log

hwinfo --netcard

Comment 2 Marcus Meissner 2006-03-10 12:49:02 UTC

Created attachment 72243 [details]
messages

/var/log/messages

Comment 3 Marcus Meissner 2006-03-10 12:49:30 UTC

Created attachment 72244 [details]
NetworkManager

/var/log/NetworkManager

Comment 4 Robert Love 2006-03-10 14:21:54 UTC

Marcus, I am confused by what the problem is?

eth1 looks like it is correctly used.

Isn't wifi0 a control interface?  NM does not use it.

Comment 5 Marcus Meissner 2006-03-10 14:37:13 UTC

the problem is that i dont get an dhcp ip number, since
dhclient is called with wifi0 apparently.

Somewhere between NetworkManager and dhclient this hickup happens...

Do you have any idea where to add debug or to look?

Comment 6 Robert Love 2006-03-10 14:44:03 UTC

Okay, I see now.  I was confused.

We launch dhclient via dhcdbd (a control wrapper around dhclient that exposes a DBUS interface).  We communicate with dhcdbd in src/dhcp-manager/nm-dhcp-manager.c.

It seems very, very odd that NM could confuse wifi0 and eth1.  It stores the interface names with each device, and wifi0 should not be anywhere.  You can see where NM tells dhcdbd what interface in that file, the calls to nm_device_get_iface().

One other oddity - your messages file has text about ifplugd and ifup.  Both of those could mess up NM.

Comment 7 Marcus Meissner 2006-03-10 14:57:23 UTC

tried anew, kept my hands of ifup and similar tools.

now it works better :/

will report if it fails again