Knetworkmanager = Hair pulling

I just don’t get it?

I’ve attempted multiple times to get the knetworkmanager to connect to an unencrypted network, yet it keeps asking for a wep key.

However the networkmanager in the Gnome version connects to unencrypted networks just fine.

Why won’t knetwork manager do the same?

I use yast to connect to a network, because knetworkmanager is unreliable to me.

Hi,

openSUSE version? KDE version? Steps taken to connect? One thing I can think of right off the bat, is that KDE has Kwallet which will ask for a password to access the network manager. This can be disabled, but it’d be nice if you gave some details so we can try to help you troubleshoot the problem.

Take Care,

Ian

Thanks! I will try to give the yast NM a go

@ijbreakey. Im using the Latest Opensuse version. 11.3

I just clicked on Knetworkmanger on the tray, and attempted to manually add the access point, still asked for WEP key, then scanned and attempted to connect. Still asked for wep key even though it’s an unsecured network.

Yeah the KDE wallet isn’t a problem as I got to enter the password and use it just fine

Was this connection protected with WEP first?
Which KDE version?

You can disable kwallet???

It was once protected by wep, but that was long ago.

Well! I DID IT! YES!!! After playing around with the Yast Network manager. I have succeeded in having a wireless connection! Thanks Pilger. :slight_smile:

I was so close to giving up hope on kde

You can disable kwallet???

Don’t know about disabling but you can leave the password blank and it will not ask again.

I meant disable using kwallet with knetworkmanager. If you store the wep/whatever key in an unencrypted file then it won’t use kwallet. Just right click on knetworkmanager and then choose manage connections. Click other and under Connection Secrets choose In file (unencrypted).

Take Care,

Ian

Thanks! wow I didn’t know that. Ah sneaky knetworkmanager. So I gotta go into Choose Manage Connections then go to Connection Secrets.

Correct. I believe any connections made before this change will still use kwallet though, so you have to delete any connections made with knetworkmanager then recreate them once the switch to In file (unencrypted) is made.

Take Care,

Ian

Thats a useful tip. I’ll have to try to remmeber for the future. :slight_smile: