Bug 201725

Summary:	KNetworkmanager fails to automatically attach to trusted network on startup
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Hans Gunnarsson <hans.gunnarsson>
Component:	Network	Assignee:	Timo Hoenig <thoenig>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	hugo.costelha, suse-beta, wclacy
Version:	Final
Target Milestone:	---
Hardware:	32bit
OS:	SuSE Linux 10.1
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	NetworkManager log config for the wireless adapter

Description Hans Gunnarsson 2006-08-25 11:58:11 UTC

I have my primary network specified in /etc/sysconfig/network/ifcfg-wlan.... It is a WEP 128 secured access point.

When I boot the computer KNetworkManager fails to automatically connect to this network when i boot and login even though it is among my trusted networks. If i choose it manually from KNetworkManager, it connects.

If I remove my /etc/sysconfig/network/ifcfg-wlan... config file, it connects automatically when i boot and login.

Comment 1 Hans Gunnarsson 2006-08-25 12:01:01 UTC

Created attachment 97139 [details]
NetworkManager log

The log when it first doesn't connect, and then when I force it connects. 
It seems to try several times and then time out since it takes more than a minute.

Comment 2 Hans Gunnarsson 2006-08-25 12:02:13 UTC

Created attachment 97140 [details]
config for the wireless adapter

I have removed my wep key from this and the NM-log

Comment 3 Walt Lacy 2006-08-28 15:47:31 UTC

is this a duplicate of  Bug 169783 NetworkManager: can't reconnect to known
WLANs

Comment 4 Hans Gunnarsson 2006-09-07 06:03:18 UTC

It doesn't seem to be a duplicate, since my SSID is broadcasted, and the network shows up in the knetworkmanager applet, it just doesn't automatically connect at startup.
Also, if I select it in Knetworkmanager it connects unlike in bug 169783

Comment 5 Walt Lacy 2006-09-07 23:42:39 UTC

Bug 169783(NetworkManager: can't reconnect to known WLANs) is actually not about the hidden essids.  But people are also seeing a problem with essids and the Atheros Chip. (Bug 175852)

I have the same problem with KNetworkManager and reconnecting to a WEP enabled Wireless Network(Hidden or broadcast essid).  I don't think it is just NetworkManager because I havn't seen people with this problem under Gnome.  I think it has something to do with KNetworkManager.

See Also:
Bug 177490 
Bug 186828 
Bug 187326

Comment 6 Timo Hoenig 2006-09-25 07:06:51 UTC

Is one of you probably able to check if this is the same within a GNOME environment (using nm-applet)?  That would help us to see if it is a NetworkManager or KNetworkManager issue.

Thanks!

Comment 7 Stefan Behlert 2006-10-18 12:28:15 UTC

Anything new here?

Comment 8 Timo Hoenig 2006-11-02 18:37:38 UTC

No update within two weeks, closing as INVALID.

Hans, if the problem remains, please re-open this bug.

Comment 9 Timo Hoenig 2006-11-02 18:41:42 UTC

-> INVALID