Bug 156409 - NetworkManager: Problems connecting to AP
Summary: NetworkManager: Problems connecting to AP
Status: RESOLVED DUPLICATE of bug 156389
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Beta 6
Hardware: i686 SuSE Linux 10.1
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-09 11:44 UTC by Stefan Arndt
Modified: 2006-03-09 12:44 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Arndt 2006-03-09 11:44:54 UTC
Hello,

I experienced the following problems with when trying to use (K?)NetworkManager to use wireless internet.

First, I use the packages from Beta6 and I am able to connect
to my AP with NetworkManager.

Sometimes, my access point simply do not appear on the list of
knetworkmanager, sometimes there are wireless networks shown
without a single ESSID. Here, usually restarting NetworkManager
helps. 
Looking through the other NetworkManager Bugreports, I found
recommondations to update
NetworkManager (to 0.6.0cvs20060306). The result was no wireless
networks were shown in KNetworkManager, even though nm-tool
listed all available networks. (I updated KNetworkmanager as well,
but it was the same version as in beta6)

Another point I want to make is that when the initial
attempt to connect to my access point fails, I get
the Knetworkmanager dialog to connect to other wireless network,
but the wrong one.

My knetworkmanagerrc is as follows:
ESSID=Egal
Encryption=WEP
HardwareAddresses=00:....
Timestamp=2006,3,8,23,51,42
Trusted=true
WEPMethod=OpenSystem
WEPType=ASCII

Furthermore I am a bit confused that it is possible at this point
to make my encryption key visible. I know that the key is stored
in kwallet but here I need to have the password. I think
a possible wrong encryption key must only be corrected in kwallet.

I hope I did not reopen known bugs.
Regards

Stefan Arndt

WEPType=ASCII
Comment 1 Michael Gross 2006-03-09 12:44:32 UTC

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