wireless support sucks - won't retain WEP settings

[lowrider]

This release blows chunks. The user interface is horrid.

I ran ndiswrapper to get the stupid thing to recognize my wireless card. It sees my router (and all the others in my neighborhood), but it will not connect. I've saved the config, but if I reboot, it looses the WEP info and even after re-inputting the info, it will not connect.

It SEES the router. It SEES every other router on the block. It WON'T connect. WEP info was double checked. It won't connect and it won't retain the WEP settings if booted.

I put Ubuntu on it, and it worked fine, ndiswrapper worked fine, it connected with no problems and my only issue was it wouldn't run K9copy. So I loaded Kubuntu and now it's basically useless since the wireless will not connect.

What a hunk of crap. I was a big fan, up until now. This release is crap

[sithlord48]

try installing wicd and using it as your network manager

sudo apt-get install wicd
to use it you will have to remove knetworkmanager (it will autoremove it for you).
then after install press alt-f2(run box default) and run wicd-client,
use wicd (now in your system tray) to manage you network needs

[lowrider]

You rock, that did it. Oddly, I can't get apt-get to pull the info and had to go to the repository to pull all the packages, but once WICD was installed, it was working in 30 seconds. Thanks much!

now to figure out why apt-get won't work

Thaks again!

[cybehh]

I have been banging my head around for secured wireless to work from jaunty and now on Karmic. The native network-management never worked for me on Jaunty and I used Knetworkmanager all this time to connect to wireless.

Now last night even after knowing about the wireless issue in Karmic I being a hard core fan upgraded to Karmic, and not a surprise this **** is not working again. Can see my wireless card, can find the AP's but simply wont connect and keep asking for the network key. Had the same problem with jaunty.

Am using Ralink RT2870 Chip wireless USB Hi Gain card. Worse of all cannot even install Knetworkmanager on this.

Tried installing WICD, than it cant even find the wireless card, allright I installed a driver through Ndiswrapper, bingo WICD finds the AP, but again cannot obtain an IP address.

Tried installing the latest STA drivers, for some reason, Ralink site has removed those drivers, got it from mirrors, but those drivers wont install on the new Kernel, some API problem. Great, booted into the 28.14 older kernel, it wont install either.

Don't really know what to do. Currently connected through a bridged connection on windows. Am so pissed and just don't want to return to windows after 6 yrs, for this little thing.

Its so irritating. Please somebody help.

Cheers.
Cybeh

[dibl]

bingo WICD finds the AP, but again cannot obtain an IP address.




Hmmmmm. Sounds like you're very close at this point.

I assume there's no question that your router is a DHCP server and will provide an IP address?

When I was first learning the mysteries of wireless connections, I turned off the encryption just to eliminate that part of the puzzle -- you might want to try that for long enough to see if that is the only problem. BTW, if you happen to get it to connect, you might want to go to WPA2 if your router supports it -- it is a considerably more robust encryption than WEP.

[kjjjjshab]

...you might want to go to WPA2 if your router supports it -- it is a considerably more robust encryption than WEP.


Well, WEP after all does stand for Wired-straight-into-a-hacker's-computer Equivalent Protection.

Please see my post here which might help you get WPA2 working, if that gives you any trouble... the fix was applied to Jaunty, but should still be relevant.

http://kubuntuforums.net/forums/index.php?topic=3106370.msg195872#msg195872

[cybehh]

Thanks Guys,

It worked with NT drivers using Ndiswrapper and native network-manager with plasma-widget-networkmanagement.

Though it was just a fluke coz I uninstalled WICD and installed the network-manager back again and after the reboot to my surprise it worked.

One thing to note even the nm-applet didn't worked for me, so as NT drivers are working, am assuming its got to do something with the drivers or some missing link, coz it can still scan and find AP's with the rt2800usb driver (Yeah its not rt2870sta in Karmic).

Bounces me, but its working (though no aircrack-ng for me). Hope this is the solution and help hundreds of users who are facing the same problem and developers can come up with a fix for this problem

I persuaded a friend for a month to chuck windows 7 and install Kubuntu and he dropped it just coz of this issue.

If we can make this simple work straight out of the box for layman's I bet we'll have ton loads of users on this forum. Amen!!

PS: kjjjjjshab, am actually using a hacked wireless ;D that's the reason am forced to stay on wireless and no Ethernet.

Cheers,
Cybeh

[sithlord48]

now that your drivers are correct you can use wicd if you wish , i find it to work better with encrypted networks,the is the first release version of knetworkmanager http://dot.kde.org/2009/11/07/introducing-kde-4-knetworkmanager

[cybehh]

now that your drivers are correct you can use wicd if you wish , i find it to work better with encrypted networks,the is the first release version of knetworkmanager http://dot.kde.org/2009/11/07/introducing-kde-4-knetworkmanager



No it was not working with WICD with the same NT drivers, it was not able to obtain the IP address. I dont know why?

[sithlord48]

oh nm then ::)

[kabar2009]

I just wanted to chime in and say thank you. I was having the same problem with connecting to my router. My only question is how make wicd my default network manager. I don't want to run wicd every time I restart my computer.

[kjjjjshab]

I just wanted to chime in and say thank you. I was having the same problem with connecting to my router. My only question is how make wicd my default network manager. I don't want to run wicd every time I restart my computer.


Did you try System Settings (Advanced tab) -> Hardware... Network Manager Backend (and then move wicd up the list to the first position)?

I forget if that works or not, but certainly worth a try.