You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Saturday, December 30th 2006, 5:56pm

KNetworkManager

I am having some BIG problems with KNetworkManager.

My network card is usually recognized by default (RaLink RT2500 chipset). But, when I go into connect through KNetworkManager... it always gets to 28% (configuring device) and then it fails. It then brings up a config dialog for the wireless interface. This includes areas to fill in the "essid" of the network and the encryption. I choose the WEP Hex encryption, and enter the key. Then I try connect. Again, 28% and then it fails. The config dialog comes up again... but I notice that the encryption type has been changed to "Passphrase." No... I don't use a passphrase... i use a 64bit WEP Key! So, I choose WEP Hex again, enter my key, click connect. Again, 28% and it fails (this keeps going forever).

I have encountered KNetworkManager three times: In SUSE 10.1, in SUSE 10.2, and in Sabayon Linux 3.2 (DVD). In SUSE 10.1, I uninstalled it, and used KInternet... which worked perfectly! In SUSE 10.2... my card was recognized, but KNetworkManager wouldn't let me connect (same problem as above). However, when I used KInternet, it didn't work either. I think that was an issue of how it was configured by default by YaST. Anyways, in Sabayon 3.2 my card was again recognized, and Sabayon even has the RaLink RT2500 configuration utility (official one), and I tried connecting through there, which seemed to work (nice green lights everywhere, no errors). But for some reason, it didn't. I notice KNetworkManager is running, so I try through there (same errors as described at the beginning).

I see no reason why KNetworkManager doesn't let me connect! I doubt it is a driver issue, as I see that it is usually recognized correctly. As said before, my card is based on the RT2500 chipset, and is PCI interface. My encryption is 64 bit Wep Hex, and I know I type it in right :P . Please help me get these problems sorted out... Thanks!

2

Monday, January 1st 2007, 11:50am

RE: KNetworkManager

Not sure if that is causing your problem, but for me KNetworkManager doesn't work with static IP addresses. Do you have DHCP activated on both, your router and your machine?

3

Monday, January 1st 2007, 2:36pm

RE: KNetworkManager

Hmmm.... I would believe so. That could be the source of this.... but how would I go about changing this?
Thanks so far!

4

Monday, January 1st 2007, 5:56pm

RE: KNetworkManager

As far as I know there is no workaround for using DHCP on the connections. At least I couldn't resolve the problem. So it's the choice to either use the "traditional" setup with static IP addresses or the KNetworkManager setup with DHCP.

Either way, for me the WLAN works with WPA-PSK like a charm :-) Whatever enryption you choose (hex or passphrase), it works.

For the records: using SuSE 10.1, with an Intel PRO/Wireless 3945ABG built in module (Toshiba Notebook Satellite Pro U200) on a Fritz! Box WLAN 7050 router..